Privacy information.
This notice covers the Saiph landing pages and launch-update signup. Read the separate account and billing privacy information for Auth0, Stripe and the development portal.
Visiting this website
These landing pages set no application cookies and load no external fonts, advertising scripts or embedded forms. Optional pageview analytics is described below; it is disabled in the prepared configuration. Vercel hosts the site and processes request metadata, including IP addresses and browser/request information, to deliver and protect it.
The purpose is website delivery, reliability and abuse prevention. The proposed lawful basis for this processing is legitimate interests in operating a secure website; the controller must confirm its assessment before the final notice is adopted.
Hosting retention:
Hosting locations and transfers:
See Vercel privacy information. A hosting region alone does not establish that all processing stays in that region.
Optional website analytics
Analytics is disabled. If enabled after notice review, Vercel Web Analytics measures public-page visits to help understand website use. It does not use analytics cookies. It processes page paths, referral information and browser/device information; Vercel also receives network metadata when requests reach its service. Cookie-free measurement does not mean no personal data is processed.
The integration allows only public informational pages, strips query strings and fragments from pageview URLs, suppresses custom events, and skips measurement when a referrer could disclose private paths or parameters. Account, login, callback and payment routes are excluded. No device identifiers, email addresses, account subjects, tokens or message content are deliberately added to analytics events.
The proposed lawful basis is legitimate interests in improving these informational pages, subject to the controller's assessment of necessity, visitor rights and applicable ePrivacy rules. Actual analytics retention, provider locations and transfer safeguards must be confirmed before activation. Vercel's visitor-hash lifetime is not the retention period for analytics reports. See Vercel Web Analytics privacy information. Changes requiring consent must be gated on consent before measurement starts.
Launch-update email
Signup is currently disabled. These pages do not collect email addresses or send launch emails.
What we collect: your email address, submission time, the consent checkbox response, consent-notice version and subscription status. The signup provider may process network metadata to prevent abuse; its notice describes that processing.
Purpose and lawful basis: consent to receive the Saiph launch announcement and occasional launch updates. Consent is optional and unrelated to purchases or account/device approval. The form requires your email and consent checkbox. This is single opt-in: no confirmation email is sent. Partial submissions are disabled.
Processor: . Provider privacy information.
Processing locations:
International-transfer safeguards:
Retention:
Withdraw consent or request deletion:
Email open/click tracking is disabled. A minimum unsubscribe/suppression record may be retained as described above to prevent further unwanted messages.
Selected signup provider: Tally
Tally acts as processor for form responses; the form creator controls their retention. Tally says form data is stored in Europe and lists Google Cloud hosting/storage in Belgium. Its optional form-email notifications use SendGrid in the United States. EU storage does not mean all processing stays in the EU. The actual enabled integrations and applicable transfer safeguards still need review before signup opens.
Tally describes a deletion window of up to 90 days for deleted form data and a separate manual Trash-emptying control. This notice does not promise that manually emptying Trash immediately purges every backup. This is the provider's deletion window, not Saiph's active-list retention policy, which remains unconfirmed. See Tally's privacy policy and GDPR and subprocessor information (reviewed 11 October 2026).
Contacting the controller
When the contact address is verified, sending an email shares your address, message and any details you include with the controller and its mail providers. Include only what is needed to answer your request.
Your choices and rights
Where applicable, you can request access, correction, erasure, restriction or portability of your data, object to processing based on legitimate interests, and withdraw consent without affecting processing that happened before withdrawal. Use the controller contact when it has been verified and published. Requests are normally answered within one month; if a lawful extension is necessary, the controller must explain it within that first month. Identity checks should be proportionate and limited to what is needed.
You can complain to the Irish Data Protection Commission or your local supervisory authority.
External links and future services
GitHub handles its own account and download requests. An email signup link opens the chosen provider's site only after you follow it. The Android beta invite link opens Google's Firebase App Distribution, which asks for your email address to send and manage your tester invitation; Google processes it under its own terms, and the controller sees your address in the beta tester list. You can ask to be removed from the beta at any time. Auth0 sign-in and Stripe billing belong to the separate development account portal; they do not run on these landing pages. No launch email data is used for device approval or content encryption.
Retention periods must match actual provider controls and deletion procedures. The account retention information distinguishes proposed policy from current development limits. The website hosting and contact-mail periods above remain unconfirmed; a draft is not a completed public notice.
A change of purpose, processor or tracking behavior requires an updated notice and, where needed, fresh consent. Paid Hosted remains subject to separate review and terms.