Privacy notice

Last updated 2026-10-18.

What this is

The Redaktis portal (redaktis.com) is where an organisation, or one person, creates an account, gets a plan and seats, and receives the licences that switch Redaktis on. Redaktis itself, the browser extension and the coding-agent tools, hides personal and company details before they reach an AI chat service. It never sends us the text it protects, the values it hid, or the AI conversations. This notice covers the portal, the extension and agent as they deal with us, and the Manager when we host it for you.

What we hold about you

• Your account: your email address (proved to us before the account exists), which sign-in methods you use (Google, Microsoft, GitHub, emailed codes, or a password) and the identifier those providers give us (for GitHub, its numeric account id), and when you created the account and last signed in.
• Sign-in secrets, if you choose them: a password is kept only as a salted one-way hash (strengthened with a secret that is not in the database); an authenticator app's secret is kept encrypted, and your recovery codes only as one-way hashes. We cannot read any of them. We also keep short-lived counters of wrong passwords and codes per email address (up to a day) to slow down guessing, and we email you a notice when a password or the authenticator changes. A browser you have signed in with gets a random cookie, and we keep a one-way hash of it with your email address (until 180 days after its last sign-in), so that someone else guessing at your address cannot shut you out of that browser.
• Your organisations: each organisation's name, who belongs to it and with which role, invitations (to an email address, open for 14 days), its plan and seats, and every licence we issued to it.
• An activity log for each organisation: what changed, when, and the email address of the person who did it. Sign-ins and sign-outs are also recorded against your email address.
• Usage totals: when an organisation's Manager reports back, we hold one organisation-wide count of use and the number of active installations. These are kept in a separate database from the contact details above, under the organisation's internal number, with no email address or name. They are not anonymous: for a person who buys for themselves, the total can be linked to their account through that number.
• Installations: when a browser or coding agent activates on its own (the free plan or a trial), we hold a random install id, the version, the plan it was given, and a name for the computer only if the person typed one. A Manager registered with the portal is held under an id with the number of seats given to it.
• Payments: for each payment, the organisation's internal number, the plan, seats and dates, the amount and GST, an internal id of the person who paid (not their name or email), and Razorpay's order and payment references. For your GST tax invoice we also keep the billing details you give us (the name and address to invoice, your state and, if you have one, your GSTIN); they are deleted with the organisation, but the invoice itself, which carries them, is a tax record and is kept like the payment record. When you go to pay we send Razorpay the amount, our reference for the payment and the email address of the person paying (to fill in its page); Razorpay is the payment provider and keeps the records of the payment, its refunds and disputes under its own privacy notice. Card and bank details are entered on Razorpay's page and never reach us. If a payment is refunded or disputed, Razorpay tells us and we note it against the payment record. Payment records are kept [period, to be set by the lawyer] for tax law, even after the organisation or account is deleted, because the law requires it.
• Technical records: our web server keeps short-lived logs (time, address visited, internet address of the visitor) to keep the service secure and to find faults. They are kept for [number] days.

The extension and the agent on your computer

The text you type or paste, your files and the AI's replies are checked on your computer. The extension talks to us (or to your organisation's Manager) only to activate, to renew its licence, to fetch its organisation's policy and protected-document fingerprints, to download the optional detection model (from the organisation's Manager only) and, where an organisation uses a Manager, to send counts. If your organisation's policy treats work and personal accounts differently, the extension reads the email shown by the chat site on that page, on your computer, to tell which it is, and does not store or send it.

If we host your organisation's Manager

When an organisation uses the hosted Manager (manager.redaktis.com), we also hold, for that organisation only and kept apart from other organisations: its installs (random ids, versions, last contact, and a name or number an administrator gave them, never an email address), counts per day, per site, per kind of account (work, personal or unknown) and per kind of item hidden (for example "4 names"), never the items themselves; the policies its administrators publish and their history; the fingerprints of protected documents (hashes, document names and word counts, never the text); its administrators' email addresses with an audit log of what they did; and the sealed key that signs its policies. Because we host it, we hold that signing key; it is stored encrypted under a master key kept apart from the database. Counts are kept for 365 days unless the organisation sets less. An owner can download everything held about the organisation and can delete it.

