Privacy notice.

Last updated: 1 September 2026. COMPSMART LTD is the controller for account, marketing, billing and platform-security information. When a customer uses FutureHost forms or an app to collect information from their own visitors, that customer is normally the controller and FutureHost acts as its processor.

1. Information we process

• Account and authentication: name, email, password hash or Google identifier, verification state, sessions, security events and sign-in metadata.
• Workspace and sites: prompts, conversations, files, generated content, versions, published pages, runtime logs, encrypted secrets metadata, database allocation and backups.
• AI account and usage: wallet and top-up ledger entries, task state, selected provider and model, token or image counts, provider cost and customer charge. A personal OpenRouter key is encrypted and write-only; we retain a keyed fingerprint, masked label, validation status and observed account limits, but never return the saved key.
• Usage and support: storage, errors, moderation signals, knowledge-base searches, assistant questions and answers, source citations, answer feedback, contact requests and human support correspondence.
• Billing and domains: plan, currency, subscription status, payment-provider references, checkout consent, domain searches/orders and encrypted registrant contact details. FutureHost does not store complete card details.
• Customer-site data: form fields chosen by the customer; visitor-member email addresses, display names, invitations, status and essential sessions; appointment attendee details, times, status and email-verification records; and cookieless aggregate page/referrer totals. Hosted analytics does not store visitor IP addresses, cookies, user-agent strings or visitor identifiers.

2. Purposes and lawful bases

• Provide accounts, workspaces, hosting, email, subscriptions, domains and support — contract or steps requested before a contract.
• Secure tenants, prevent abuse, diagnose errors, measure capacity and improve reliability — our legitimate interests in a safe, effective service.
• Keep tax, payment, consent and domain records and respond to lawful requests — legal obligation.
• Send optional product marketing — consent where required; you can withdraw it at any time. Service and security notices are not marketing.
• Process a customer’s hosted forms, app data and email — the customer’s documented instructions under our service contract.

We do not use solely automated decisions that produce legal or similarly significant effects about customers. Automated abuse signals may restrict activity, with human review available where practical.

3. Who receives information

We use vetted service providers only where needed: infrastructure and email providers; Stripe for subscriptions and AI-credit payments; Google for Google sign-in, Gemini Live voice and consent-based Google Analytics; OpenRouter to route coding, document and image requests to the model selected in the workspace; OpenAI for source-backed support answers; Cloudflare and registry/registrar partners for domains, DNS and delivery; Meta for FutureHost-owned Facebook and Instagram publishing, insights and comment moderation when Social is enabled; Kie for approved Social image/video generation; and professional advisers or authorities where legally necessary. AI requests include the prompt and bounded workspace or attachment context needed for the task. FutureHost requests disabled response storage and denies provider data collection where the route supports it, but OpenRouter, Kie and the selected model provider still process the request to return an answer or media. The support assistant sends the question, a small set of relevant published guides and limited signed-in account facts to OpenAI with response storage disabled; it does not send mailbox passwords or secret keys. Providers receive only information needed for their role and are bound by contracts or applicable provider terms.

4. International transfers

Some providers may process information outside the UK. Where UK adequacy regulations do not apply, we use an approved transfer mechanism such as the UK International Data Transfer Agreement or UK Addendum, together with proportionate security checks. Contact us for more information about safeguards relevant to your data.

5. Retention

