Muhammad Abdullah Rathore, operating Titan Omega. Contact: rathoreabdullah816@gmail.com. Written enquiries and data-subject requests go to the same address.
| Data | Why | Kept for |
|---|---|---|
| Email address | To create and identify your account. It is the only personal detail signup asks for. | Until you ask for the account to be deleted. |
| Password | To let you sign in. Stored only as a PBKDF2 hash with a per-account salt — the plaintext is never written to disk or logs and cannot be recovered, including by us. | Same as the account. |
| Websites you ask Titan to audit | To run the audit and show you the result over time. | Per your plan’s history window, then discarded. |
| Usage counts (audits run, AI calls made) | To enforce plan limits. Counts only — not the contents. | Rolling 30-day window. |
Titan sets no advertising or analytics cookies. Your session token is held in your own browser’s local storage so you stay signed in, and it is removed when you sign out.
Only the services needed to run the product: the hosting provider, and the AI provider that generates text when you request it. Prompts sent to an AI provider contain the content you asked Titan to work on. If that matters for a particular client, do not paste confidential material into those fields.
If you are in the EU/EEA or the UK you have the right to access, correct, export, restrict, object to, or delete your data, and to complain to your data protection authority. Everyone gets the same rights here regardless of where they live — email the address above and it will be actioned within 30 days.
Traffic is HTTPS-only and forced with HSTS. Passwords use PBKDF2 with 200,000 iterations. Founder-only data is separated from customer data at the API level and the separation is covered by automated tests that walk the live route table.
Material changes will be dated at the top of this page. Continuing to use Titan after a change means you accept it.