Privacy Policy
This policy explains what SurfStats Studio collects, why we use it, when data is sent to service providers, how first-party analytics and referrals work, and the controls available to you.
Last updated: 10 September 2026
Who this policy applies to
SurfStats Studio is operated by SurfStats Studio Software cc. This policy applies to the public SurfStats Studio website and the authenticated SurfStats Studio application. Questions, access requests, correction requests, objections, or deletion requests can be submitted through Support.
Some features rely on independent service providers. Their own privacy terms may also apply to information they process for the service you choose.
Plain-language commitment
Collect what is needed to run the product, explain material sharing, protect the service, and give users practical controls over their account and data.
The data categories used by the current product
| Category | Examples | Why it is used |
|---|---|---|
| Account & authentication | Name/display name, email, password hash for password accounts, confirmation status, login provider and external account identifier. | Create, authenticate, recover, secure and administer the account. |
| Workspace & collaboration | Workspace membership, role, invitations, client records, approvals, campaign/brand settings and collaboration activity. | Provide team, agency, client-review and role-based access workflows. |
| Creator content | Prompts, scripts, images, videos, audio, thumbnails, uploaded files, generated media, Characters, Worlds, Brand Kits, project settings and export/review data. | Store projects and perform the creative actions you request. |
| Voice & likeness material | Reference images, voice samples, consent recordings and related settings when you deliberately use character, likeness or voice-clone features. | Perform the requested character, voice or media workflow and retain the project where needed. |
| Billing & credits | Plan, product, transaction/subscription identifiers, amount, currency, status, credit ledger and checkout/refund events. | Provide subscriptions, top-ups, credits, refunds, reconciliation and fraud protection. |
| Support | Name, email, subject, message, IP address and browser/user-agent information submitted with a support request. | Respond to support, investigate problems and reduce abuse. |
| Referral & partner attribution | Campaign/referral code, referral type, landing path, referrer, IP address, browser/user-agent and later account/purchase attribution where applicable. | Attribute approved affiliate/recruiter referrals and reconcile eligible commission. |
| Usage & technical data | Page/CTA events, path, referrer, campaign/UTM fields, pseudonymous visitor/session IDs, viewport, authentication state, diagnostics, IP/server logs and security/audit events. | Operate, troubleshoot, secure and improve the user journey and product. |
How browser storage is used
SurfStats uses browser cookies or storage for account sessions, security, preferences, referral attribution, and first-party product/marketing analytics. We do not use a third-party advertising network on these pages.
- Essential/session storage: sign-in, security, anti-forgery/session behavior, active workspace/channel and user preferences required for the product to function.
- Referral cookies: when you arrive through a configured affiliate/recruiter campaign, SurfStats may store first-party referral code/type cookies for up to 60 days so a later signup or eligible purchase can be attributed.
- First-party analytics: SurfStats creates a pseudonymous visitor ID in
localStorageand a session ID insessionStorage, and records page/CTA events, paths, referrers and campaign/UTM fields. When you are authenticated, the stored analytics event may include a SHA-256 hash of the account email rather than the plain email address.
Disabling first-party usage analytics below does not disable essential sign-in/security storage or referral attribution that was created through a referral link.
First-party analytics choice
You can opt out of SurfStats page/CTA analytics on this browser. Opting out also clears SurfStats' analytics visitor, session and stored attribution identifiers from this browser.
Purposes of processing
Account & security
Create accounts, authenticate users, confirm email, manage roles, prevent abuse, investigate suspicious activity and protect the service.
Requested creative services
Store your project state and send the minimum practical prompt/media inputs to the selected provider or processing service needed to produce the requested output.
Billing & credits
Maintain subscriptions, top-ups, credit balances, refunds, provider-cost safeguards and FastSpring purchase reconciliation.
Product operations
Measure first-result and CTA journeys, troubleshoot failures, understand aggregate usage, improve navigation and support launch/quality decisions.
Collaboration
Let authorized workspace members, reviewers and clients see the shared records and assets appropriate to their role.
Legal & trust
Handle disputes, enforce terms, maintain audit/security records, comply with lawful requirements and protect SurfStats, users and the public.
When creator content leaves SurfStats
Many generation features cannot run entirely inside the SurfStats web application. When you request an AI, voice, cloud-media, billing, email, or similar provider-backed feature, SurfStats may send the prompt, selected files and necessary technical metadata to the provider used for that job.
Google services
Used for basic Google Sign-In and selected Google Cloud/AI services where enabled, including provider-backed image, video, text, storage or voice workflows.
Creative providers
Providers such as ElevenLabs and other configured AI/media services may process prompts or media only when you select or invoke a feature that needs them.
Commerce & infrastructure
FastSpring acts as Merchant of Record for paid purchases. Hosting, email, security and infrastructure providers may process the data needed to operate those services.
Voice, likeness & consent material
Some creator workflows can process a real person's face, likeness, voice sample or consent recording. Depending on the country and context, this material may be treated as sensitive or biometric-related information.
- Only upload a real person's image or voice when you have the necessary permission and rights.
- Voice-clone workflows may require an explicit provider consent recording.
- SurfStats uses this material to perform the feature you requested and to retain the related project/files where the workflow requires it.
- Do not use SurfStats to impersonate, deceive, harass or violate another person's rights.
Who can see creator content
Drafts and project records are not treated as public merely because they exist in SurfStats. Content can, however, be shared with people you authorize through workspace/client/reviewer workflows, or become public when an authorized workflow deliberately publishes or promotes it to a public showcase or external destination.
Workspace Owners and Administrators control member access. Creators, Publishers and Reviewers/Clients may receive different permissions. You are responsible for choosing appropriate collaborators and reviewing content before public release.
Basic identity access is separate from YouTube
Normal Sign in with Google requests only openid, profile, and email. SurfStats receives the basic identity information needed to authenticate the account, such as name, verified email and Google account identifier. Normal sign-in is configured with SaveTokens = false, so Google access/refresh tokens are not persisted after the external sign-in profile has been processed.
Normal Google Sign-In does not request YouTube channel, YouTube Analytics, upload, publish, edit or delete scopes. Any future Google/YouTube feature requiring additional scopes should use a separate explicit connection and consent step. See Google Access and YouTube Data Use.
Google API Limited Use commitments
- We do not sell Google user data.
- We do not use Google user data for advertising.
- We do not use Google API user data to train generalized AI or machine-learning models.
- We do not transfer Google user data except as needed to provide the requested feature, comply with law, or protect rights, safety and security.
- Human access is restricted to support, security, abuse prevention, legal compliance and cases where you ask us for help.
SurfStats Studio's use and transfer of information received from Google APIs will adhere to the Google API Services User Data Policy, including the Limited Use requirements.
FastSpring billing
FastSpring processes checkout as Merchant of Record. SurfStats receives the transaction/subscription metadata needed to activate plans, add credits, reconcile renewals/refunds and protect against fraud. SurfStats does not store full payment-card numbers on its own servers.
Affiliate/recruiter attribution
Configured referral links can create a 60-day first-party attribution cookie and server-side click/signup/reward records. These can include campaign code, landing page, referrer, IP address, user agent and the attributed account or eligible purchase.
Support & service messages
SurfStats may send confirmation, security, account, billing and support messages needed to provide the service. A support submission stores the message and basic anti-abuse/diagnostic information such as IP address and user agent.
We do not sell personal information
We may disclose information only when reasonably needed for:
- service providers that operate features you request, hosting, email, security, billing or infrastructure;
- workspace/client collaborators you authorize through SurfStats;
- legal obligations, valid legal process, fraud prevention, safety or enforcement of our rights and terms;
- a merger, acquisition, financing, reorganization or sale of business/assets, subject to applicable law and appropriate safeguards.
We do not disclose creator content to advertisers for targeted advertising, and we do not sell account or Google user data.
How long information is kept
Retention depends on the record and why it exists. Account and project data is generally retained while the account/project is active and as needed to provide the Service. Billing, refund, referral, security, audit, fraud-prevention and legal records may need to be kept longer when reasonably necessary or required by law.
Account deletion removes the account and stored application records targeted by the self-service deletion process and performs best-effort cleanup of user upload folders. Some information can remain temporarily in backups, infrastructure/security logs, provider systems, or records that SurfStats must retain for legal, accounting, fraud-prevention or dispute purposes. See Data Deletion for the current controls.
How information is protected
SurfStats uses reasonable administrative, technical and organizational safeguards, including authenticated access, role-based workspace permissions, password hashing, anti-forgery/session controls, webhook signature verification, abuse controls, server-side audit/security logging and restricted operator access.
No online service can guarantee absolute security. You should use a strong unique password, protect your email account, sign out on shared devices and report suspicious activity through Support.
Controls available to you
Delete account/data
Use the self-service account deletion process or review what it removes.
Deletion detailsGoogle revocation
Revoke SurfStats from your Google Account permissions independently of SurfStats.
Google permissionsAnalytics opt-out
Disable SurfStats first-party page/CTA analytics for this browser.
Analytics choicesAccess/correction request
If a self-service control is not available, ask us to review or correct personal information associated with your account.
Contact SupportOther legal rights
Depending on applicable law, you may have rights to access, correct, delete, restrict, object, receive a copy of data, withdraw consent, or complain to a privacy regulator.
Submit requestData may cross borders
SurfStats and its service providers may process data in countries other than the country where you live. Where applicable law requires it, SurfStats will take reasonable steps to use appropriate contractual, organizational or technical safeguards for international processing.
Not designed specifically for children
SurfStats is a general creator and business service and is not designed specifically for children. If applicable law requires a parent or guardian to consent to a minor's use of an online service, the account should not be used without that authorization. Contact Support if you believe a child's personal information was submitted inappropriately.
Keeping the policy current
SurfStats may update this policy as the product, providers or legal requirements change. The date at the top identifies the latest published version. Material changes should be reflected here rather than relying on older product descriptions.
Questions or requests
Use the public Support form for privacy questions or requests. For account-specific requests, include the email address used for the SurfStats account so we can identify the relevant records safely.