Pramaan Background Checks Addendum

Version 1, 19 October 2026. This addendum is part of the Terms of Service (section 8).

1. What this covers

Background checks are the superpowers and missions marked as hiring checks or court-record checks in the catalogue. Each one names the addendum on its page.
Calls to a background check are refused with the code addendum_required until an owner or admin of the workspace has accepted the current version of this addendum.

An owner or admin accepts it in Settings, for the whole workspace. It then binds every member and every key in that workspace.
We record who accepted, when, and which version.
When we change this addendum in a way that matters, we show the new version. Background checks pause until an owner or admin accepts it. Other superpowers keep working.

You decide why a check is run and what is done with the result. For that data you are the controller (or business, or user of the report). We act as your processor (or service provider), as Terms of Service section 8 and the DPA describe.
You are responsible for meeting the laws that apply to you as the user of a check, in every place where you, the person checked, or the decision sits.

Run a check only for a purpose the law allows where the person is, and only for the purpose the person agreed to.
Hiring checks are for decisions about hiring or engaging the person checked: as an employee, contractor or volunteer.
Never run a background check to decide on credit, insurance, housing or similar eligibility, or about a person who has not applied to you, or to monitor an existing worker without the consent and notice the law requires.
Court records about criminal matters are restricted in many places (for example the EU and UK GDPR, Article 10). Run court-record checks only where the law lets you, and only to the extent it does.

Before each check, get the person's clear, informed consent, in the form the law requires (for example a separate written disclosure in the US).
Pass the record id of that consent with the call. Passing an id means:
- you hold that person's valid consent for this check and this purpose;
- you will show us the record within 5 business days if we ask;
- the id is not invented, reused or taken from a different person or purpose.
Give the person every notice the law requires about the check, including who ran it and how to dispute it.

Never use a check as the only basis for a decision about a person.
Before you decide against a person because of a check, where the law requires it:
- tell them, and give them a copy of what you relied on;
- give them a fair chance to explain or dispute it;
- then tell them of your final decision.
Follow fair-chance and similar laws that limit when and how you may ask about or use criminal history.

Results come from public and third-party sources. They can be incomplete, out of date, or about a different person with a similar name. Check that a result matches the person before relying on it.
If a person disputes a result, tell us at privacy@pramaan.dev with the call's id. We will check it with the source and tell you what we find within 30 days.
Correct or delete any result you hold that turns out to be wrong.

We may ask for consent records and other evidence that you follow this addendum.
We may suspend background checks, or the workspace, if you do not provide them, or if we believe a check was run without consent or for a purpose this addendum does not allow.
We may report misuse where the law requires us to.

You are responsible for claims that come from checks you run in breach of this addendum or the law. You will cover every legal fee, fine, penalty and damages award we face because of them. This has no cap: the liability limits in Terms of Service do not apply to it.
Our own liability to you under this addendum, including any legal fees, is capped at US$100.