Privacy notice
Version 2026-10-23.3. The controller for personal data processed by SceneBeam is Jonas Risbrandt, a private individual in Sweden, Manskärsvägen 10, 388 92 Ljungbyholm. Privacy contact: support@scenebeam.app.
In short: we process the email address and purchase details needed to run your account, and nothing for advertising. Camera images and visitor positions are processed on your own computer and are never uploaded or stored by us.
1. What we process, why, and on what basis
- Account: email address, a hashed password if you set one, email confirmation, two-factor settings and recovery codes, account creation date and sign-in security data. Used to create your account, sign you in and protect it. Legal basis: performance of our agreement with you.
- Optional Google or Facebook sign-in: when you choose an available provider, we request your email address and basic profile. The provider may also return information such as your name. We store only your email address, the provider name and its unique account identifier for this connection in our account database; we do not save the returned name or profile picture there. This lets us create your account, recognise you on later sign-ins or connect the provider to an account you are already signed into. An existing account is never linked automatically just because the email addresses match. New accounts still require SceneBeam email confirmation. Legal basis: performance of our agreement with you. Email/password sign-in remains available.
- Purchases and access: product, price, currency, campaign, Paddle transaction ID, purchase and refund status, dates and the signed permission for offline playback. Used to give you access, handle refunds and support. Legal basis: performance of the agreement; our legitimate interest in reconciling payments and handling claims for the limited payment references retained after deletion.
- Emails we send: account confirmation, password resets and messages about your account or purchases. Messages in our delivery queue are encrypted and retained for the limited periods in section 6. Legal basis: performance of the agreement.
- Support: what you write to us and our replies. Used to help you and handle complaints. Legal basis: performance of the agreement and our legitimate interest in answering questions.
- Security: your IP address is used briefly in server memory to limit repeated requests and is not stored. Administrator actions on accounts are recorded in an audit log. A limited erasure register prevents deleted accounts from being brought back during recovery. Legal basis: our legitimate interest in keeping the service and your account secure.
We never receive your Google or Facebook password. Provider access and refresh tokens are used only as needed to complete sign-in and are not saved for later API access. We do not request access to your inbox, contacts, calendar or friends, and do not use sign-in data for advertising, sale or AI model training. Sign-in data is used only for account and security functions described here; our hosting, email and encrypted backup services process the relevant account data as described below.
2. Data that stays on your device
Installation settings, calibrations, configurations, prepared offline files and offline permissions are stored in your browser (local storage, IndexedDB and the service worker cache). They are not sent to us. The camera picture is analysed in your browser to detect visitors; images, detections and positions never leave your computer.
3. Cookies
We use only strictly necessary cookies: scenebeam.session keeps you signed in, and an anti-forgery cookie protects forms. They are not used for analytics or advertising, so no consent is needed. When you open the checkout, Paddle loads its own script, which may set cookies under Paddle’s privacy policy.
If you choose social sign-in, short-lived cookies protect the redirect to the provider and temporarily hold the authentication result until sign-in is completed. These are necessary for that sign-in method and may temporarily contain the profile claims returned by the provider. Google or Facebook handles sign-in on its own site and may use its own cookies under its privacy policy. SceneBeam does not load their sign-in flow until you choose it.
4. Who receives data
- Google / Meta: if you choose their sign-in method, the selected provider receives the sign-in request and learns that you are signing into SceneBeam. It authenticates you and returns the requested account information. Google and Meta process data for their own account and sign-in services under their respective Google privacy policy and Meta privacy policy. Choosing this sign-in method does not send your SceneBeam purchase history, camera data or prepared shows to them.
- Paddle (Paddle.com Market Ltd, United Kingdom) is our reseller and Merchant of Record. Paddle receives your order details and processes payment details, billing address and tax information as an independent controller under its privacy policy. We never receive your card details.
- Netcup GmbH (Germany) hosts our servers and database in Germany.
- Resend (Resend, Inc., USA) delivers the emails we send.
- Cloudflare (Cloudflare, Inc., USA) provides DNS and forwards mail sent to our support address, which is delivered to a Google Gmail mailbox (Google Ireland Ltd).
- Cloudflare R2 stores encrypted backups in a private bucket with EU jurisdiction. The backup decryption password is kept separately.
- Professional advisers, such as an accountant, and authorities when the law requires it.
Hosting, backup and email delivery services process data for operating SceneBeam. Paddle acts as an independent controller for its payment services. Provider terms and data protection arrangements govern each service; providers may also have independent legal and security responsibilities. We do not sell personal data.
5. Transfers outside the EU/EEA
Resend, Cloudflare, Google and Meta may process data in the United States. Such transfers rely on the EU–US Data Privacy Framework or the European Commission’s standard contractual clauses. Transfers to Paddle in the United Kingdom rely on the Commission’s adequacy decision for the UK.
6. How long we keep data
Automatic cleanup runs approximately hourly while the service is operating. The periods below are our retention limits, not general GDPR deadlines. A service interruption may delay cleanup; it resumes when service is restored.
- Account data and access rights: while your account exists. Account deletion removes sign-in credentials, linked sign-in methods, access rights, queued emails to your address and account-related administrator audit entries from the live database.
- Purchases: retained with your account to provide access and purchase history. Uncompleted checkout attempts without an access entitlement are deleted after 90 days. On account deletion, the account link and purchase recovery secret are removed immediately. Remaining payment references are deleted after 90 days to allow late payment notifications and refund reconciliation. These references are not described as anonymous: Paddle transaction IDs may still identify an order.
- Email queue: sent messages are deleted 30 days after sending; unsent messages are deleted 30 days after creation, even if delivery has failed. This concerns our queue, not your inbox or the delivery provider’s independent systems.
- Paddle notifications: deleted 90 days after processing. Notifications that cannot be processed are deleted 90 days after receipt.
- Support correspondence: reviewed manually each month and deleted when no longer needed, normally no later than two years after the last contact. An ongoing complaint or legal obligation may require specific correspondence to be kept longer; access is restricted and the need is reviewed.
- Erasure register: a one-way hash of the random account ID and deletion time is kept for 63 days to reapply deletions when restoring a backup. It contains no email address or password and is used only for recovery and verifying erasure.
- Encrypted backups: normally kept for at most eight weeks. Cleanup runs daily and removes expired snapshots and unreferenced data blocks. Failures can delay cleanup and require operator action. Backups are isolated from ordinary use; when restoring an older copy, we reapply later known account deletions and overdue cleanup before reopening the service.
The app database is not our accounting archive. Where accounting or tax law requires particular financial documents to be retained, those documents are kept separately for the applicable statutory period. Paddle is independently responsible for its own payment and customer records; deleting a SceneBeam account does not delete those records.
The provider connection is kept while your SceneBeam account exists. Deleting the account removes the connection from our live database; the backup rules in section 6 still apply. You can also revoke SceneBeam access in your Google or Facebook account settings. Revoking access there does not delete your SceneBeam account or purchases. Deleting your SceneBeam account does not delete your account with the provider.
7. Your rights
You have the right to access your personal data, to have it corrected or erased, to restrict or object to processing, and to receive data you have given us in a portable format. You can delete a regular account yourself from Account; for an administrator account, contact us so erasure can be handled securely. Account deletion does not automatically remove support correspondence or independent provider records. Contact us for requests covering those records. For other requests, contact support@scenebeam.app. We answer within one month.
If you think we handle your data incorrectly, you can complain to the Swedish Authority for Privacy Protection (IMY), imy.se, or the supervisory authority where you live.
8. Security
All traffic uses HTTPS. Passwords are stored as salted hashes, queued emails and payment notifications are encrypted, administrator access requires two-factor authentication, and the database is not reachable from the internet.
9. Changes
We publish updated versions here with a date and version number. For material changes, we provide the additional information required by law, for example in the app or by email.