Privacy Policy

Effective October 20, 2026

This policy covers Unify’s public website and beta waitlist. The app is in development. Joining the waitlist does not connect your university account, create an app account, or upload coursework.

Who to contact

Unify is an independent academic-planning project. The founder operates this website and waitlist. For privacy questions, access, corrections, deletion, or to stop beta emails, contact founder@unifyapp.dev from the address you used to sign up.

What this website collects

• Waitlist: your email address, signup timestamp, an internal random identifier, the version of your consent, and a “landing” source label. The form requires your agreement to receive beta access and availability emails.
• Spam protection: the signup endpoint reads the network address supplied by Cloudflare and hashes it with the current hourly time window. The database stores that hash, an attempt count, and an expiry time. It does not store the raw address. Hashing reduces exposure; it does not make this information anonymous.
• Hosting: Cloudflare processes requests to deliver and protect this site, including technical request information such as network address, browser information, and requested URL under its own policies.
• Analytics, if enabled: Cloudflare Web Analytics measures aggregate visits and page performance. The site is prepared for it but does not load its beacon unless it is enabled for the deployment. The signup form does not send email addresses or form contents to analytics. Cloudflare’s privacy policy explains its processing.
• Contact: if you email us, we receive your message and sender details through the business email service.

How we use it

We use waitlist information to manage beta invitations and send beta availability updates. We use technical information to run the website and limit abuse. We do not sell waitlist information, use it for targeted advertising, or send it to AI model providers. We do not ask for your student password, Canvas token, grades, or payment details on this website.

Where it is stored and shared

Signup records are stored in a separate Cloudflare D1 database. Only the website’s signup function and authorized account operators should have database access. The public endpoint accepts signups but cannot list subscribers. The waitlist is separate from the app’s Supabase database. Hosting and email providers process data as needed to provide their services; processing may occur outside your country. We may also disclose information when required by applicable law.

Retention and your choices

We intend to keep a waitlist entry for no longer than 12 months after signup, unless you separately agree to a new purpose. Automated cleanup runs on valid signup requests; operators also need to run the documented monthly cleanup when traffic is low. Rate-limit records expire at the end of their hourly window and are removed during later valid signup requests or maintenance. Provider backups and operational logs may remain for their applicable retention periods.

You can request a copy, correction, or deletion of your waitlist record, or withdraw email consent at any time by emailing founder@unifyapp.dev. We may verify control of the address before acting. Rights depend on your location; you may also contact your local data-protection authority. Removing yourself from the waitlist does not affect processing already carried out.

Cookies and browser storage

This website does not set advertising cookies, create a sign-in session, or save signup information in local storage. The optional Cloudflare Web Analytics beacon is designed to operate without analytics cookies. Cloudflare’s security services may use technical mechanisms if configured by the operator. Fonts and product graphics are served from this website.

How the future app differs

The current app implementation uses Supabase for account authentication and academic records. Depending on features enabled at beta launch, records can include courses, assignments, deadlines, imported document text, source evidence, and updates. The Canvas Companion implementation stores an import credential and queued approved coursework locally in the browser. Live Canvas origins are currently disabled.

Optional model-assisted document extraction uses Anthropic when enabled and is off by default in the implementation. The current academic briefing itself is rule-based. These app features are not activated by joining this website’s waitlist. We will provide app-specific disclosures reflecting the deployed configuration before collecting academic data through the beta.

Audience and changes

The waitlist is intended for university students aged 18 or older. Please do not submit another person’s email address. If we learn that a child has submitted personal information, we will take steps to remove it. We may update this policy as the beta develops; the effective date above identifies the current version. Material changes to the use of signup information will be communicated before that new use.