Draft

Privacy Policy

This draft describes the Phase 1 Intry account only. It is written so a reviewer can see what the software actually does.

NEED CONFIRMATION — legal review

This is a draft for the Intry Phase 1 product. It is not finished legal text. It does not name a legal entity, postal address, regulator, or certification, because none of those were supplied. Do not treat this page as binding until someone who can speak for the operator reviews it.

Who operates Intry

NEED CONFIRMATION. The legal name, postal address, and contact role of the operator are not recorded in this repository. Do not invent them. Until they are added, the product name “Intry” is only a name for this software.

What this release does

Phase 1 lets a person sign in with Google, see the name, email, and avatar Google returns, save a timezone preference, and delete that account. It does not read, store, or send email.

Data the app stores

Supabase auth user id created when you sign in.
Email address returned by Google for that account.
Display name returned by Google, when Google provides one.
Avatar URL returned by Google, when Google provides one. The image itself is loaded from Google.
A timezone preference, defaulting to UTC. A digest hour column exists and is left empty.
A session cookie set by Supabase Auth so you stay signed in.

Data this release does not store

Email bodies, subjects, headers, labels, or attachments.
Gmail OAuth tokens. Sign-in uses openid, email, and profile only.
Payment details. There is no checkout.
Analytics events. Cloudflare Web Analytics is not installed.

Google sign-in

Sign-in is Google OAuth through Supabase Auth. The scopes requested by the app are openid, email, and profile. Gmail scopes are intentionally absent. Google’s own processing of the sign-in is covered by Google’s terms, which the operator must link or describe after review. NEED CONFIRMATION.

Services the code is built to use

These are implementation choices, not a signed list of subprocessors. The operator must confirm the legal entity names and any data-processing terms before launch. NEED CONFIRMATION.

Supabase, for authentication and the Postgres database that holds the profile and preferences.
Cloudflare Workers, for hosting the app.
Google, for the sign-in identity only.

Legal basis and regions

NEED CONFIRMATION. This draft does not claim a GDPR, UK GDPR, CCPA, or other legal basis, and it does not name a representative or a supervisory authority. If people outside the operator’s home country can sign in, the operator has to decide which rules apply before this page is published as policy.

How long data is kept

Profile and preference rows stay until the account is deleted or the operator removes the Supabase project. There is no separate retention schedule. NEED CONFIRMATION before launch.

Deletion

The account page can delete the Supabase auth user. Profile and preference rows reference that user and are removed with it. Deletion needs the server service role key. If that key is missing, the button stays off and nothing is deleted. This does not delete the person’s Google account.

Children

Intry is not directed at children. The minimum age is NEED CONFIRMATION and is not stated as a legal rule here.

Changes

When Gmail access or an assistant is added, this draft is out of date and must be rewritten before those features are offered. Phase 2 is not described here as if it already happens.

Contact

A support address has not been assigned in this repository. See the contact page. NEED CONFIRMATION.