• Unclaimed Try workspaces: up to 24 hours.
• Active site files and account data: while the account is active; paused site data is normally deleted after 90 days.
• Workspace conversations and private attachments: normally up to 90 days, or up to 24 hours for an unclaimed Try workspace; deleting a conversation removes its messages and private attachments from active storage.
• Version history, analytics and backups: the period shown for the effective plan, subject to safe rotation.
• Form submissions, visitor members and appointment records: while the site is active and for the site’s normal 90-day post-suspension recovery period, unless the customer deletes them or asks us to do so sooner. Site owners control individual member deletion and appointment management.
• Authentication and booking verification codes: 10 minutes operationally and then routinely cleared; delivered transactional-email bodies are cleared after processing. Member sessions last up to 30 days unless revoked.
• Personal OpenRouter keys: until removed; after a downgrade they are disabled and scheduled for deletion after 30 days.
• Expired sessions, one-time tokens and short-term rate-limit records: routinely cleared after they are no longer operationally needed.
• Social comments and Social Manager chat: up to 90 days. Unused generated Social candidates: up to 30 days. Published Social media and audit metadata: up to 25 months.
• Knowledge-base searches: up to 90 days. Human support correspondence and funnel records: normally up to 24–25 months.
• AI accounting, top-up, billing, consent, fraud and domain records may be kept up to seven years where required for tax, disputes or legal obligations. AI accounting records do not contain prompt or extracted-document content.

Backups rotate rather than deleting instantly; deleted information disappears from them as those copies expire.

6. Cookies, campaign attribution and local storage

FutureHost uses secure, host-only cookies for platform account sessions, Google OAuth integrity and—when a site owner enables native member accounts—an essential customer-site member session lasting up to 30 days. Member cookies keep a visitor signed in and enforce protected pages; they are not advertising or cross-site tracking cookies. Essential browser storage remembers your cookie choice, whether Nova has already greeted this browser or signed-in account, a temporary Try workspace, a pending claim, currency preference and access to the current support conversation. Analytics and Advertising are separate optional choices. Google Analytics measurement ID G-YGQEMLDG3W and its script are not loaded until you allow Analytics. If allowed, Google Analytics cookies and a short-lived anonymous FutureHost funnel token help us understand which pages, builder starts and later account stages are useful. Browser-level campaign attribution is retained only with Analytics permission. Separately, our web server counts requests to marketing, claim and Try pages without cookies or browser identifiers. These counts use the page path, response status and bounded campaign or ad labels from the URL. They record whether a Facebook click parameter is present, but not its value; no IP address, raw user-agent, cookie, full referrer or complete query string is retained in this measurement log. Known crawlers are counted separately. Request logs rotate after 14 days and daily totals are retained for up to 25 months. Campaign pages do not automatically open the cookie-choice panel; optional choices remain available in the footer. Platform click identifiers and advertising events are retained or sent only with Advertising permission; withdrawing it clears accessible click-attribution storage and disables future advertising delivery. Where a permitted email or similar identifier is used for server-side conversion matching, FutureHost hashes it before delivery. Choosing “Essential only” prevents analytics and advertising scripts and removes accessible measurement storage. You can change your choice at any time using “Cookie choices” in the footer. FutureHost’s analytics for customer-hosted websites remains cookieless and separate from FutureHost’s own campaign measurement.

7. Social content and community moderation

When an administrator enables Social, FutureHost processes public comments on FutureHost-owned Facebook and Instagram posts through a bounded Meta connector. Comments are sanitised, classified and retained with their platform identifiers; direct messages are not included. A restricted moderator may prepare a short response using approved FAQ excerpts, but every response requires administrator approval and is published exactly as approved. Comment links are treated as untrusted content and are not followed. Social media generation uses only FutureHost-owned demo material, permitted synthetic characters and references for which FutureHost has rights or consent. Customer workspaces and customer media are excluded.

8. Security

Controls include tenant separation, least-privilege services, TLS, password hashing, encrypted domain, runtime and Social provider secrets, write-only secret retrieval, rate limits, audit trails, health-checked deployment and retained recovery copies. No internet service can promise absolute security.

9. Your rights

Depending on the circumstances, UK data-protection law gives you rights to be informed, access, correction, erasure, restriction, objection, portability and withdrawal of consent. We may need to verify identity. Use the contact page and select Privacy or data rights, or email [email protected]. You can also complain to the UK Information Commissioner’s Office. Please contact us first if you can so we can investigate.

10. Children and changes

FutureHost is intended for people aged 18 or over and is not designed for children. We will post changes here and give additional notice where a material change affects how existing customer information is used.