Privacy and data
Privacy Policy
This policy explains what personal data RightSignal processes, why, where and for how long, who receives it and what rights you have. It follows Indian law, including the Digital Personal Data Protection Act, 2023 (the "DPDP Act"), and the General Data Protection Regulation (the "GDPR") for people in the European Union.
01Who we are
Provider and scope: Manraj Singh Chandpuri, a Canadian citizen and a law student in India, trading as RightSignal, of Chandigarh, India ("RightSignal", "we") provides the RightSignal service. This policy covers the website rightsignal.legal, the app at app.rightsignal.legal, the API at api.rightsignal.legal and RightSignal's own crawler.
Our role: For account data and service data we decide why and how the data is processed, so we are the data fiduciary under the DPDP Act and the controller under the GDPR. We act as a processor only where we process a client's personal data on that client's behalf, for example personal data inside a corpus manifest submitted for Trace or inside materials supplied for Matters. In those cases the client is the data fiduciary or controller, our Data Processing Agreement applies, and we refer any request about that data to the client.
Business users only: RightSignal is offered only to businesses, institutions and professionals, and never to children. We do not knowingly process the personal data of anyone under 18 as a user, and we will delete such data if you tell us about it at privacy@rightsignal.legal.
02Personal data we process
Account and service data: The table below lists the personal data that we process as data fiduciary and controller, what we use it for and our ground under the GDPR. We hold no passwords, because sign-in is by a single-use email link.
| Data | What it contains | What we use it for | GDPR ground |
|---|---|---|---|
| Account and member data | Your email address, your name and job title where you give them, your organisation's name, your role and the dates of your membership. | To create and run your organisation's account. | Contract, and our legitimate interest in serving your organisation. |
| Acceptance records | The name you type when you accept our terms or a Service Statement, the documents and versions accepted, the time, and the IP address and browser details of the request. | To record who accepted what and when. | Contract, legitimate interest in keeping evidence, and legal claims. |
| Sign-in links and sessions | The address a sign-in link was sent to, the times it was made, used and expired, and a hash of each link and session token. A link works once for 15 minutes, and a session ends after 12 hours without use or 7 days at most. | To sign you in and keep you signed in. | Contract. |
| IP addresses and the audit log | For each authenticated request and each failed key attempt, the organisation, the key or user, the method, the route, the status, a request identifier, the IP address and the time. The log never holds a request body, a query string or a secret. | Security, detection of misuse and an audit trail that your organisation's owners can read. | Legitimate interest in security and accountability, and legal obligation. |
| API key records | The key's name, mode, visible prefix, scopes and state, who made it, the dates of its use, and a salted and keyed hash of its secret. | To authenticate API requests. | Contract. |
| Email records | The address we sent a message to, its subject, its text with any sign-in link removed, its delivery status and the time. | To send sign-in email and confirm delivery. | Contract and legitimate interest. |
| Usage events | For each billable or limited action, the organisation, the key or user, the type of action, the amount, any AI model cost and the time. | Quotas, limits, billing and capacity. | Contract and legitimate interest. |
| Checks and receipts | The page address, crawler, purpose and policy asked about, which user or key asked, and the sealed receipt. | To make and record decisions and keep evidence of them. | Contract, legitimate interest in keeping evidence, and legal claims. |
| Administrator records | For RightSignal's own administrators only, their email address, their second-factor records, their sessions and a separate log of their actions. A second-factor record is a passkey's public key or an encrypted secret for time-based codes. | To control and record administrative access. | Legitimate interest in security. |
| Billing data and messages | Your name, organisation, billing contact and tax number, what you bought and paid, and anything you write to us. Our payment provider handles card and bank details. | To take payment, keep tax records and answer you. | Contract, legal obligation and legitimate interest. |
| Website visits | Your IP address and browser details, processed by the provider that hosts rightsignal.legal. | To serve and protect the website. | Legitimate interest. |
What we do not do: We do not sell personal data, and we do not use it for advertising or for profiling people. We use no tracking or analytics cookies, and we send service email only. Our decisions concern websites and what they publish, so we make no decision about any individual by automated means.
Grounds under Indian law: Until the main duties of the DPDP Act come into force, section 43A of the Information Technology Act, 2000 and the rules made under it in 2011 apply, and we do not ask for sensitive personal data as those rules define it. Once the DPDP Act's duties apply, we will process the personal data that you give us voluntarily for the purposes this policy specifies, as section 7(a) of the Act allows, and we will ask for your consent wherever the Act requires it.
03Personal data in captured pages, receipts, the model ledger and backups
Captured pages: To make a decision, our crawler reads the page that a client asked about and the website's signal files, home page and policy pages, such as its terms of use, privacy policy and copyright page. These public pages sometimes contain personal data, for example the name and contact details of a site's grievance officer. Apart from the one page that a client asks about, the crawler does not read a site's articles, listings, profiles or comments. We do not search, index or build any record about the people named in captured pages, and we use those pages only to find and evidence what the site says about access and use.
Receipts: A receipt records the request, the signal files and policy pages that were read, the wording relied on and the decision, and it does not keep unrelated content from the site. It may hold the name of the person who accepted the Service Statement for the client and, rarely, personal data that appears in wording quoted from a policy page.
Model ledger: In live mode we may send the text of a site's policy pages, and of the pages visited to find them, to an AI model provider so that the AI reader can work. We keep a ledger of each such request and answer so that a reading can be reproduced and accounted for, and the ledger therefore holds the same public page text. We do not send account data to the AI provider or tell it which client asked, and test mode does not use the AI models.
Backups: Our daily backups contain the account database and an export of the model ledger, so they contain the data described in clauses 2 and 3.3. We encrypt each backup before it leaves our server.
Publicly available data: Section 3(c)(ii) of the DPDP Act takes personal data outside the Act where the person concerned has made it publicly available, or where another person has made it publicly available under a legal duty. Some personal data in captured pages falls within that exclusion, such as a grievance officer's details that a site must publish by law, but we do not assume that all public data does. The GDPR has no such exclusion, so for people in the European Union we rely on our legitimate interest in recording what websites publish about access and use, within the limits in clause 3.1.
04Where data is stored and who receives it
India: The service runs on a virtual private server operated by Hostinger and located in India. The account database, each organisation's sealed records and captures, the model ledger and the server's logs are stored there.
United States: We store two kinds of data with Backblaze B2 in the United States, in its region us-east-005. The first is encrypted backups of the account database and the model ledger, which we keep for 35 days and which Backblaze cannot read, because the key that opens them is never on any server. The second is live-mode receipts, which we lock in write-once storage for seven years by default and do not encrypt before upload, because they must stay checkable with the standalone verifier.
Our providers: We share personal data only with the providers that help us run the service, and only what each one needs. The Subprocessors page gives the current list.
| Provider | What it does | What it receives |
|---|---|---|
| Hostinger | Hosts the server in India. | Everything stored on the server. |
| Backblaze | Stores backups and locked receipts in the United States. | Encrypted backups, which it cannot read, and live-mode receipts. |
| Resend | Sends our sign-in email, and delivers to us the messages sent through the website's forms. | The recipient's email address and the message, including the sign-in link, and what you type into a form. |
| Anthropic | Provides the AI models for the AI reader and the policy-page assistant. | The text of public website pages and our instructions, and no account data. |
| Cloudflare | Hosts the website rightsignal.legal, receives its forms and serves the crawler's public key directory. | The IP address and browser details of website visitors and of whoever fetches the directory, and what you type into a form while it is passed on. |
| Razorpay | Takes payments, when used. | The payer's name, contact and payment details and the amount. |
Other disclosures: We also disclose personal data to a court, regulator or other authority where the law requires it, to our professional advisers under a duty of confidence, and to a successor entity as clause 9.2 describes. The owners of your organisation can see its members, keys, usage and audit log in the app. Our own administration console shows counts and money only, and it does not show an organisation's decisions, receipts, checks, keys or audit entries.
Transfers: The DPDP Act allows personal data to be transferred outside India except to a country that the Central Government restricts by notification, and to our knowledge no notification restricts transfers to the United States at the date of this policy. Where the GDPR applies to a transfer that we make to a provider outside the European Economic Area, we rely on an adequacy decision that covers that provider or on the European Commission's standard contractual clauses. You can ask us for a copy of those clauses at privacy@rightsignal.legal.
05How long we keep data
Retention periods: We keep personal data for as long as its purpose needs it and then for the periods in the table below. We keep data for longer where a law, a court order or a pending claim requires it, and we review these periods every year.
| Data | How long we keep it |
|---|---|
| Account and member data, sign-in and session records, API key records, email records, usage events, the audit log and check records | While your organisation's account is open and for up to 3 years after it closes, which is the general period for bringing a contract claim in India. |
| Acceptance records | For as long as the agreement lasts and the receipts that refer to them are kept, and for 3 years after the later of the two. |
| Live-mode receipts | Locked for 7 years from the date of the receipt, or for another period agreed with the client. |
| Captured pages and the model ledger | For at least as long as the receipts that rely on them. We may delete the full text of captured home pages after 180 days. |
| Backups | 35 days, so data deleted from the live service remains in backups until they expire. |
| Billing and tax records | For as long as Indian tax law requires, which can be up to 8 years. |
| Administrator records and messages you send us | Up to 3 years after the role ends or after the last message. |
The seven-year receipt lock: A receipt is evidence of what a website said and what was decided at a stated time, and its value depends on its being kept unchanged. We therefore lock each live-mode receipt in write-once storage for seven years, to provide that evidence to the client and to establish, exercise and defend legal claims. The storage runs in governance mode, which means that the credentials our service uses cannot alter a locked receipt, delete it or shorten its lock. Only the holder of the storage account could lift a lock, and our policy is not to do so unless the law requires us to erase the data and no ground for keeping it applies.
06Security and breaches
How we protect data: Our Security page describes our measures in full. In summary, connections to the app and the API are encrypted in transit, sign-in uses single-use email links, API key secrets are stored only as salted and keyed hashes, each organisation's records are kept apart, backups are encrypted before they leave the server, and receipts are sealed with a digital signature.
Personal data breaches: If we become aware of a personal data breach, we will act to contain it and find out what happened. We will tell the people affected and the authorities as the law requires, including the Data Protection Board of India once the DPDP Act requires it, the Indian Computer Emergency Response Team within the time its directions set, and the competent supervisory authority within 72 hours where the GDPR applies and that is feasible. Where a breach affects data that we process for a client, we will tell that client as the Data Processing Agreement requires.
07Your rights
In India: You may ask us to tell you what personal data of yours we process and with whom we have shared it, to correct, complete or update it, and to erase it where we no longer need it and the law does not require or allow us to keep it. You may nominate a person to exercise your rights if you die or become unable to do so, and you may withdraw any consent on which our processing rests. If you are not satisfied with our answer to a grievance, the DPDP Act lets you complain to the Data Protection Board of India once the relevant provisions are in force.
In the European Union: Where the GDPR applies, you also have the right to receive a copy of your personal data, to have it corrected or erased, to have our processing restricted, and to receive it in a portable form where the processing rests on contract or consent. You may object to processing that rests on our legitimate interests, and you may complain to the data protection authority where you live or work.
How to exercise your rights: Write to privacy@rightsignal.legal from the email address on your account, or give us enough to identify you. We will answer within 30 days and do not charge for a reasonable request.
Limits: We cannot alter a locked receipt and do not delete one during its lock, because we keep it as evidence and for legal claims, which Indian law and the GDPR both allow. Data that we delete from the live service stays in encrypted backups until they expire after 35 days. If you are named on a page that we captured, tell us the page and your concern, and where the law requires it we will delete the data, hide it in what we show or restrict its use, so far as that can be done without destroying sealed evidence that we need for legal claims.
08Grievance Officer
Contact and response times: Our Grievance Officer is Manraj Singh Chandpuri, RightSignal, Chandigarh, India, who can be reached at privacy@rightsignal.legal. The Grievance Officer will acknowledge a grievance within 7 days and aim to resolve it within 30 days.
09Other matters
People in the European Union: RightSignal is established in India and has no establishment in the European Union. At the date of this policy we have not appointed a representative under Article 27 of the GDPR, and we will appoint one and publish its name and address here when Article 27 requires it. Until then you can contact us directly, which does not affect your rights or your right to complain to a supervisory authority.
Successor entity: RightSignal intends to form a company or other entity to carry on its business. When it does, we will transfer the personal data described in this policy to that entity, which will become the data fiduciary and controller in our place and will be bound by this policy. We will tell account holders before the transfer takes effect, and your rights will not change.
Cookies and changes: The website sets no cookies, and the app sets one essential session cookie that our Cookie Notice describes. We may change this policy, and each version carries a version number and a date. If a change is material, we will tell account holders by email or in the app before it takes effect.
Contact
Privacy questions and grievances go to privacy@rightsignal.legal. Security reports go to security@rightsignal.legal, legal notices to legal@rightsignal.legal and general enquiries to hello@rightsignal.legal.
Manraj Singh Chandpuri, trading as RightSignal, Chandigarh, India.