Luvia Logo
Luvia FORMS
Data Protection & Privacy Commitment

Privacy Policy

Effective Date: August 28, 2026 • Last Updated: August 28, 2026

1. Overview & Privacy Philosophy

At Luvia Universal OS ("Luvia", "We", "Us"), privacy is not an afterthought or a secondary compliance setting — it is engineered directly into our core cryptographic foundation.

This Privacy Policy explains how Luvia collects, processes, and protects information across the Luvia Universal Ecosystem (including luvia.page, forms.luvia.page, pix.luvia.page, and account.luvia.page). Whether you are a Form Owner creating intake surveys, an elector voting in a secret ballot, or a respondent submitting an encrypted confession, we respect your data sovereignty.

2. Privacy Commitments Across Our Four Form Modes

How your data is handled depends strictly on the mode configured by the Form Owner:

Mode 1: Standard Forms & Intake

Submissions are stored in encrypted Cloud Firestore databases. Form Owners control field definitions and access response data. Standard telemetry (submission timestamps) is recorded to provide form analytics to the owner.

Mode 2: Cryptographic Verifiable Elections (Secret Ballot)

Identity Detachment: Voter credentials (Google SSO, token, or whitelist) are authenticated to issue a single-use voter token, but the vote choice is detached from voter identity upon submission.

Voters receive an auditable cryptographic receipt proof (0x...) to verify inclusion in the tally. It is mathematically impossible for Luvia, Form Owners, or auditors to map a voter's identity back to their candidate choice.

Mode 3: Live Polls & Quizzes

Poll answers are aggregated in sub-second memory streams via Cloudflare Durable Objects. Individual voter identities are never published on presenter screens or live stream feeds.

Mode 4: Zero-Knowledge Vault Encrypted Anonymous Submissions

Client-Side WebCrypto Encryption: Responses are encrypted on the respondent's device using public-key cryptography before network dispatch. Luvia servers store only unreadable ciphertext blobs and store zero decryption keys.

  • Zero IP Address Logging: Respondent IP addresses are stripped at the Cloudflare Workers edge.
  • Browser Telemetry Scrubbed: User-Agent strings, viewport metrics, and micro-timestamps are auto-scrubbed to render correlation attacks impossible.

3. Data We Collect & How We Use It

We collect minimal data necessary to deliver and secure our services:

  • Account & Auth Metadata: Email address, display name, user ID, and OAuth tokens provided via Google SSO or email sign-in for account creation.
  • Form Configuration Data: Questions, field types, theme tokens, and logic rules created by Form Owners.
  • Billing & Subscription Data: Payment transaction references, plan status, and billing email managed securely via Paystack or Paddle. (Full credit card numbers never touch Luvia servers).
  • Privacy Analytics: Anonymized, cookieless pageview telemetry collected via Bigdelta SPA analytics to monitor platform performance without tracking users across external sites.

4. Third-Party Data Processors

We rely on industry-certified infrastructure providers who adhere to strict security and privacy standards:

  • Cloudflare Inc.: Edge worker execution, DDoS protection, D1 database storage, and Durable Objects WebSocket streams.
  • Google Cloud & Firebase: Authentication services, Firestore database hosting, and FCM v1 Push Notification delivery.
  • Paystack & Paddle: PCI-DSS Level 1 certified payment processing and subscription billing.
  • Meta WhatsApp & Telegram APIs: Webhook processing for respondents opting to complete forms directly inside messaging applications.

5. Data Retention, Portability & Deletion Rights

Under applicable data privacy regulations (including GDPR, CCPA, and international standards), you maintain full control over your personal data:

  • Export Rights: Form Owners can export form configurations and submission data in JSON or CSV formats at any time.
  • Deletion Rights: Deleting a form permanently purges all associated responses and field definitions from our primary Firestore and D1 databases.
  • Account Erasure: Account termination purges your profile data, workspace membership links, and API access keys.

6. Cookies & Local Storage Policy

Luvia Forms does NOT use cross-site tracking cookies or third-party ad retargeting scripts. We utilize essential browser technologies strictly for functionality:

  • SessionStorage / LocalStorage: To store active theme choices (Dark/Light mode) and maintain local guest modal preferences.
  • Essential Auth Cookies: Secure, SameSite=Strict HTTP-only cookies to verify authenticated login sessions across Luvia micro-apps.

7. Security Controls & Global Transfers

All data in transit is encrypted using TLS 1.3 Strict, and data at rest is encrypted using AES-256.

8. Contact & Data Protection Officer

For privacy inquiries, data subject access requests (DSAR), or compliance questions, reach out to our Data Protection Officer at:

privacy@luvia.page • dpo@luvia.page