Galivox · account policies

Privacy Policy

How Galivox handles account information, eligibility, security, support, and local Frame editing.

Version 2026-10-22-us-free-beta-2 · Effective October 22, 2026, on publication

All account policies

1. Who this policy covers

This notice describes galivox.com, shared Galivox accounts, the proposed Frame free beta, support and existing test billing. The operator is Galivox INC, Connecticut, United States, as confirmed by its owner. Contact: galivoxinc@gmail.com.

Frame edits selected projects, media, captions, proxies, waveforms, exports and recovery files on your device or selected drive. Account checks exchange identity and access status, not editing content. Local folders may separately synchronize through iCloud or another service you choose. Unfinished features and the eligibility rollout below are not represented as already available.

2. Information we collect

  • Account information: your email address, name or display name, account identifier, verification status, sign-in provider, and account creation and update dates. Company information is optional.
  • Authentication information: password verification records, sign-in sessions and tokens, confirmation and recovery requests, and authenticator enrollment and verification information if you enable two-factor authentication. Supabase Auth stores password hashes rather than readable passwords. Credentials you enter are sent to the authentication service to verify them.
  • Profile and preferences: an optional profile photo, theme color, language, and notification choices. The uploaded photo is cropped and converted to PNG in your browser before that version is stored privately. Your device’s time zone is displayed from your device; it is not a saved account preference.
  • Security and technical information: account events and their timestamps, browser user agent, platform, and device category. Our infrastructure providers also receive request information such as IP address, requested URL, and browser details when they deliver and protect the service.
  • Billing information: when you open billing tools, your account identifier links to a Stripe customer. Stripe receives the billing name, email, address, optional phone number, and payment information you provide. Galivox retrieves subscription status, billing dates, invoice summaries and links, and limited saved-card details such as brand, last four digits, and expiry. Current billing is test-only; use test payment details.
  • Support information: the messages, contact details, screenshots, logs, and files you choose to send to us. Please remove passwords, recovery keys, full card numbers, and unrelated personal information before sending support material.

3. If you choose Google sign-in

Google and Supabase exchange the identity information needed to sign you in, including your Google account identifier, email address, name, and profile information made available with that permission. We use this information to create or connect your Galivox account.

The current Google sign-in flow does not request access to Gmail messages, Drive files, contacts, or calendars. Your Google password is entered with Google, not in Galivox’s password form. You can review Galivox’s connection in your Google account settings; removing that connection is separate from deleting your Galivox account.

4. How we use information

We use the information above to create and maintain accounts, authenticate users, save account settings, show security activity, deliver account emails, provide support, prevent misuse, and operate and reconcile billing. We use service and error information to diagnose failures and keep the service working.

Optional product-update email choices are off by default. Product and optional billing mailings are not active yet. Saving a preference does not start a mailing. Account confirmation, password recovery, security notices, and required service or transaction messages are separate from marketing preferences.

Where data-protection law requires a legal basis, account and requested service operations are performed to provide the service or contract; security and troubleshooting rely on legitimate interests, subject to your rights; legal recordkeeping relies on applicable obligations; and optional marketing, when introduced, requires the appropriate permission. We do not treat reading this policy as blanket consent.

5. Service providers and other disclosures

We share information needed to run the service with these providers:

  • Supabase provides authentication, account database storage, private photo storage, and server functions.
  • Resend delivers account emails and processes recipient addresses, email content, and delivery information.
  • Google provides optional Google sign-in and handles messages sent to our Gmail support inbox.
  • Stripe provides the current test checkout, saved payment methods, invoices, and billing portal. Stripe also processes some information for its own security, legal, and payment-service purposes.
  • Website hosting, DNS, and software delivery providers process the requests needed to load pages, images, and authentication software. For example, the account pages load the Supabase browser library from esm.sh, which receives a network request when that software loads.

Our current account service does not sell personal information, share it for targeted advertising, or use account information or support files to train an AI model. We may disclose information when legally required, to address fraud or security incidents, or to protect people’s rights. If a business transfer affects account data, the recipient must be informed of the applicable privacy commitments and users will receive notice where required.

