KEYOUT Privacy Policy
Version: 2026-1. Effective: 2026-11-05.
This policy describes the launch service. KEYOUT operates from British Columbia, Canada. Contact the person responsible for privacy through the brand address support@keyout.app, with “Privacy” in the subject. KEYOUT is a trading name. This policy addresses information handling under British Columbia's Personal Information Protection Act (PIPA) and Canada's Personal Information Protection and Electronic Documents Act (PIPEDA), where applicable, including business across borders.
1. Information we collect
The personal detail required to sign in is your email address. There are no passwords. Sign-in uses a one-time email magic link. The service also handles:
What you enter: brick sets, sizes, names, colors, joint settings, personal stars, company names and contractor/manufacturer type, descriptions, ring chart details and approved-user email addresses. Do not enter another person's details without permission or a lawful reason.
Your CLOCKOUT records: dates, start and end times, breaks, work/night/travel type, distance, client and contractor names, notes and the name you choose for a timesheet. These are optional work records you choose to enter, not extra sign-up identity requirements.
Account and acceptance records: account type, account identifier, sign-in/session state, terms version, server time of acceptance and deletion or restoration requests.
Payment status: the product, whether paid, refunded or disputed, transaction references and related access status received from the payment provider. KEYOUT does not receive or store card numbers or card security codes; card details go directly to the provider's checkout.
Support messages: your email and the information you send when asking for help. Avoid sending unnecessary hours, confidential sets or payment details.
Hosting, authentication and email providers process the technical information needed to deliver and protect the service, such as IP addresses, request times, browser information, delivery and security logs. These are distinct from the information we ask you to type. We do not ask for a home address, government identification or a device's precise location for a KEYOUT account. The payment provider may collect its own billing information under its own privacy terms.
2. Why we use information
We use it to sign you in, keep your account secure, record agreement to terms, determine paid access, save and restore your sets and hours, calculate requested results, deliver approved sharing, answer support requests, handle refunds or deletion, and prevent abuse. Offline data is backed up in small batches when online. Finished calculation results for identical brick inputs may be reused without including account identity, names or hours in the reusable table.
We collect and use information for these stated purposes and seek any consent the law requires. Where consent is the basis, you may withdraw it by contacting support. We will explain the effect on the service; for example, without an email we cannot provide sign-in. Withdrawing consent does not cancel legal recordkeeping duties or automatically request a refund. We do not sell your personal information or use private sets or hours for advertising.
3. Who can see sets and hours
Your private sets and personal stars are private to your account through the app. Only a contractor or manufacturer can share a set, and only with emails on its approved-users list. Shared details include the company's name and type, set name, description, ring chart details, bricks and joint settings. Stars are not shared. There is no public set directory or public sharing. Companies should tell people before adding their email and use it only for this approved-sharing purpose.
An approved recipient can make a private copy. Copies cannot be shared on through the app. Removing approval or deleting the source prevents future access to that source but cannot recall copies already owned by recipients, printed sheets or downloaded files. Do not share information you lack permission to disclose. Company names are not verified at launch.
Only the worker can read CLOCKOUT hours through an account. A contractor or client named on a row cannot read them, and approving an email or sharing a set does not give access to hours. You decide whether to give someone your printed timesheet or spreadsheet. Service operators and processors may need restricted access for authorized operation, support, security or legal requirements; this is not a promise of encryption that hides records from the operator.
4. Providers and disclosures
We use service providers for specific purposes, with access limited to what their role needs:
Provider: Purpose and information handled
Supabase: Authentication, database and server functions; account, session, acceptance, sets, hours and access records.
Cloudflare: Hosting, delivery and protection of the public, auth and app sites; request/security information. Server-side aggregate traffic statistics cover the public site only; no browser analytics tracker is added.
Stripe Managed Payments / Link: Merchant of record: checkout, payments, taxes, receipts, refunds and disputes. The selected provider collects payment details directly and sends KEYOUT payment/access status and references.
AWS Simple Email Service (SES): Transactional sign-in email, including the recipient address, magic link and delivery information. Custom SMTP is configured for these passwordless account emails.
The merchant of record also has its own purposes and legal duties for transaction, tax and fraud records; read its checkout privacy policy. We do not present the fallback as an additional provider that receives every purchase. We do not send account data, private sets or hours to public-site analytics or add advertising trackers.
Providers may process or store information outside British Columbia or Canada, where other laws may allow authorities access. We remain responsible for our own handling of personal information and use appropriate contractual and security safeguards. The actual hosting regions, provider retention and transfers must be verified before publication. We may also disclose information where legally required or permitted to address fraud, security or legal claims, limited to what is needed. We do not promise anonymity from a valid legal requirement.
5. Security, your phone and exported files
Supabase encrypts stored data at rest, including CLOCKOUT hours. Connections to the service use encryption in transit. Database access rules restrict records to authorized accounts, including owner-only hours. Provider encryption is not end-to-end encryption: authorized infrastructure operators can access data as required for their duties. No system is completely secure.
The phone keeps saved sets, finished results and hours in browser storage so they work without signal, along with pending changes waiting to sync. Sign-in cookies/session information are needed for access; these are not advertising cookies. A sign-in lasts up to one year, with one active device at a time. Signing out or switching accounts clears that user's device data through the app's lifecycle. Keep the device locked and the email inbox secure; an offline device cannot receive an immediate remote deletion or access change until it reconnects.
Local browser storage is not promised to have separate application-level encryption. Downloaded spreadsheets and PDFs have no passwords or file encryption. Printing or emailing them creates copies outside KEYOUT's control. Protect those files and remove local copies you no longer need.
6. Retention, deletion and restoration
We keep account information, sets, hours and acceptance records while needed to provide the account, and limit operational records to their stated purposes. You can request deletion in the account controls or at support@keyout.app. We verify control of the account before releasing information or acting on an email request; never send us a password or sign-in token.
Deletion pauses access. Your account and its data, including your owned sets and shared source sets, hours, settings and acceptance records, are permanently deleted within 30 days of the request. You can re-enable the account any time before that permanent deletion runs within the period. Your email is removed from companies' approved-user lists. Permanent deletion cannot be undone. Restoring an account does not reverse a refund or create paid access.
Deleting your source set or account cannot delete a private copy another person already owns or recall printed or downloaded files. Reusable finished-result tables without account identity may remain. Reconnect devices so the app can apply the account change and clear user-scoped local data; remove exports and browser data yourself on devices you control. A device that stays offline cannot be remotely wiped by this service.
The merchant of record retains its transaction and tax records under its own legal duties. KEYOUT does not promise to erase records independently controlled by that provider. Provider backup deletion, logs and support-message retention must be confirmed before publication so the 30-day account-data commitment is supported in practice; this policy grants no indefinite backup exception to it.
7. Access, correction, complaints and choices
Contact support@keyout.app to ask what personal information we hold, how it has been used or disclosed, to request a copy or correction, to withdraw consent, or to request deletion. You can also correct your own saved sets and hours in the app. Describe the request without sending unnecessary sensitive details. We may verify identity in proportion to the request, explain any lawful restriction and respond within the deadlines required by applicable privacy law.
If you have a concern, contact our privacy contact first so we can investigate. You may also contact the Office of the Information and Privacy Commissioner for British Columbia about PIPA, or the Office of the Privacy Commissioner of Canada about PIPEDA, as applicable. Nothing in this policy limits your right to complain to a regulator.
8. Changes and contact
We will publish dated, versioned updates and explain material changes in advance. Where a change needs fresh consent, we will obtain it; publishing a policy alone is not consent to unrelated uses. The Terms of Use have a separate recorded acceptance process. Previous published versions remain available so you can see what changed.
Contact KEYOUT at support@keyout.app for privacy and data requests.