Help
DPDP statement
For recipients and uploaders under India’s DPDP Act, 2023: what a delivery or portal page collects, why, how long it is kept, and whom to write to.
Updated 2026-09-21
Who is who#
When a sender (a company, a lab, a practice, a studio) sends you files, or asks you to upload files, that sender is the data fiduciary for the files and for your details as a recipient or uploader — it decided to send to you and it chooses the settings. Boita (Aariko Systems OPC Private Limited, Pune) is the sender's data processor: we run the pages and move the bytes on the sender's instructions. For the account and billing data of the sender itself, Boita is the fiduciary; that is covered by the privacy policy.
What a delivery or portal page collects#
| Data | Why | When |
|---|---|---|
| Your email address | To show you the files when the sender asked for verification, to send you the one-time code, to attribute your download on the sender's receipt, and — on a portal — to confirm your upload landed | Only if you type it |
| A 6-digit code | To prove the address; it expires in ten minutes | When verification is on |
| A guest token on your browser | So you are not asked to verify the same address again for 30 days, and so app.boita.io/me can list your deliveries | After a successful verification |
| Your WhatsApp number | Only when the sender addressed the delivery to it; public pages show it masked | Chosen by the sender |
| A hashed hint of your IP address and your browser's description | Abuse limits on the page, and the sender's receipt; the address itself is not stored on the receipt | Every visit |
| Views, downloads, reactions, approvals and comments | The sender's delivery receipt — the record that the delivery happened | When you do them |
| Your name and message on a portal | So the sender knows who sent what | If you type them |
| Your low-bandwidth choice | Stored on your browser only, to keep the page light | If you change it |
The files themselves are the sender's; Boita stores them for the sender, records a checksum for each so both sides can prove what was delivered, and deletes copies made for you (such as watermarked renders) when the link ends.
What we do not do#
We do not sell or share your details with anyone but the sender that sent to you. We do not use your address for marketing. Recipient pages carry no third-party scripts or advertising trackers. Comments and reactions are shown to the sender, never to other recipients.
How long#
Recipient records live as long as the sender's link and its receipt do — links expire on a date the sender chose (at most a year on the largest plan), and receipts stay with the sender's workspace. Verification codes are kept for ten minutes; the guest token on your browser for 30 days; abuse-limit counters for minutes to hours. When a sender closes its workspace, its data — including recipient records — is deleted on the schedule in the privacy policy.
Your rights and whom to write to#
Under the DPDP Act you may ask for access, correction and erasure of your personal data, and nominate someone to exercise these rights. Because the sender decided to send to you, write to the sender first — the sender's name and email are on the delivery page. You can also write to Boita's grievance officer, who will act on the sender's behalf or forward your request:
Grievance Officer — Snehal Pawar, grievance@boita.io, Workflo Icon Tower, Office No. 702, Baner Road, Pune 411045, Maharashtra, India.
Complaints that are not resolved can be taken to the Data Protection Board of India.
Language#
The delivery page, the upload page and this statement are published in English only for now.