Privacy policy
This page describes what AIPolicyTracker stores about you, why, how long it is kept and how to get it back or removed. It describes the system as it is actually built: the tables named here exist in the published source, and the repository can be read to check any claim on this page.
Last updated .
Who is responsible
AIPolicyTracker is operated by Dignep Group Pvt. Ltd.. That entity decides what is collected and why.
Requests about your data can be sent through the contact and contribution form.
Reading the site without an account
You can read every policy record, obligation, jurisdiction, change entry and guide without an account and without giving us anything.
- Page counts carry no identifier. The site counts how many times a path was viewed on a given day. That record holds a date, a path and a number, and nothing else. There is no visitor identifier in it, so there is nothing to attribute back to you.
- Analytics are off until you accept them. Where an analytics provider is configured, its script is not loaded until you accept the consent banner. Declining leaves it unloaded.
- No advertising, no profiling, no data sales. We do not sell or rent personal data, we do not run advertising, and we do not build behavioural profiles.
What an account stores
| What | Why |
|---|---|
| Name and email address | To identify the account, sign you in and send what you asked for. |
| Password | Stored as a one-way hash. It cannot be read back, by us or by anyone with the database. |
| Organisation name | Required when you download a template, because a template download is how organisations tell us what the material is for. |
| Terms acceptance time | The record that you accepted these terms, and when. |
| Marketing consent time | Separate from terms acceptance and never pre-ticked. Empty means you did not opt in. |
| Two-factor secret and recovery codes | For administrator accounts only. Encrypted at rest and never included when the account is serialised. |
| Phone number, organisation email | Only if you chose to give them. Both are optional. |
| Sign-up IP address and browser user agent | Recorded once at sign-up to make abuse of the free-account gate traceable. This one field is kept in full rather than hashed, which is an inconsistency with the rest of the system and is recorded as known technical debt in the repository. |
Downloads, alerts and saved work
- Template downloads. Each download records which template, which version and file, when, the referring page, and a hash of your IP address rather than the address itself.
- Newsletter. The digest stores your address, the jurisdictions you chose and a confirmation token. Subscription is double opt-in: nothing is sent until you confirm from the address itself, and every email carries a one-click unsubscribe.
- Followed records and alerts. Records you follow are stored against your account and are visible only to you.
- Saved screening profiles. The applicability screener can save your answers to its questionnaire. That profile belongs to one account, is never published, and holds questionnaire answers only. It is not a place to describe your systems, your evidence or your conclusions, and nothing you save there is read by anyone else.
If you report a correction
A correction you submit becomes part of the public record: the corrections log publishes what was reported, what was decided and when, including refusals. Your name, address and affiliation are never published with it. They are kept so a reviewer can come back to you with a question, and giving them is optional.
Payments
No card or bank details are stored here or pass through this application. Where a paid plan exists, checkout and the billing portal are hosted by the payment provider, who is the merchant of record. This site keeps only the provider's identifiers, the plan, the status and the dates.
How long things are kept
| Record | Kept |
|---|---|
| Account record (name, address, organisation) | Until you delete the account. Deletion removes it immediately. |
| Download history | Until you delete the account. |
| Newsletter subscription | Until you unsubscribe, which removes the address from the sending list. |
| Contribution you submitted | Kept indefinitely as part of the public correction record. Your name and address are never published with it. |
| Aggregate page counts | Kept indefinitely. They contain no identifier, so there is nothing in them to attribute to you. |
| Administrator action log | Kept indefinitely. It records staff actions, not reader activity, and exists so an editorial decision can be traced to a person. |
Your control over it
- See and change it. Your account page shows your details, your download history and your consent settings, and lets you change them.
- Delete it. The same page deletes the account. This is not a request queue: it removes the account and the records tied to it.
- Stop the email. Unsubscribe from any digest in one click, or clear marketing consent on the account page. Neither affects your ability to read the site.
- Ask a person. If any of the above does not do what you need, use the contact form and a person will answer.
Depending on where you live you may have statutory rights of access, correction, erasure, portability and objection. We apply the list above to everybody rather than asking where you are.
How it is protected
- Traffic is served over HTTPS, with a content security policy and without disclosing server versions.
- Passwords are hashed. Administrator two-factor secrets, recovery codes and provider API keys are encrypted at rest.
- Administrator access needs a second factor, and every change an administrator makes is written to an audit log that records who, what and when, and a hash of the address rather than the address.
- Template files are stored outside the public web root and delivered through short-lived signed links bound to the account that requested them.
No system is beyond compromise. If you believe you have found a vulnerability, report it through the contact form rather than disclosing it publicly, and we will work with you on it.
Who else touches it
The site runs on third-party hosting and uses third-party services to deliver email, serve traffic and, where configured, process payments and measure usage. These providers process data on our instructions to run the service. They are not permitted to use it for their own purposes, and none of them is given data for advertising.
Changes to this policy
Every change to this page is a commit in the public repository, so its history is the change log. The date at the top is the last substantive update. If a change materially reduces your protection, we will say so on the site rather than only editing the page.
Informational only, not legal advice. Verify every claim against the linked official sources and consult qualified counsel before acting.