# Tilkly Privacy Policy

Plain-text mirror of https://builder.tilkly.com/privacy. Last updated July 27, 2026.

## Data Controller

- EI Jyoti SINGH (entrepreneur individuel)
- 169 Avenue de Grande Bretagne, 31300 Toulouse, France
- SIREN: 104 629 845 · SIRET: 10462984500017
- Hosting: Hostinger VPS, Paris, France
- Privacy questions: privacy@tilkly.com

## What Tilkly Collects

- Account data: email address, optional profile details, authentication/session data.
- Site content: pages, blocks, media, generated text, and settings users add to their sites.
- Abuse reports: reported URL, category, description, optional reporter email, and hashed reporter IP for moderation.
- Contact form submissions on published sites: visitor-submitted data, privacy acknowledgement metadata, optional marketing opt-in, and hashed IP for abuse prevention.
- CRM data: contacts, companies, deals, tasks, activities, tags, consent and opt-out details, source identifiers, sync status, retries, and errors.
- Usage counters: resource counts and rolling-window timestamps for pages, media, bandwidth, forms, support, Store products, analytics, and CRM capacity.
- Support and feedback: request type, subject, message, status, account reference, and timestamps stored in the in-app queue.
- Security and audit logs: IP address, action, and timestamp for authenticated actions.
- AI-generated content data: prompts submitted to AI features are sent to Google Gemini API; raw prompts are not stored in the shared cache, while recent account-scoped history may be kept briefly to support workflow.
- Payment data: Stripe handles card details. For AI credits and voluntary support contributions, Tilkly receives payment references, amount, currency, product type, status, and session identifiers.
- Stripe Connect account data: Stripe account ID used to route creator payments and apply Tilkly's 1% platform fee.

## How Tilkly Uses Data

- Authenticate accounts and secure sessions.
- Host and publish user websites.
- Deliver forms, domains, payments, AI features, support, moderation, and abuse prevention.
- Send essential OTP, security, legal, and account-deletion messages. Tilkly does not process form alerts, lifecycle marketing, or CRM outbound email.
- Improve product reliability with aggregated or anonymized usage patterns.

## AI And Google Gemini

Tilkly AI features use the Google Gemini Paid API. Tilkly states that prompts sent through paid API usage are not used to train Google's models. Users should avoid personal, sensitive, or confidential information in prompts.

## Payments And Stripe

Stripe is Tilkly's payment processor. Stripe handles card data directly. For AI credits and voluntary support, Tilkly receives the references needed to reconcile the purchase. For creator payments through Stripe Connect, the site owner is the merchant of record, Tilkly routes the payment, and Tilkly deducts a 1% platform fee.

## Published-Site Forms

For forms on a user's published Tilkly site, the site owner is the data controller and Tilkly acts as processor. Site owners are responsible for having a legal basis and privacy notice for their own visitors.

## Cookies And Analytics

Tilkly uses first-party cookies for authentication, preferences, CSRF protection, and consent. First-party analytics on published sites are consent-gated and collected via server logging, not additional analytics cookies. Site owners may add GA4 to their own published sites, also gated by analytics consent. Tilkly does not load third-party advertising scripts on Tilkly marketing, policy, dashboard, or published-site pages.

## Sub-processors

Includes Cloudflare (CDN/R2), Hostinger VPS (Paris), Google Gemini API, Backblaze B2, Stripe, and Spaceship (Spacemail for OTP and approved security, legal, or account-deletion notices).

## Retention

- OTP codes are short-lived.
- Form submissions follow the retention periods described in the rendered Privacy Policy and related feature policies.
- CRM data is retained while the account is active or until deletion, subject to legal requirements. At 250 contacts, source linking may pause while source records and retry status remain available.
- Support records are retained while needed to handle requests and prevent abuse, then deleted or anonymized under the support retention schedule.
- Rolling usage counters are kept long enough to enforce published windows. In-product analytics history is limited to 90 days.
- Security and audit logs are kept for security and compliance needs.
- Users can request access, correction, export, or deletion of personal data.

## Rights And Contact

Users may request access, correction, export, deletion, restriction, objection, or withdrawal of consent where applicable. Contact privacy@tilkly.com for privacy requests and support@tilkly.com for general support. Users may lodge a complaint with their local EU supervisory authority; in France, contact the CNIL at cnil.fr.
