Privacy Policy

1. Who we are

FutureContent is a content intelligence service operated by Future CX (Martijn van Deel), registered with the Dutch Chamber of Commerce under number 86444042. Future CX is the controller for account, service administration, security, and business contact data described in this policy.

When a business customer submits page content that contains personal data for analysis, that customer decides why the data is processed. In that situation, the customer is normally the controller and we act as its processor to provide FutureContent.

2. Data we handle

Account and identity data

We handle your email address, account identifier, authentication method, and session information. If you choose Google sign-in, Google provides the basic profile information you authorize: your Google account identifier, name, email address, and profile image.

Workspace and service data

We handle workspace names, membership and role information, website hostnames and labels you add, submitted page URLs, and the settings and results associated with your use of the service.

Technical and communication data

Our systems and service providers may process IP address, browser and device information, request timestamps, security events, and essential session cookies. If you contact us, we handle your message and contact details so we can respond.

Usage analytics data

We use narrowly allow-listed first-party events to measure whether a capability-checked Guest Scan result was viewed and whether that same browser claimed it during a successful registration within 24 hours. The same private system also measures committed Page Scan lifecycle outcomes using Scan State, complete, Partial Result, or Failed outcome, plan class, Evaluation Version, and a bounded duration range. It also counts successful Share Link creation, the first capability-checked opening, and revocation. User-initiated Rescans are measured separately from retry, recovery, and result refresh, with comparable same-version results represented by bounded overall and Assessment Score changes and a fixed improvement classification. Events record only allow-listed classes, server time, bounded numeric facts, and generated pseudonymous keys where needed during the raw retention window. They do not record page URLs, referrers, route parameters, submitted content, findings, recommendations, excerpts, provider payloads, free-form diagnostics, names, email addresses, raw account, Page Scan, Workspace, or Share Link identifiers, full IP addresses, Share Link tokens or digests, Guest capabilities, or advertising and cross-site identifiers.

We also use Vercel Web Analytics to understand general page visits, referrers, approximate location, device type, operating system, and browser. Before an event is sent, we remove query parameters and fragments and replace Guest, account Scan, and Share Link identifiers in page paths. Vercel Web Analytics does not use analytics cookies or associate page-view data with a full IP address.

3. Why we use data

• To create and secure your account, authenticate you, and maintain your session.
• To provide workspaces and the page-analysis features you request.
• To operate, troubleshoot, protect, and improve the service, including preventing abuse.
• To answer support requests and send service messages such as sign-in links.
• To comply with legal obligations and enforce our Terms.

We rely on performance of our contract when data is needed to provide the service, our legitimate interests in keeping the service secure and improving it, and compliance with legal obligations where applicable. Where the law requires consent, you may withdraw it at any time without affecting earlier processing.

4. Google user data

FutureContent uses Google OAuth only to let you create or access a FutureContent account. We request the minimum identity scopes: openid, email, and profile. We use the returned identifier and profile information only to authenticate you, link the sign-in to your FutureContent account, display your basic profile, prevent fraud, and support your account.

FutureContent does not request access to Gmail, Google Drive, contacts, calendars, or other Google product content. We do not use or separately retain Google OAuth access or refresh tokens, sell Google user data, use it for advertising, or allow humans to read it except when needed for security, support you at your request, or comply with law. Google identity data is shared only with the service providers and in the limited circumstances described below.

5. Service providers and sharing

We use the following suppliers to operate FutureContent:

• Vercel: Application hosting, serverless execution, security, and Web Analytics. It receives Application requests and page-view dimensions with query strings, fragments, and object identifiers removed.
• Supabase: Authentication, database, and realtime service infrastructure. It receives Account, Workspace, service, and authentication data.
• Google PageSpeed Insights: External performance and Lighthouse analysis of a public page. It receives The submitted public page URL.
• OpenAI API: Moderation and structured content analysis. It receives A normalized analysis document derived from the fetched page, not the fetched HTML.
• Google sign-in: Optional account authentication. It receives The openid, email, and profile identity scopes authorized by the User.
• Resend: Transactional authentication and Workspace invitation email. It receives Recipient and sender addresses, message content, and delivery metadata.
• hCaptcha: Abuse prevention on authentication and Guest Scan requests. It receives Browser, device, network, and security-check interaction data.