Provider links describe their practices; they do not replace Galivox’s responsibility for its own use of your information. Information you deliberately share through an external service is also subject to that service’s rules.

6. Browser storage and tracking

The account service uses browser local storage for authentication sessions and tab session storage for account navigation, pending confirmation hints, and temporary Google or Frame sign-in state. These support sign-in and account continuity. Clearing storage can sign you out or interrupt a pending sign-in. Signing out clears account UI state; closing a tab clears its session storage.

The reviewed website code contains no advertising pixels, behavioral advertising, or added analytics trackers. We do not currently change account behavior in response to a browser’s Do Not Track signal. Hosting, authentication, Google, or Stripe may use their own logs, cookies, storage, and security tools when their services are contacted. This statement is not a claim that those providers never collect technical information.

7. Retention and account deletion

Account and preference records remain while your account is active. The current account activity history has no automatic age-based deletion schedule; it remains linked to the account until account deletion. You can replace or remove your profile photo.

The account deletion flow removes the account, linked active profile and preference records, stored profile photo, account activity, and sessions. The current test billing cleanup also removes the linked test customer and Galivox’s test billing records. If deletion cannot finish, the account is blocked from normal use while cleanup is retried rather than being reported as successfully deleted.

Galivox follows an owner-approved manual support procedure: remove support attachments and downloaded copies 30 days after the request is resolved, and ordinary support correspondence after 180 days. Keep a minimal privacy-rights, correction or appeal decision record for 24 months after closure, without raw birthdays, ID scans, authentication secrets or unnecessary message copies. An applicable request or deadline may require earlier action. A necessary legal/security hold is documented, purpose-limited and reviewed every 90 days. These schedules do not delete your projects or original media and are not an automated mailbox purge.

Deletion from the active account system does not instantly remove copies from backups, infrastructure logs, delivered email, or records a provider must retain for legal or security purposes. Those systems have separate retention rules. You can request review or deletion of support material by email. There is no claim here that every provider copy disappears immediately or on a fixed unverified timetable.

Live payment record retention will be documented before live billing starts. When live payments become available, legally required transaction records may need to remain after account deletion. Deleting a Galivox account does not delete your Google account or files on your computer.

8. Your controls and requests

In Account → Profile, you can update your display name, company, photo, language, theme, and optional email choices. In Account → Security, you can manage email, password, two-factor authentication, sessions, and account deletion. Current test billing tools are in Account → Billing.

For information you cannot manage there, email galivoxinc@gmail.com with “Privacy request” in the subject. Depending on the law that applies, you may request access, a copy, correction, deletion, restriction, or portability of your information; object to certain processing; withdraw optional consent; or complain to your privacy regulator. Exercising privacy rights does not result in a penalty.

The owner-approved manual procedure aims to acknowledge privacy/account-rights requests within seven calendar days and resolve them within 30 days of receipt, honoring any shorter applicable deadline. These are response targets, not a guarantee to fix every software bug within 30 days. Urgent child-privacy and security concerns receive priority. These targets are manual operating commitments, not automated inbox handling.

We may ask you to confirm account ownership before disclosing or changing personal information. Do not send a password, authenticator code, setup key or ID scan in an email. If you cannot access your account, contact support to discuss verification; an email request alone does not bypass two-factor authentication. A guardian’s verified withdrawal link stops their Frame approval; it does not provide access to the teen’s account or media.

If we refuse a privacy request, reply to the same contact with “Privacy appeal” and your case reference. We reassess the request and explain the decision, including any required regulator route. We do not claim that an independent reviewer handled an appeal when that did not occur.

9. Security, location, and your media

Account controls include verified sign-in, optional authenticator-based two-factor authentication, server-side ownership rules, private profile-photo storage, and session revocation. No internet service can guarantee absolute security. Keep your credentials and offline authenticator setup key private.

Our providers operate internationally, so account, delivery, support, and payment information may be processed in countries other than your own, including the United States. This notice does not promise storage in one country or claim an unverified international-transfer certification.

The reviewed account and billing code does not upload Frame projects, timelines, source media, or exports. Signing in or making a test subscription does not give us access to those files. A file or screenshot you intentionally email to support is shared with support. Any future cloud upload or desktop telemetry feature needs a separate disclosure before it collects data.

