Privacy Notice
The short version. We collect the least we need to run a DPDP compliance-management tool: who you are, how to reach you, what you record in the tool, and the technical records needed to keep it secure. We do not sell personal data. We do not show advertising. We do not use what you record to train AI models. The database is in Mumbai; outgoing email passes through a US company (Resend). You can ask us to show, correct or erase your data, and complain to us, and then to the Data Protection Board of India.
1. Two different roles
This matters because the law treats them differently.
| Role | When | What that means |
|---|---|---|
| Data Fiduciary (we decide why and how) | We handle personal data for our own purposes: your sign-up and account details, billing, messages you send us, website and service logs, security records. | This notice is our notice to you. We are responsible to you for it. |
| Data Processor (we act for our customer) | A customer organisation puts personal data into VERIDIAN DPDP — for example its staff, vendors, clients, students or parents — to manage its own DPDP work. | The customer is the Data Fiduciary and decides what is collected, why and for how long. We process it only on its behalf under our Terms. If you are one of those people, your main contact for your data is the organisation that gave us your details; we will help them help you. |
Who we are: IT SERVICES BY RAJAT AGARWAL, a sole proprietorship in India: the trade name of Rajat Agarwal, an individual, B-1105, Shipra Krishna Vista, Indirapuram, Ghaziabad, Uttar Pradesh, 201014, India; e-mail rajatsiroffice@gmail.com; phone +91 96503 97480 (the "Company", "we"). We are a software company. We deliver no physical products or services; everything is delivered digitally over the internet.
2. What we collect
| What | Examples | From whom / how |
|---|---|---|
| Account and contact details | Name, business email address, role, organisation name, phone (if given) | You, or the customer that invited you |
| Work records (Customer Data) | Jobs assigned to you, your answers and notes, dates, who confirmed or approved, fingerprints (hashes) of evidence, names of vendors or processors the customer lists, consent and parent-consent responses collected through the customer's pages | You, the customer and people it invites. Each change is added to a dated record; earlier entries are not overwritten. |
| Email and delivery records | The emails we send you (for example the Monday email), including the text of each one, whether they were delivered, opened links you used, unsubscribe choices | Our systems and our email provider. Open and click tracking on our sending domain is off. |
| Mail you send us | Messages and attachments sent to dpdp@veridian-aios.com, sender address, ticket number and category | You |
| Payment records | Invoice details and the proof of payment you send us, which can be a screenshot or PDF file you upload (kept privately; only you and our operator can open it). For payments made through Razorpay we keep Razorpay's reference numbers, the payment method, the card network, the last four digits of a card, the bank's name, a masked UPI id and the bank's reference number. We never keep a full card number or a full UPI id on this Service. | You |
| Sales Partner payout details | If you join as a Sales Partner: your PAN (if you give it), bank account name, account number and IFSC code, or your UPI id, so we can pay your commission. These are stored encrypted and are used only to make and record your payouts. | You |
| Technical and security data | IP address, browser type, date and time, pages requested, security and error logs | Automatically. Our hosting provider (Cloudflare) processes request data to deliver and protect the site and may set strictly security-related cookies. |
| Audit log of activity in the application | What was done in the application and by whom: signing in, a failed sign-in, creating, changing, deleting, publishing, downloading, reading personal data, consent and erasure, and anything an AI assistant read or prepared through an AI work link. For each: the account, role or AI tool, the time, the address, country, network, browser and device identifier it came from, and for a change what was changed. Never passwords, one-time codes, card or bank details, or keys. | Automatically, as the application is used. Personal values in it are stored encrypted. Each entry is chained to the one before it so that any alteration of the log can be detected. |
| Website measurement (public pages only) | The page address without anything after a "?" or "#", the time, the kind of device (phone, tablet or computer), the name of the site you came from, your country, page-speed figures, and any error the page hit or file that failed to load | Automatically, by a small script served from our own domain that reports to our own server. No cookie, no browser storage, no account, no third party, and we do not store your IP address in these records. It does not run on the signed-in application, the sign-in page or the links we email you. A browser that sends "Do Not Track" or Global Privacy Control is not measured. Records are kept for 90 days. |
| Visit journey (public pages only) | Which site or search you came from, any campaign tag in the link, the pages and parts of a page you looked at and for how long, which links and choices you used, where you left, your device, language, country and city, a shortened IP address (its last part blanked) and a one-way code of the full address that we cannot turn back into an address | Automatically, by a small script served from our own domain, so we can see which pages help people and where visitors come from. It sets one random visitor-id cookie for a year and never records anything you type. A browser that sends "Do Not Track" or Global Privacy Control gets no cookie and is only counted. When you sign in, the visit is linked to your account so we can see which visits led to a sign-up. Kept for 365 days, then only anonymous totals remain. |
| AI work link activity | That a link was created, its level and expiry, what was read or changed through it, and when | Our systems |
We do not intentionally collect sensitive personal data such as health records, biometric data, passwords, identity-document images or financial credentials. Please do not enter them; describe them instead. The Service is not directed at children. Children's data reaches it only when a school or other customer, as Data Fiduciary, adds it or collects a parent's consent through the Service.
3. Why we use it, and on what basis
| Purpose | Basis |
|---|---|
| To set up your account, sign you in, give you the jobs and pages the customer has assigned you, send the weekly email and reminders, and keep the dated record | Your consent (and, for people added by an employer, processing for purposes of employment where the customer relies on it); performance of the service the customer has asked for |
| To answer you, give support, handle grievances and data requests, and keep the ticket record of them | Your request; legal obligation |
| To keep the Service secure, prevent misuse and fix faults, including measuring how fast the public pages load and which errors they hit | Our legitimate operation of the service and reasonable security safeguards required by law |
| To invoice and to meet tax, accounting and company-law duties | Legal obligation |
| To protect or defend legal rights, and to comply with lawful orders | Legal obligation; legal claims |
We do not use personal data for advertising, we do not sell it, and we do not use Customer Data to train artificial-intelligence models. We do not make decisions about you by automated means that have legal effect on you.
4. Who receives it
| Recipient | Why | Where |
|---|---|---|
| The customer organisation you are linked to (and, for a CA/CS/audit/legal firm, the client it serves, and the reverse) | It is their record | — |
| Supabase (database, authentication) | Hosting and storage | Mumbai, India (AWS ap-south-1) |
| Cloudflare | Website hosting, network security, the website measurement records above, routing of mail sent to dpdp@veridian-aios.com | Global network |
| Resend | Sending our emails to you and receiving mail sent to dpdp@veridian-aios.com; the content of those emails passes through its service | A US company. Our mail is handled in Tokyo, Japan (AWS ap-northeast-1) |
| Razorpay | Taking card and UPI payments in its own payment window (through the Razorpay account of IT Services by Rajat Agarwal); it tells us a payment succeeded and its reference. We do not see or keep card numbers | India |
| Google (mailbox) | Our operator's mailbox that receives forwarded copies of mail sent to dpdp@veridian-aios.com | Google's network |
| Professional advisers, auditors, insurers | To advise us, under duties of confidence | India |
| Courts, the Data Protection Board of India, police and other authorities | Only where the law requires or a lawful order is received | India |
| A successor to the business | If we are restructured or sold, on the same terms as this notice | — |
| An AI provider chosen by a user | Only if a user hands an AI work link to their own AI assistant. That provider then acts for the user, under its own terms; it is not our sub-processor | The provider's location |
Transfers outside India are made under section 16 of the Digital Personal Data Protection Act, 2023, which allows them except to countries the Central Government restricts by notification. We will follow any restriction it notifies. We do not otherwise sell, rent or disclose personal data.
5. How long we keep it
- Account and work records: while the customer's account is active and the purpose continues. After the account ends we make the data available for export for 30 days and then delete or irreversibly de-identify it within a reasonable time, except what the law requires us to keep.
- Mail to dpdp@ and tickets: an open ticket is kept until it is closed; a closed ticket is deleted 24 months after it was closed, unless a grievance, dispute or legal duty needs it kept longer.
- Invoices and accounting records: for the period the tax and company laws require.
- Sign-in codes and sessions: deleted 30 days after they expire. E-mail confirm links: 30 days after they expire.
- The log of e-mails we sent: deleted after 13 months.
- Network-prefix records for AI work links (the first part of the address a link was used from, kept only to warn you of unfamiliar use): deleted after 90 days.
- Other security logs: for a short operational period, and longer where the law requires logs to be kept (for example for a period after erasure under the DPDP Rules) or where needed for an investigation.
- The audit log of activity in the application: 365 days, then deleted. Why we keep it: for security and audit, so that we and our customers can show who did what with personal data and protect it, as the DPDP Rules (Rules 6 and 8(3)) expect. About a month before deletion the owner, the heads of department and each person who appears in the log get a short e-mail with a link; until deletion you can download your own entries (and the owner or a head of department the organisation's entries) from the signed-in application, with identifiers shortened. We never e-mail the log itself. What remains after deletion: counts with no identifier in them, and a certificate that records that the deletion took place. If a court or authority requires records to be held, deletion is paused for that organisation until the hold ends.
- Back-ups expire on their normal cycle.
6. How we protect it
We take reasonable security safeguards: encrypted connections; separation of one customer's data from another's enforced in the database; role-based access for our own staff on a need-to-know basis; an append-only history of changes; limited, expiring links for AI work; contracts with our providers. No system is perfectly secure and we cannot promise otherwise. If there is a personal data breach affecting data we hold, we will tell the customer concerned without undue delay and, for data we hold as a Data Fiduciary, the Data Protection Board and the people affected, as the law requires.
7. Your rights and how to use them
Under the Digital Personal Data Protection Act, 2023 you may: get a summary of the personal data we process about you and with whom we have shared it; ask us to correct or complete it; ask us to erase it (we will unless the law requires us to keep it or we need it for the purpose you agreed to); withdraw consent at any time, as easily as you gave it (the weekly email has an unsubscribe link; withdrawing does not undo what was lawfully done before); have your grievances answered; and nominate another person to exercise these rights if you die or cannot. To use a right, open My data in the application (you can see what we hold, ask for a copy, a correction or erasure, and name your nominee there), or write to dpdp@veridian-aios.com with the subject Data request (or Grievance). We may ask you to prove who you are. If your data belongs to a customer's records, we may pass your request to that customer, who decides it; we will help. Erasing an account removes your personal data from the product, but entries about you in the audit log (section 5) stay until their 365 days end, because the law expects this kind of log to be kept; they are then deleted.
- Grievance Officer. The Grievance Officer of the Company, Rajat Agarwal, handles grievances at dpdp@veridian-aios.com (subject: Grievance) or on +91 96503 97480.
- Response time. We reply within 14 days. We resolve issues through mutual discussion within 90 days.
- Data Protection Board. If we do not resolve it, you may complain to the Data Protection Board of India (section 13 of the Act). Make the complaint through the Board's online complaint process; we will link it here once the Board publishes it. The law expects you to have first used our grievance process and given us the chance to respond.
- Complaints about a customer's handling of your data go first to that customer.
The full list of the outside services we use, with what each does and where, is on the sub-processors page.
8. Cookies and similar tools
The public pages do not use advertising or cross-site tracking cookies. Their measurement script (see the "Website measurement" row in section 2) sets no cookie and uses no browser storage. A second small script (the "Visit journey" row) sets one first-party cookie with a random number, dpdp_vid, for one year, and keeps the same number in local storage; neither is set when your browser sends Do Not Track or Global Privacy Control. The home page remembers the colour theme you pick (one of three) in your browser's local storage on your own device; it is a display preference, not personal data, and it is never sent to us. The application also keeps small items on your own device so that it works offline and remembers a referral link: a copy of your jobs (in the browser's IndexedDB), a service worker that serves the pages without a connection, a referral code in local storage, and a session marker in session storage. None of these is read by advertisers, and sign-out removes the copy of your jobs. If your browser allows notifications, the application can show one reminder a day, made on your own device from that copy; nothing is sent to us for this. Our hosting provider, Cloudflare, also adds its own Web Analytics script (served from static.cloudflareinsights.com) to our pages, including the signed-in application; it collects page-load timing figures, and Cloudflare states that it does not track individual visitors across its customers' websites. The signed-in application keeps a sign-in session in your browser and may store small items to remember your place. Our hosting provider may use cookies strictly necessary for security and performance. You can block cookies in your browser, but the signed-in application will not work without the sign-in session.
This site uses first-party storage on the device for the sign-in, the colour theme and a random code that recognises a returning visit. No advertising cookies and no third-party trackers are used.
Navigation data is collected to improve this site. A Global Privacy Control signal from the browser is respected: no navigation data is collected.
The visit counter keeps the pages looked at and the time spent on them, how the visit arrived, the country and city, the network name, the browser and device type, a scrambled short form of the network address and the random code, for up to one year, and never a name, a mobile number or an e-mail address; a visitor who sends the signal is counted only in anonymous daily totals.
9. Changes
We will post changes here with a new date. For a change that materially affects how we use your data we will also tell you by email or in the Service, and ask for fresh consent where the law requires it.
10. Contact
dpdp@veridian-aios.com (subject: Grievance, Data request, Sales or Partner)
IT SERVICES BY RAJAT AGARWAL · B-1105, Shipra Krishna Vista, Indirapuram, Ghaziabad, Uttar Pradesh, 201014, India · rajatsiroffice@gmail.com · +91 96503 97480.