AccessRecord

Privacy Policy

This explains what personal data AccessRecord collects, why, how long we keep it, and what rights you have over it.

Last updated 11 October 2026

1. Who is responsible for your data

Operated byNabin Karna
Trading asAccessRecord
Contactsupport@accessrecord.app
Governing lawNepal

For the account data described in section 2, and any payment records described there, the operator — an individual, and a natural person under data protection law — is the controller. For the product and conformance data you enter, which may include the name and job title of a person who signed a record, you are the controller and we are the processor, acting on your instructions. That processing is covered by our Data Processing Addendum.

There is no data protection officer. There is no privacy team and no legal department. Data protection requests are read and answered by the operator, whose contact address is above — which is usually faster than a form letter to a large vendor's privacy portal.

2. What we collect

CategoryWhat it isWhy
AccountUsername, password hash, two-factor secret, backup code hashes To authenticate you and protect the workspace
PaymentYour name, the email you are invoiced at, what you paid and when Only if you enter a paid arrangement — to invoice you and meet tax obligations
Your contentProducts, versions, conformance levels, remarks, signatory names and titles To provide the service — this is what you came for
TechnicalIP address, user agent, timestamps, and an audit log of security events To secure the service, rate-limit abuse and investigate incidents
SupportThe contents of messages you send us To answer you
Worksheet downloadIf you ask for the free worksheet on the VPAT template page: the email address you give, your name and company if you give them, and the date To record the download. No email is sent because of it and it is not added to any mailing list. Ask, and it is deleted.

We do not use advertising trackers, we do not sell personal data, and we do not use your content to train machine-learning models.

One further use, and only if it applies to you: if you buy a subscription, the email address you gave at checkout is used to send you the single message that lets you set a password. That is the only email this service sends. It is not added to a mailing list, there is no newsletter, and there is nothing to unsubscribe from.

3. Cookies

We set exactly two cookies, both strictly necessary, both HttpOnly and SameSite=Strict:

CookiePurposeLifetime
ar_sessionKeeps you signed in12 hours
ar_pendingHolds the half-finished sign-in while you enter a two-factor code5 minutes

There is no analytics cookie and no consent banner, because there is nothing to consent to. Pages on the public verification site set no cookies at all.

4. Who we share it with

Only the processors listed on the Subprocessors page, and only as far as needed to run the service. We may also disclose data where we are legally compelled to, and we will tell you unless we are prohibited from doing so.

That list is short, and it is short on purpose. One person runs this service, so there is no support floor, no contractor pool and no offshore operations team that could be given access to your data even if someone wanted to. We do not share your data with marketing tools, analytics platforms, or anyone who would use it for their own purposes.

5. International transfers

Where personal data moves outside its region of origin, we rely on an appropriate transfer mechanism — the UK or EU Standard Contractual Clauses, the UK International Data Transfer Addendum, or an adequacy decision. Our subprocessors list records where each provider stores data.

6. How long we keep it

7. Security

Passwords are hashed with scrypt and never stored in readable form. Sessions are signed, HttpOnly cookies. Two-factor authentication is available and can be required. Traffic is encrypted in transit. The workspace data directory is not reachable over HTTP, and a public verification page exposes only the record you deliberately published.

On access: production access belongs to one person — the operator. There are no support staff, no contractors and no third-party administrators who can read your workspace. Fewer people with access is a real security property, and it is one of the few genuine advantages of a service this size.

No system is perfectly secure, and no honest one-person operation will tell you otherwise. If we become aware of a breach affecting your personal data we will notify you and the relevant authority within the timescales the law requires — 72 hours for the GDPR.

8. Your rights

Depending on where you live you may have the right to access, correct, delete, restrict or object to processing of your personal data, to receive it in a portable format, and to withdraw consent where consent was the basis. To exercise any of these, contact support@accessrecord.app. We will respond within 30 days.

You will get a reply from a person, not an automated acknowledgement. If you are in the UK or EU you may also complain to your local supervisory authority. We would rather you came to us first.

9. Children

The service is a business tool and is not directed at children. We do not knowingly collect personal data from anyone under 16.

10. Changes

If we make a material change to this policy we will tell you before it takes effect.