Account and billing privacy.

How the development account portal handles identity and sandbox billing, and what must be settled before public Hosted accounts open.

Who is responsible

Alexander Belik, operating as Abelik1, Ireland, is the controller for Saiph account administration. See contact details and their current status. The website notice separately covers landing pages and the optional launch-update list.

Sign-in and essential cookies

Auth0 (Okta) authenticates the account. Depending on the configured sign-in connection, it receives login details, an email address/profile and network, device and authentication-event information. A social identity provider may also process the login when that connection is enabled. The actual enabled connections, tenant region and provider log-retention settings need confirmation.

The portal requests the openid, profile and email sign-in scopes, but saves only the authenticated subject in its session user profile to verify its owner. It uses a secure, HTTP-only, host-only, SameSite Lax session cookie that is non-rolling, transient and expires within one hour. The sign-in flow also uses temporary transaction cookies. Auth0 maintains its own sign-in session and essential cookies on its domain; signing out locally does not erase provider records. These cookies support authentication, rather than advertising.

The proposed legal basis is taking requested steps to provide an account and, when available, performing the service contract. Login protection and abuse prevention rely on legitimate interests, subject to a documented assessment. An account cannot be provided without the authentication data needed to secure it.

Payments and subscription records

Stripe Checkout and its billing portal collect payment and billing details directly on Stripe's pages. Saiph's development handlers accept test-mode resources only; use only Stripe test payment details, never real card or bank details. The account application does not receive or store full payment-card numbers or security codes.

Saiph's billing database stores the Auth0 subject, Stripe account/customer/subscription/price identifiers, creation and observation times, subscription status, cancellation and billing-period dates, and a minimal event receipt used to prevent duplicate processing. Stripe metadata contains a derived account reference; hashing that reference does not make the linked billing records anonymous. Full webhook payloads are not stored by this billing schema.

The proposed bases are contract administration for requested billing, legal obligations for records that must be retained, and legitimate interests for fraud prevention, reconciliation and disputes. Stripe acts as processor for some merchant-directed activities and as an independent controller for its own regulated, fraud-prevention and other purposes described in Stripe's privacy policy. Cancelling a subscription, deleting an account and asking for a refund are separate requests.

Providers and international transfers

Auth0 supplies identity services, Vercel hosts the portal, Neon supplies its PostgreSQL database, and Stripe handles checkout, billing and payments. Mail providers process correspondence when a contact channel is configured. Authorized administrators may access records needed to run the service or answer requests; authorities and professional advisers may receive information where legally required or necessary for a dispute.

Actual hosting/database/identity regions, subprocessors, provider retention and any transfers outside the EEA must be recorded before public onboarding. A selected EU region alone does not establish EU-only processing. Confirm the applicable contracts and safeguards, such as a valid adequacy decision or standard contractual clauses with any required supplementary measures; do not assume a safeguard without checking it.

Provider references: Auth0 data processing, Okta privacy, Vercel privacy, Neon privacy and Stripe privacy.

Retention and account deletion

The current development portal has no self-service account deletion or automatic billing-record purge. Customer identity records are protected against deletion by the current database schema; a reviewed maintenance process is needed to erase or minimize them safely. Deleting an Auth0 user does not automatically erase Saiph, Neon, Stripe, support or backup records. Provider records have their own deletion processes and legal duties.

The proposed operational rules are: remove account/profile data within 30 days after account closure, security logs after 30 days, and resolved routine correspondence after 12 months. Retain only accounting records required by law for the applicable statutory period; Irish Revenue generally requires business tax records for six years. These are proposed policy targets, not deployed cleanup guarantees. Provider backup windows, specific accounting triggers, dispute holds and technical deletion steps remain to be approved and tested before these periods become a service promise.

A legal hold must identify its reason, narrowly scoped data, responsible person and review date. Records kept under a hold or statutory duty must be restricted to that purpose, then deleted when it ends. Closing a paid account must also address future renewal; erasure alone is not a cancellation mechanism.

Hosted content is a separate boundary

The account portal does not receive clipboard, message or file content, and successful payment or login does not approve devices or supply encryption keys. The isolated Hosted prototype can observe account/device identifiers, routing metadata, sizes and timing even where payloads are sealed. The ordinary self-hosted Hub can process readable content. Public Hosted retention, recovery, security and provider arrangements need a separate verified description before release; the prototype is not a reviewed production service.

Your choices and rights

Where applicable, request access, correction, erasure, restriction or portability; object to legitimate-interests processing; or withdraw any optional consent without affecting earlier lawful processing. Account and billing data are not added to the launch-update list without separate consent. No advertising or analytics is included in the development portal.

Use the verified controller contact once published. Requests are normally answered within one month; any lawful extension must be explained within that month. You may complain to the Irish Data Protection Commission or your local supervisory authority. Account authorization is automated access control; no credit or eligibility profiling is implemented by this account application. Stripe's own fraud and payment decisions are described in its notice.