dirhp Privacy Notice
This notice explains how dirhp handles personal data during the pilot, under Singapore's Personal Data Protection Act 2012 (PDPA). It is part of the Pilot Terms.
dirhp is run by Jovin Lim, an individual in Singapore. Jovin is responsible for data protection and can be reached at help@dirhp.io.
What we collect
- Account details: your name and email, your role and studio size if you give them, whether you have confirmed your email, whether your account is active or suspended, and which version of the Pilot Terms you accepted and when.
- Sign-in details: Supabase handles your password, and dirhp never stores it. We keep the codes that keep you signed in only in hashed form. For each Rhino you connect, we store its computer name and Rhino version. For each AI app you authorize, we store its registration and access token.
- Design data: the objects you track or save through dirhp, including their geometry, attributes and User Text, along with your options, versions, notes, recipes, viewport captures, files you add, and the Rhino document's name. Your .3dm file itself stays on your computer.
- Usage records: which dirhp tools ran, when, for how long, and whether they worked, including short error messages. We record the names of a tool's inputs, not their values. Each session also keeps an activity log.
- Messages to us: if you join the waitlist or send us a message from dirhp.io, we keep your email, name and message, with your browser type and country. If you send feedback from the dirhp panel, or ask your AI assistant to send it, we keep your name, email and message, with your dirhp and Rhino versions.
We see your IP address to limit repeated sign-up and sign-in attempts. We don't store it.
Cookies
dirhp sets one cookie, dirhp_session, which keeps you signed in for up to 7 days. The web app also saves your layout preferences in your browser. We don't use analytics or advertising cookies. The bot check at sign-up is provided by Cloudflare Turnstile under Cloudflare's own privacy policy.
Why we use it
- To run dirhp: create your account, sign you in, store and sync your designs, and send your confirmation emails.
- To keep dirhp secure: check sign-ups for bots, limit repeated attempts and look into abuse.
- To fix problems and improve dirhp, using usage records.
We use your design data only to run dirhp for you. We don't sell your data, and we don't train AI models on it.
Who processes it for us
These providers handle data for us, only to provide their service to dirhp:
- DigitalOcean (Singapore): hosts dirhp's servers and database, including your design data.
- Supabase (Singapore): handles sign-in and passwords. It receives your name, email and password.
- Cloudflare (global network): hosts the dirhp.io website and its forms, checks sign-ups for bots and serves downloads. It receives your IP address for the bot check.
- Resend (sends from Japan, keeps its records in the United States): sends confirmation and set-password emails. It receives your email address, your first name and the link.
- Zoho: hosts the help@dirhp.io mailbox, so it holds any email you send us.
- Google Fonts: the dirhp.io website loads its fonts from Google, so Google sees your IP address when you visit.
The AI assistant you connect (such as Claude or ChatGPT) runs on your own account with its provider. Design data it reads through dirhp goes to that provider under your agreement with them, not ours. dirhp does not see your conversations.
Data stored outside Singapore
Some of these providers store or process data outside Singapore, including in the United States. We use providers that commit, in their terms with us, to protect personal data to a standard comparable to the PDPA.
How long we keep it
- Account and design data: while your account is open. If you or we end your use of dirhp, you have 30 days to export your data, and then we delete it. If you ask us to delete it sooner, we do so within 30 days of your request.
- Usage records and session activity logs: 7 days.
- Sign-up requests that are never completed: 30 days.
- Waitlist sign-ups and messages to us: until you ask us to delete them.
- Backups: deleted data can remain in server backups for up to 4 weeks before those backups are replaced.
How we protect it
All connections to dirhp are encrypted (HTTPS). Supabase handles passwords, and dirhp keeps sign-in and device codes only in hashed form. Access to dirhp's servers and database is limited to the person who runs dirhp.
Your rights
You can ask to see the personal data we hold about you, to correct it, or to have it deleted, by emailing help@dirhp.io. We reply within 30 days.
You can withdraw your consent at any time by emailing us. We then stop using your data and delete your account, so you can no longer use dirhp.
If you're not satisfied with our reply, you can complain to Singapore's Personal Data Protection Commission.
Changes
We'll tell you before changes to this notice take effect.
Last updated: 16 November 2026