10. Eligibility and younger users

The approved coordinated rollout limits shared signup, including Google, to people age 13 or older. New accounts must complete the age declaration and email-verification process. Frame users aged 13–17 require separate guardian approval. Under-13 signup and Frame access are excluded. A neutral birth-date entry precedes requesting signup email information. The server independently checks UTC calendar dates, treating February 29 as March 1 in a non-leap year. At 18, guardian approval is no longer required. No identity-document upload is requested.

The eligibility service uses a date of birth transiently. Its private records keep an adult-category date or a teen’s 18th-birthday date, which can reveal a birthday and remains personal information. It also keeps an account identifier, declaration/agreement times and document versions, guardian email and attestation/approval/decline/withdrawal state/times, hashed email-link capabilities and abuse counters. These data are not placed in public profile metadata. Guardian review shows the requesting account email, not its password, projects or videos.

Raw capability links are processed by the recipient’s browser and mail providers delivering the message body; the eligibility database stores hashes, not raw capabilities. Do not forward approval or withdrawal links. Qualified synthetic service mail had no tracking pixel or rewritten capability link; that is not an assurance about inaccessible provider copies or every future message.

Signup links expire in 30 minutes, guardian invitations in 48 hours, receipt withdrawal links in seven days and fresh withdrawal links in 30 minutes. Expiry denies use, not physical deletion. The cleanup design removes requests a day after expiry, abuse counters after two days and minimizes the birthday-derived date after adulthood. An hourly job can take until the next successful run to remove a newly purgeable record; failures or delays need operator follow-up. Current account-linked eligibility, approval and review records cascade with account deletion. Delivered mail, provider logs and backups have separate limits; no universal instant-erasure deadline is promised.

Supabase hosts private eligibility records; its inspected primary database is East US (Ohio), us-east-2. Its Free plan excludes managed project backups, not necessarily all provider copies. Resend delivers account mail using verified auth.galivox.com; published Resend information states US storage, 30-day email/log retention and seven-day backups. Google supplies optional sign-in and support Gmail. Cloudflare hosts/protects the site and supplies Turnstile; browser authentication loads its SDK from esm.sh. Providers receive necessary connection, identity or delivery information. Primary/sending regions do not mean all processing occurs in one country.

Email confirmation and attestation do not independently prove age or parenthood. Credible age or guardian concerns are reviewed rather than ignored because a checkbox was used. Guardians may request a verified withdrawal link. If the service is unavailable, that page provides the support contact. Previously verified offline access may persist for up to seven days after withdrawal; saving and recovery remain available. Contact galivoxinc@gmail.com for child-privacy concerns, age corrections or withdrawal help.

The private schema and eligibility endpoint are installed. Hourly cleanup and ten-minute failure monitoring are active; scheduled failure/recovery and alert delivery have been qualified in the isolated and main environments. Signup interception, guardian processing and Frame eligibility enforcement are enabled through the separately authorized coordinated rollout. Their actual composed journeys and the signed editor require qualification before customer invitations. Publishing this notice alone activates none of those access controls.

The private support-review process can hold Frame access during an age correction or guardian concern after activation. Its current review row stores account ID, an opaque case reference, bounded reason, hold state and time until account deletion. A verified correction resets prior agreement and guardian authority and requires fresh agreement and, for teens, fresh approval. An email alone does not authorize changing someone else’s account or bypassing MFA. Previously verified offline access can last up to seven days.

Cloudflare's Turnstile notice describes its processor role for protecting a site and its separate controller role for improving bot detection. Not all provider processing is solely on Galivox's instructions. Exact internal provider deletion deadlines are not invented here.

11. Changes and contact

This version is effective on publication on October 22, 2026. Future material changes get a new notice/version and appropriate notice or renewed agreement. A new optional data use requires its own applicable permission, not silent reuse of an old receipt.

Privacy questions and requests: galivoxinc@gmail.com. Related documents: Terms of Service and the separate bundled Frame privacy notice when the app is available. The Frame free beta does not adopt paid-service terms.