Security

System & Account Security

Last updated: November 2026

This page describes the security measures in place at SONNESTRA to protect your account and data, and how you can help keep your account safe. For how we collect and process data, see the Privacy Policy.

1. Overview

We protect data in several layers, so that a fault in one layer does not expose the whole system:

  • Sign-in does not require a password, which reduces the risk of a reused password being leaked.
  • The server verifies the sign-in session before processing any sensitive request, and does not trust information the browser declares about itself.
  • The database administrative key exists only on the server and never appears in the browser.
  • Videos and reference images are accessed through signed links with a short expiry.

2. Sign-in authentication

You sign in in one of two ways:

  • Email link (magic link): enter your email, then click the link in the message sent to your inbox. The link only signs in to the account tied to that exact email address, and is confirmed on the system’s authentication page.
  • Google account: authenticated through Google using the OAuth protocol. We never receive your Google password.

We do not store passwords, because the service does not use them. So your sign-in email inbox is the key to your account. Protect that inbox with two-factor authentication from your email provider.

3. Sessions

The sign-in session is kept in a cookie managed by the authentication system. The session cookie is sent when needed and refreshed automatically while you use the service.

  • Sign out of the current device: click sign out in the navigation bar.
  • Sign out of all devices: go to Settings, Account and security section. Sessions on all devices will end and you will need to sign in again.

Use this feature when signing in on a public or shared computer, or when you suspect your account has been accessed without permission.

4. Encryption in transit

  • The website works only over HTTPS. The browser is instructed to always use HTTPS for this domain (HSTS), even when you type the address without https://.
  • Connections between the website, the database and processing servers go through encrypted channels.
  • Video download links use HTTPS and carry a signature.

5. Data access control

User data tables have Row Level Security (RLS) enabled from the first migration. So at the database layer, each account can read and write only its own data, even if there is a bug in the application layer.

  • Administrator rights are checked on the server, not based on information sent by the browser.
  • Administrative actions (approving payments, adding or deducting credits) are recorded and reserved for accounts granted admin rights.
  • Full-access service keys are used only on the server and processing workers, and are never sent to the browser.

6. Videos and reference images

File typeProtection
Rendered videosDownloadable only through signed links tied to a specific path that expire after 10 minutes. A link copied and used after that time will no longer work.
Reference imagesStored in a private, non-public store. Uploaded through an upload link with a time limit issued by the server. Limited to 10 MB, and only PNG, JPEG and WebP are accepted.
Reference images during renderingThe worker downloads the image using internal service permission and checks the file format signature before processing, not just the file extension.

[To be completed by the site owner: the time limit for automatically deleting videos and reference images after a job completes (see also the Storage section in the Privacy Policy).]

7. Payments

  • Payment is made by bank transfer. We do not collect or store card information.
  • Transaction notifications from SePay are authenticated with an API key. The system compares keys in constant time, so the key cannot be guessed from response timing.
  • Credits are added only when a transaction matches the order and the transfer note. Unmatched transactions are reconciled manually.

8. Abuse prevention

Some actions are rate-limited to prevent automation and probing attacks:

ActionLimit
Creating a credit top-up order5 times per minute per account
Updating profile and settings20 times per minute per account

These limits are currently a basic layer of protection and are counted separately on each processing server. As infrastructure scales, we will move to a shared counter.

9. Browser protection

The website sends the following security headers to protect you while you browse:

HeaderEffect
X-Frame-Options: DENYPrevents other websites from embedding this page in a frame, protecting against clickjacking
X-Content-Type-Options: nosniffThe browser does not guess file types, reducing the risk of content run under the wrong type
Referrer-Policy: strict-origin-when-cross-originLimits the page address information sent to other websites
Permissions-PolicyTurns off access to the camera, microphone and geolocation for the page
Strict-Transport-Security (HSTS)Requires the browser to use HTTPS for the domain
Content-Security-Policy (under monitoring)Restricts sources of scripts, connections and resources. Currently in report-only mode; it will be enforced after alerts have been reviewed

10. Secret keys and configuration

  • Secret keys (database service key, payment API key, AI model access key, link signing key) are stored only in environment variables on the server.
  • AI model keys and processing keys are held on a separate worker server, and are not included in the website source code or sent to the browser.
  • If a key is suspected to be compromised, we revoke it and issue a new key immediately, then update the configuration on the relevant servers.

11. Your role

You can help keep your account safe by:

  • Protecting your sign-in email inbox with a strong password and two-factor authentication.
  • Not sharing sign-in links sent by email with anyone, including people claiming to be support staff.
  • Signing out when using a public or shared computer.
  • Not putting sensitive information (identity documents, account numbers, passwords) into prompts or uploaded images.
  • Contacting us immediately if you see unfamiliar transactions or activity in your account.

SONNESTRA staff will never ask you for your email password, two-factor codes, or to transfer money to a personal account.

12. Reporting vulnerabilities

If you discover a security vulnerability, please report it to us before publishing it. Email hotro@sonnestra.vn, with a subject line starting with "[Security]". Contact information is published according to the standard at /.well-known/security.txt.

To help us reproduce the bug quickly, please describe:

  • The location of the bug (page path or API) and the steps to reproduce it.
  • The impact you believe could occur.
  • Do not access, modify or delete other people’s data when testing. Stop immediately if you see data that does not belong to you.

[To be completed by the site owner: response time for security reports, commitment to credit reporters, and the conditions for good-faith security research.]

13. Incident response

When we detect an incident that may affect data, we contain and fix it, review its cause, and notify affected users with instructions on the steps to take, such as changing your sign-in email or signing out of all devices.

[To be completed by the site owner: the incident notification procedure and deadlines for the competent authority and users under current regulations (Decree 13/2023/NĐ-CP).]

System & Account Security - SONNESTRA