Privacy policy

Privacy at Form303.

Form303 processes only the account, form, branding and response data needed to provide the service. Google provider access is handled server-side, stored encrypted rather than in plaintext, and limited to read-only Forms content and Drive metadata scopes.

Free during beta. Anonymous demo available.

Before

With Form303

Editorial Minimal Form303 theme representing careful data handling

01 Import without rebuilding

02 Brand every detail

03 Publish a memorable link

Information Form303 processes

Form303 may process your email address and account identifiers, workspace membership, imported form structure, saved presentation settings, uploaded brand assets, publication metadata and responses submitted to your published forms.

Anonymous demo editing is designed to avoid cloud writes. You need an email account to save a draft. Importing and publishing additionally require a connected Google identity.

Google account access

Form303 requests Google Forms body read-only and Drive metadata read-only scopes. The connection is verified server-side against the Google identity linked to the authenticated account. Provider tokens are not placed in the browser bundle and are not intended to be stored in plaintext.

Form303 uses Google access to retrieve forms the connected identity is authorised to access. It does not request write access to edit the source Google Form.

Uploaded assets and published forms

Logos and backgrounds are associated with the creator’s workspace. Published forms use an immutable revision containing the form schema and presentation references. Customer-published forms are excluded from the marketing sitemap and default to noindex, nofollow.

Responses

Published forms may accept anonymous submissions. If a form is configured to collect email, the respondent email is stored separately from question answers. Authorised workspace members can view responses and export them.

Service providers and security

Form303 relies on service providers including Supabase for authentication, database and server functions, Vercel for application hosting, and Google for authorised form access. Access controls, row-level security and server-owned mutations are used to limit data exposure.

Data requests

For a privacy request or question, contact brooke@techguider.com.au. This beta policy will be reviewed as retention, billing and account-deletion workflows are formalised.

Current limitations

Form303 is in beta and does not yet publish a self-service data deletion or retention console. Do not use the service for sensitive regulated information until its suitability for that use has been independently assessed.

Your form, only sharper

Bring the form. We’ll bring the finish.

Explore the anonymous demo first. Create an email account when you want to save, then connect Google when you are ready to import and publish.

Open the studio