What a self-hosted Manager tells us

A Manager run by an organisation on its own systems keeps its counts, policies and signing key there, and they never reach us. Once a day it checks in with the portal to renew its licence, sending only: its installation id, a rolling connection key, the number of active installs, its version, one organisation-wide usage total, the licence it holds, its clock and a one-time number. No employee data, text or file names. The people who sign in to a self-hosted Manager (their email addresses, password hashes, authenticator secrets and recovery-code hashes, or the sign-in account they use) are kept in that Manager's own database and never reach us.

What we do not hold

• The text you or your colleagues type or paste, files, the values Redaktis hides, or replies from AI services.
• Anything about the individual people whose browsers or tools Redaktis protects, beyond the install records above: a Manager reports totals, not people. (An organisation's own administrators can see more in the Manager they run; that is theirs, not ours. On the hosted Manager we hold only an employee name, device name or number if the administrator enters one, never an email address.)
• Your password, or the codes your authenticator app makes, in any form we could read. Redaktis staff can see that an authenticator is on, never its secret.

Why, and who else sees it

We use this only to run your account and licences, to keep the service secure, and to stop one person taking repeated free trials [the legal basis for each use, to be set by the lawyer]. We do not sell it and we do not use it for advertising.

Others who handle it for us: the company that hosts the portal in India [hosting provider], the service that sends sign-in codes by email [email provider], Google, Microsoft or GitHub when you choose to sign in with them (they know you signed in to Redaktis; we receive your email address and an identifier; from GitHub we ask only for your account id and your primary, verified email address, and we do not keep the access token it gives us), and Razorpay, the payment provider (it receives the amount, our payment reference and the paying person's email address). Records of payments we must keep for tax law are held by the payment provider (Razorpay) and in the portal's payment records and our accounting records [period].

How long we keep it

• Your account until you delete it. Sessions end after at most 12 hours. Sign-in codes work for 15 minutes. Your password hash, authenticator secret and recovery-code hashes are kept until you remove them or delete the account; counters of wrong tries are removed within a day; a remembered browser 180 days after its last sign-in, or at once when your password is reset.
• An organisation's records, including its activity log and licence history, until the organisation is deleted.
• Free trials: to stop repeated trials we keep a one-way fingerprint of a simplified form of your email address (capital letters, dots and "+" tags removed), which cannot be turned back into the address, for 12 months, even after you delete your account. It is not linked to your account or organisation.
• Usage totals until the organisation is deleted.
• Hosted Manager data: counts for 365 days (or the organisation's shorter setting), the rest until the organisation is deleted. Deleted data leaves the live system at once and our backups after at most about 21 days (server snapshots can hold it for up to 7 more).

Your choices

• See what we hold: "Your account" has a download of your data.
• Delete your account: "Your account" deletes it for good. Organisations that only you belong to are deleted with it. If you are the only owner of an organisation that others belong to, you first make someone else an owner, or delete the organisation. Where the activity log of another organisation has to stay, your email address and number in it are replaced by a stand-in that cannot be traced back to you.
• Delete an organisation: an owner can do it under "Organisation settings": members, invitations, plan history, licence history, activity log and usage totals are erased. Licences already issued cannot be called back: each keeps working on its installation until its own end date. We do not give refunds.
• Correct or ask something else: write to [privacy contact address]. [Grievance officer and response time, to be set by the lawyer.]

Where it is kept and how it is protected

In India [region]. Connections are encrypted. The database files are readable only by the portal's own account, backups are encrypted [to be confirmed at launch], and we tell the people affected and the authorities if there is a breach, as the law requires [process to be written].

Changes

If this notice changes in a way that matters, we will say so on the portal before it applies.