Privacy Policy
This policy is written in plain English and applies to your use of Inflozo. We may update it as the service evolves; we will communicate material changes before they take effect.
This policy describes the personal data Inflozo processes, why, and the rights you have over it.
Who we are
Inflozo is operated by Umang Kagathara, an individual proprietor based in Gandhinagar, Gujarat, India, who is the data controller for the purposes described below. For privacy questions or to exercise your rights, contact hello@inflozo.com.
Our role
We process personal data in different roles depending on the data:
- Controller for your Inflozo account, workspace membership, billing-account references, marketing-site analytics configuration, waitlist and contact data, and support communications.
- Processor / service provider for the Ghost content snapshots and project/theme data your workspace processes through Inflozo for its own site-building purposes.
- Independent controller for the security, audit, fraud and abuse prevention, and legal-compliance records we must keep to operate the service.
Data we process
- Account data: your email address, and session and device information used for magic-link sign-in and active-session management.
- Ghost connection secrets: the Ghost Content and Admin API keys you provide. Your Ghost API keys are encrypted at rest and are only ever used by server-side jobs — they are never exposed to client-side JavaScript.
- Content snapshots: the posts, pages, tags, authors, and site metadata Inflozo fetches from a connected Ghost site to render your designs.
- Project data: the themes, components, assets, comments, and version history you create in the builder.
- Billing data: handled by our payment provider as Merchant of Record; Inflozo stores only a reference to the provider’s record, not your raw card details.
- Security and usage logs: IP address, security/audit events, and product usage events used to operate and protect the service.
Lawful bases
Where data-protection law requires a lawful basis, we rely on:
- Contract: account creation, authentication, workspace and project operation, exports and deploys, support, and billing-account administration.
- Legitimate interests: security, abuse prevention, service reliability, audit logs, debugging, and product improvement using proportionate usage events.
- Consent: optional analytics, marketing or waitlist communications, and optional cookies or tracking, where consent is required.
- Legal obligation: tax and accounting retention, lawful requests, fraud prevention, and compliance records.
Subprocessors and service providers
We rely on the following providers to run Inflozo, each processing data only to provide its part of the service:
- Supabase — authentication, Postgres database, realtime, and related backend services.
- Cloudflare and Cloudflare R2 — CDN/WAF, object storage, and asset/export delivery.
- Fly.io — worker runtime for long-running backend jobs.
- Postmark — primary transactional email.
- Resend — transactional email failover.
- Sentry — error monitoring.
- Dodo Payments — primary Merchant of Record for paid billing.
- Paddle — fallback Merchant of Record.
- Plausible Analytics — privacy-friendly, cookieless aggregate marketing-site analytics.
Where data is stored
Inflozo is designed with an EU storage posture for primary databases and object storage. Some providers may process limited data outside the EU or India. Where that happens, we rely on provider contractual safeguards, data-processing terms, and security controls appropriate to the service.
Your rights
Subject to applicable law you can access, correct, export, or delete your personal data, and object to or restrict certain processing. You can export your project data and delete your account, after which we remove your data according to our retention schedule.
Retention
We keep account and project data while your account is active. After an account deletion request, backup purge is targeted within 30 days. Magic-link security logs are retained for 90 days, soft-deleted projects for 30 days, soft-deleted assets for 14 days, pre-migration backups for 30 days, and preview access logs for 30 days with hashed IP addresses. Billing and tax records are retained by the active Merchant of Record for 7 years. Change history and export artifacts follow the plan-based retention windows described in the product terms.
Cookies and tracking
Our use of cookies and any analytics is described in the cookie policy. Analytics and waitlist capture will only run after you have given consent where consent is required.
Contact
For privacy questions or to exercise your rights, email hello@inflozo.com.