The fetched HTML is held only while the requested analysis runs and is discarded after analysis. OpenAI receives the normalized analysis document rather than that HTML. OpenAI does not use API inputs or outputs to train its models by default.

Semantic results retain only bounded excerpts needed to explain an artifact or finding: no more than 240 characters per excerpt, three references per item, and 12,000 aggregate excerpt characters per Page Scan after deduplication. Copied excerpts expire after 90 days or earlier when the Page Scan or Workspace is deleted. After expiry, the retained rubric output can keep its source field and location but not the copied text.

We do not retain full raw HTML, the full normalized page, unrestricted prompts, raw provider or model responses, credentials, refusal text, /llms.txt file bodies, linked-resource bodies, screenshots, traces, or unbounded diagnostics. External citation checks use safe bounded retrieval to establish technical resolvability only; they do not verify factual truth or source reputation.

These providers process data under their own terms and, where applicable, our data-processing arrangements. We may also disclose data when required by law, to protect users and the service, or as part of a business reorganization with appropriate safeguards. We do not sell personal data or share it for cross-context behavioural advertising.

6. International transfers

Some providers may process data outside the European Economic Area. When required, we use an adequacy decision, the European Commission's Standard Contractual Clauses, or another lawful transfer safeguard.

7. Retention

We keep account and workspace data while your account or workspace is active. We delete or anonymize it after it is no longer needed to provide the service, resolve disputes, meet legal obligations, or protect the service. Security records, support correspondence, and backups may remain for a limited period based on their operational or legal purpose. Google profile data follows the same account-retention criteria and is not kept for an unrelated purpose.

• Unclaimed Guest Scans: 24 hours from Guest Scan creation.
• Free Scan History: 30 days after completion.
• Failed Page Scans: 7 days after failure.
• Abandoned Page Scans: 7 days after the Scan was started or created.
• Temporary operational diagnostics: 7 days after it was recorded.
• Data-governance run records: 7 days after the governance run.
• Copied semantic evidence excerpts: 90 days at most, or earlier with Page Scan or Workspace deletion.
• Bounded origin-level /llms.txt evidence: cached for 24 hours; file and linked-resource bodies are not retained.

Raw product analytics events expire no later than 90 days after the server-recorded event time. We retain only low-dimensional daily totals after expiry; those totals contain no Guest pseudonym or Share Link, Page Scan, User, Workspace, Website, URL, or content identifier.

As verified on 11 August 2026, FutureContent's Supabase projects use the Free plan and expose no scheduled-backup or point-in-time recovery restore points. Historic database recovery is available only when an explicitly maintained operator-owned logical dump exists. Any future provider physical backup or point-in-time recovery copy restores the database as a whole and cannot be selectively edited through the provider's supported restore controls. If an older copy is restored, normal service remains unavailable while current retention and deletion controls run again.

You can permanently delete your Account from Settings after recent authentication and exact Account-ID confirmation. You must first delete or transfer every Workspace you own. Deletion removes your Auth identity and sessions, profile, Workspace memberships and preference, addressed invitations, and personal analytics association. Shared Workspace records remain, and aggregate product metrics remain only without an Account association.

8. Security

We use access controls, encrypted connections, row-level data isolation, and operational safeguards intended to protect personal data. No online service can guarantee absolute security, so please protect access to your email and Google accounts and notify us about suspected misuse.

9. Your rights

Depending on your circumstances, you may ask us to access, correct, delete, restrict, or provide a copy of your personal data, or object to processing based on legitimate interests. You may also complain to the Dutch Data Protection Authority. We may need to verify your identity before completing a request.

10. Cookies

FutureContent uses cookies and similar storage that are necessary for authentication, security, Guest Scan access, and keeping the service working. Our first-party events and Vercel Web Analytics do not use analytics cookies. We do not currently use advertising cookies.

11. Children

FutureContent is a business service and is not directed to children. You must be at least 18 years old to create an account.

12. Changes and contact

Business customers can also review our Data Processing Agreement and current Subprocessors.

We may update this policy as the service or legal requirements change. We will change the date above and provide additional notice when a material change requires it.

For privacy questions or requests, email m.van.deel@futurecx.nl. You can also identify us using Chamber of Commerce number 86444042 or VAT number NL863969379B01.