Privacy Policy

01Scope of this policy

Phane Shane ("we", "the platform") operates the website at phaneshane.xyz and the account system used to request and receive product access. This policy applies to that website and account system.

Individual products may run as separate applications. Where a product processes data beyond what is described here, it will present its own notice before you use it. This policy does not describe the internal behaviour of products that are not yet publicly operational.

02Account creation and authentication

Accounts are created and authenticated through Supabase Auth. When you register with an email address and password, we process:

• your email address;
• a password, which is stored by Supabase Auth as a hash — we never receive or store your password;
• email verification status and the timestamps of account creation and updates;
• session cookies, which are HTTP-only and are not readable by scripts in your browser.

A profile record is created alongside the account. It holds your user identifier, email address, an optional display name, your role on the platform, and your account status.

We also record which versions of the Terms of Service and this Privacy Policy you accepted, and when. That record contains your user identifier, the document name, the version, a timestamp generated by the database, and whether acceptance came from the registration form or from a sign-in flow. It does not contain your IP address, a browser fingerprint, cookies, tokens, or any part of your password.

You cannot change or delete that record yourself while your account exists — it is the evidence of what you agreed to — but it is not kept forever: if your account is deleted, its acceptance records are deleted with it. We would rather lose the record than keep personal data about someone who asked to be removed.

03Signing in with Google

You may sign in with a Google account. In that case Google confirms your identity to Supabase Auth and provides basic profile information associated with that account — typically your email address, and the name and picture your Google profile exposes to applications.

We do not request and do not receive access to your Gmail messages, Google Drive files, contacts, calendar, or any other Google service. We cannot act on your Google account. Sign-in confirms who you are; it grants us nothing else.

Google processes the sign-in itself under its own privacy terms. You can review and remove the connection at any time in your Google account settings.

04Records created while you use the platform

Access requests

When you request access to a product we record your user identifier, the product, the request status, a reference code, any message you choose to include, the review outcome, any note written by the reviewer, and the relevant timestamps.

Manual payment administration

Payments are arranged and confirmed outside the application. What the platform stores is administrative workflow metadata: which request a payment relates to, its state, the amount and currency recorded by an administrator, a payment method label, an administrator reference or note, and the timestamps of each transition. We do not ask for and do not store card numbers, banking credentials, one-time codes, or full payment documents.

Entitlements

An entitlement records which product an account may use, its state, when access starts, and when it expires. Entitlements are the platform's authoritative record of access.

Access events

When an account attempts to launch a product, we record the decision — allowed or denied, the reason, the product, and the time. This exists so that access problems can be diagnosed and abuse detected.

Administrative audit records

Administrative actions such as approving a request, granting or revoking an entitlement, recording a payment transition, or changing an account status are written to an audit log together with the administrator and the affected account, including the email addresses involved so that attribution survives later account deletion.

05Operational logs and security monitoring

The server that hosts the platform keeps ordinary operational logs: web server access and error logs, application service logs, and system logs. These can include IP addresses, request paths, response codes, user agents, and timestamps. They exist to keep the service running, to investigate faults, and to detect abuse such as automated login attempts.

A local health check records service status, certificate expiry, resource usage, error counts, and the result of a database privilege audit. It records counts and statuses only — never request bodies, cookies, tokens, query strings, or email addresses.

06Encrypted backups

The database is backed up on a schedule. Each backup is compressed and encrypted with AES-256 before it is written to disk, is readable only by the service account that created it, and is retained for a limited number of generations before being removed automatically.

Backups necessarily contain the account records described above, because that is what a backup is. Backup restoration is tested against an isolated, disposable local database that is destroyed afterwards; restored data is never served to anyone.

07Service providers we actually use

• Supabase — authentication, the application database, and managed database backups.
• Google — only where you choose to sign in with a Google account.
• Hostinger — the business email service behind info@phaneshane.xyz. Anything you send us by email is processed there.
• Our virtual private server provider — hosting for the website, the application service, and the encrypted backups described above.
• Telegram — only if you choose to contact us on Telegram. Messages you send there are processed by Telegram under its own terms.

These providers operate infrastructure in more than one country, so your data may be processed outside the country you are in. We choose providers that offer authenticated access, transport encryption, and encryption of stored data, and we restrict who on our side can reach production systems.

08Why we process this data

• to create and authenticate your account, and to keep you signed in;
• to receive, review, and answer product access requests;
• to confirm a payment has been arranged and to record the resulting entitlement;
• to decide whether an account may open a product, and to record that decision;
• to keep an accountable record of administrative actions;
• to operate, secure, debug, and restore the service;
• to detect and respond to abuse, fraud, and security incidents;
• to answer your questions and support requests;
• to keep records we are required to keep, or that we need in order to handle a dispute.

We process this data because it is necessary to provide the service you asked for, to keep that service secure, and to meet obligations that apply to us. We do not sell personal data, we do not share it for advertising, and we do not use it to build advertising profiles.

09Who can see your data

Access to production data is limited to the platform owner and to administrators who need it to operate the service. Database row-level security restricts ordinary accounts to their own records: an authenticated account can read its own profile, its own requests, and its own entitlements, and nothing belonging to anyone else.

Administrative actions are recorded in the audit log described above. Administrators cannot act on accounts at or above their own level, and cannot suspend their own account.

10How long we keep it

We keep account records for as long as the account exists, and afterwards only for as long as we have a reason to: handling a dispute, investigating abuse or fraud, or meeting a record-keeping obligation.

Access requests, payment workflow metadata, entitlement history, access events, and audit records are retained as a history rather than overwritten, because they are the record of who was given access to what and on whose authority. Encrypted backups age out automatically on a fixed retention count, so a deletion propagates out of backups as older generations are removed.

11Security

We take security seriously and apply the measures we consider proportionate: server-side-only handling of database credentials, HTTP-only session cookies, transport encryption, row-level security in the database, least-privilege database grants that are audited automatically for drift, encrypted backups whose restorability is verified, and rate limiting on authentication endpoints.

No system is completely secure, and we do not claim otherwise. We cannot guarantee that data transmitted over the internet or stored by any provider is immune to every possible attack. Use a unique, strong password, and tell us promptly if you believe your account has been accessed by someone else.

12Correction, deletion, and questions

Write to info@phaneshane.xyz from the address on your account if you want to correct information, ask what we hold about you, ask us to delete your account, or raise a privacy concern. We will ask you to confirm control of the account before acting on a request.

Deletion has limits, and we would rather state them than surprise you. We can close an account and remove profile details, and your legal acceptance records are removed along with the account. We generally cannot remove records that exist for security, fraud prevention, dispute handling, or legal record-keeping — in particular administrative audit records, which deliberately retain the email addresses involved so that a past administrative decision remains attributable. Where a record must be retained, we keep it for that purpose only.

13Changes to this policy

We may update this policy as the platform develops. The effective date and version at the top of this page always identify the current document. Where a change is material, we will ask you to accept the new version the next time you sign in; earlier acceptance records are kept as they are and are never rewritten to suggest you accepted something you did not.

14Contact

Email info@phaneshane.xyz or message Telegram @phaneshane. See the contact page for which channel to use and what to include.