How data is used

Description of the current Windows build of Sera, 10/08/2026.

Local vault

Profiles, imported bots and settings are saved on your computer. The private storage is protected by encryption. Running browsers and bots get the access they need to do their work.

Google Drive

Sera requests drive.file permission for files created by the application or provided to it by the user. Copies are sent to the Google Drive of the account selected by the user. Google password is processed by Google. Authorization data is stored locally with device protection; The assistant bot does not receive OAuth tokens. To disable, use the button in Sera; permission can also be revoked in your Google account settings.

Payment and AI

The creation and confirmation of payments uses the ownsera.com server and the selected payment system NOWPayments or TryBit. When accessing cloud AI, the request text is transmitted to the selected provider. Each service has its own data processing terms.

Website and bot

This version of the site does not add advertising counters or download external fonts. The server can keep a technical log of requests. The Google Cloud bot launches a local wizard, downloads the official Google Cloud CLI, creates the selected project at your command, and enables the Drive API. Desktop OAuth settings are passed to the local Sera and stored encrypted. The bot does not send archives on its own. Google Cloud CLI authorization is stored separately in its local configuration.

Deletion and copies

Uninstalling a program does not automatically remove copies from Google Drive. Manage local data, cloud files and access separately. Save the vault key: without it, restoring the encrypted copy may not be possible.