Skip to content
OverviewPricingDownload
Sign in

Privacy notice

Draft for review · 15 October 2026

This notice is an initial draft. Operator details and the support contact are still being finalized.

This notice describes the account service and planned desktop activity reporting for Spielberg945 Lite. Desktop activity becomes available only after the app integration is released.

Information the account service uses

We use your email address, account identifier, session information, and any profile details you provide to authenticate you and operate your account. If you create or join a company, we also store the company name, memberships, roles, and invitation records, including invited email addresses.

Activity collection

We retain monthly counts of successful project creations, files successfully imported locally, and terminal export outcomes. Counts are grouped by UTC month, account, personal or company context, and an opaque local project identifier. Export counts distinguish output types and successful, failed, or cancelled outcomes. A project-package or backup export is not counted as a rendered video; unknown export types remain unknown.

The API receives event identifiers, an app version, and reported event times to validate submissions and place counts in the correct month. Events may arrive up to 30 days after they happened, or have a reported time no more than five minutes ahead of the server. We do not retain an individual activity timeline. App opens, export starts, clicks, editing time, exported duration, and provider-token usage are not tracked.

Activity reporting does not collect footage, filenames, local file paths, prompts, transcripts, API keys, or raw error payloads. Imported-file counts describe local imports, not uploads. Activity is client-reported usage, not a live inventory of your files or a basis for financial billing. Counts can be incomplete if offline events expire or the app closes before an export outcome is observed.

Local editing and external services

Editing projects, media, and rendering remain on your computer. If you connect an external agent, voice, music, or other service, content you choose to send to that service is handled under its terms and privacy policy. This account service does not provide media storage.

Company agreement and payment records

For company agreements, we store subscription terms, monthly allowances, invoice and payment references, payment dates and amounts, prepaid credit entries, and reasons for administrative changes. Audit records include the administrator's account identifier and the submitted change. Company owners can view their company's financial records; authorized internal administrators manage them. We do not collect card or bank credentials. Managed-service usage and automatic credit deductions are not active yet.

Who processes information

Cloudflare hosts the website and application API. Supabase provides authentication and database services. Transactional email services deliver sign-in codes and company invitations. Company owners can view membership details and manage invitations for their company; they do not automatically receive platform-wide activity reports.

Sessions and security

We use a cookie to remember your language preference for one year.

The website stores authentication session information in your browser using the Supabase SDK so you can stay signed in. Sign out on shared devices. We restrict account and company access by identity and role, and internal reporting is limited to authorized administrators.

Retention and account requests

Monthly usage aggregates have no automatic expiry. We also keep limited retry receipts—identifiers, hashes of submitted data, and the minimum export metadata needed to prevent duplicate or conflicting counts. These receipts do not contain full event payloads. They expire 35 days after first acceptance and are removed by daily cleanup; retrying does not extend that period. Removing receipts does not reduce the monthly counts.

There is no self-service deletion control on the website. An administrator deleting an account removes its associated monthly aggregates and retry receipts. Leaving a company or being removed does not delete your account, its retained usage counts, or local project files. Administrative company deletion removes usage counts associated with that company.

Company financial records and their audit history currently have no automatic expiry. They remain after an administrator's account is deleted or company ownership changes. A company with financial records cannot be deleted through the current database flow. Corrections are recorded as additional entries instead of erasing payment history.

Contact and changes

The support profile is being finalized. The X support link is currently a placeholder, not an operational request channel. This notice will be updated as the service and its operational policies are finalized.

Spielberg945 Lite

A little closer to the cut you imagined.

Privacy · draftTerms · draftSupport on X ↗Support profile coming soon

© 2026 Spielberg945 Lite Made for the making.