Legal
Data processing agreement
Last updated: 19 November 2026
Pending review by a lawyer. Questions: contact us.
For studios: how Hourbill handles the personal data you put into it — your team's and your clients' — on your behalf.
1. Parties and scope
This agreement is between the studio that uses Hourbill (the "controller") and Neeraj Chouhan, New Delhi, India, who runs Hourbill (the "processor"). It applies to personal data the studio puts into Hourbill, and forms part of the terms of service. Accepting the terms accepts this agreement; if you need a signed copy, write to privacy@gethourbill.com.
2. What is processed
- People: the studio's team members and its clients' contacts.
- Data: names, email addresses, postal and billing addresses, tax ids, time entries, expenses and receipts, rates, estimates, invoices and payment status, notes and files the studio adds.
- Purpose and duration: only to provide Hourbill to the studio, for as long as the studio uses it, and until deletion as set out in section 8.
- Special categories: none are needed; the studio agrees not to put them into Hourbill.
3. Hourbill's duties
- Process the data only on the studio's documented instructions — these terms and the studio's use of the app.
- Make sure anyone with access is bound to confidentiality.
- Keep the security measures in section 5.
- Help the studio answer requests from the people whose data it is (access, correction, export, deletion), mostly through the app's own export and delete features.
- Help the studio with security and impact assessments where the law requires them.
- Make available what's needed to show this agreement is kept, and allow reasonable audits on notice.
4. Subprocessors
The studio allows Hourbill to use the services on the subprocessors page. Hourbill gives each the same data protection duties as in this agreement, stays responsible for them, and emails the owner at least 30 days before adding a new one, so the studio can object (and cancel if we can't resolve it).
5. Security
- Each studio's data is separated in the database itself (row-level security on every table).
- Encrypted connections everywhere; payment keys encrypted with AES-256-GCM, the key kept outside the database.
- Two-factor sign-in, which an owner can require for the whole studio.
- Fresh sign-in needed for payout changes, exports and deletion; payout changes logged and emailed to owners.
- Rate limits and bot checks on public endpoints; team members never see rates or costs.
- Error monitoring without session replay or personal details.
6. Personal data breaches
Hourbill tells the studio owner without undue delay, and in any case within 48 hours of becoming aware of a breach affecting the studio's data, with what is known, and keeps the owner updated.
7. Transfers
The database and files live in a single Supabase region (write to privacy@gethourbill.com to ask which); some subprocessors work in other countries (see their entries). Where the law requires a transfer safeguard, Hourbill relies on the provider's standard contractual clauses or an equivalent.
8. Deletion and return
The studio can export all its data at any time. When the owner deletes the studio, it can be restored for 14 days and is then deleted with its files; backups, where enabled, roll off within 7 days. Hourbill keeps nothing of it afterwards except a record that the deletion happened.
9. Contact
Data protection questions: privacy@gethourbill.com. Postal: Neeraj Chouhan, New Delhi, India.