Privacy policy

What personal data Rabbinatix keeps, why, where it's stored, who processes it for us, how long we keep it and how you can see, export or delete it. We collect what the product needs to work: no advertising, no tracking, no selling of data.

Last updated 19 November 2026

1. Who is responsible

Darius A. Bualan Jr., as an individual until the company that will run Rabbinatix is registered, is responsible for the personal data in your account. Write to us through the contact form at rabbinatix.com/?contact=privacy#contact (topic: Privacy or my data). Data protection officer: Darius A. Bualan Jr., through the same contact form. When the company is registered, we will tell you before it takes over.

For the content of an organization (its systems, tickets, chat and so on), the organization is responsible for the personal data its members put in, and we process it on the organization's behalf.

2. What we keep

  • Your account: name, email address and a password, which Firebase Authentication keeps as a salted hash; we never see it. If you sign in with Google, Google gives us your name and email address.
  • Your profile and settings: your avatar colour or photo, and what you choose to add (title, short bio, location and time zone); who can open your profile follows the visibility you choose. Also your role in each workspace, your default workspace, and your notification choices.
  • What you and your team create: systems, endpoints, API specifications, contracts, flows, logic, tickets, pages, whiteboards, screens, comments, chat messages, meetings in the calendar, files you upload, and the organization's activity and audit log, which records who did what and when, with their name and email address.
  • While you're signed in: whether you're online and typing in chat, so others see it. It is removed when you close the app.
  • Voice and video calls: the audio, video and shared screen go directly between the browsers in the call and are never recorded or stored by us. To connect, the browsers exchange network details, including IP addresses, through our database and a Google connection server; these are removed when the call ends.
  • App errors: when something breaks in the app, it sends us the error message, the page (without its query or any share link's key) and the app version, so we can fix it. Errors of the same kind are counted together; a kind not seen for 90 days is deleted.
  • Messages to us: what you send through the contact form (with the name, email address and company you give) or in a report about abuse, and our replies. Your IP address is only used, as a one-way hash, to limit how many messages one address can send.
  • Bot protection: the app uses Google reCAPTCHA Enterprise (Firebase App Check) to check that requests come from the real app. Google receives information about your browser and device for that, under Google's privacy policy.
  • Time away, on Standard and up: the days you, your team lead or an admin mark you away, the kind (leave, public holiday or training) and who stands in for you, which everyone in the organization sees. No reason is kept. It goes when you leave the organization.
  • The org chart, on Standard and up: who you report to, your position in the organization and the departments its teams are in, as people who manage teams set them, which everyone in the organization sees. It never changes what you may do. You leave it when you leave the organization, and the people who reported to you then report to your manager.
  • Integrations: the webhook and email addresses admins connect, a log of each delivery, and API and watcher tokens, which are shown to you once and stored only as a hash.
  • Emails we send: notifications go into a mail queue with the recipient, subject and text, which our email provider sends.
  • In your browser: Firebase keeps you signed in, reCAPTCHA keeps what it needs to recognize the real app, and the app remembers your theme, layout and view choices. These stay on your device. We use no advertising or analytics cookies.

We don't use analytics or tracking. If we add analytics, we update this policy first.

3. Early access questions and feedback

  • When you set up a workspace we ask, optionally, about your company: its size, industry and country, how you heard of Rabbinatix and what you want to use it for, and whether we may contact you about your experience or invite you to a short call. You can skip it, and change or remove your answers in your profile. If you pressed Tell me when it’s ready on chat’s AI assistant page before it opened, we keep that you asked, so we can tell you in the app.
  • Feedback you send from the app: what you wrote, the page you were on, and your name and email address so we can reply.
  • A one-time question after two weeks of use: how disappointed you would be without Rabbinatix, and what would make it better.

We use these to understand who uses Rabbinatix, what to build first and how to price it later. We only contact you about your experience if you said we may. Your company answers are kept while your account exists and deleted with it; feedback and survey answers are kept for 24 months.

4. Why we use it

  • To provide Rabbinatix to you under the terms of service: your account, your workspaces, collaboration, notifications and integrations.
  • To keep it secure: checking permissions, the audit log, and stopping abuse. This is in our legitimate interest and yours.
  • To answer you when you write to us.
  • To meet legal obligations, for example keeping billing records.

AI assist works out its answers in your browser from your organization's data, and sends nothing to an outside AI service. Only the AI assistant in chat uses an outside AI provider, as described under "Who processes it for us".

5. Where it's stored

Rabbinatix runs on Google Cloud through Firebase. The databases (Cloud Firestore and the Realtime Database), the server code (Cloud Functions) and file storage (Cloud Storage) are in Google Cloud's asia-southeast1 region, in Singapore. Firebase Authentication and Firebase Hosting are global Google services, so sign-in data and the website can be handled in other countries. Emails are sent through Resend (United States).

Where data leaves your country, we rely on the safeguards our providers offer in their data processing terms, such as standard contractual clauses.

6. Who processes it for us

  • Google LLC and Google Cloud (Firebase Authentication, Cloud Firestore, Realtime Database, Cloud Functions, Cloud Storage, Firebase Hosting): hosting and storing everything above.
  • Google Fonts: the website's fonts are loaded from Google, which sees your IP address when your browser fetches them.
  • Google reCAPTCHA Enterprise (through Firebase App Check): checking that requests come from the real app.
  • Google's connection (STUN) server: helping the browsers in a call find each other; it sees their IP addresses.
  • Resend (United States): sending the emails: sign-up checks, password resets, invites and notifications.

The AI assistant in chat uses the AI provider a member connects with their own key (Anthropic, OpenAI or Google), and only when someone who manages the organization has turned it on. When that member uses it, what they ask and what the assistant reads from the organization to answer (as that member may see it) goes to that provider, under the member's own agreement with it. Rabbinatix keeps the key encrypted, never shows it again, and keeps the member's conversations, private to them, until they delete them or their account. We don't send anything to an AI provider otherwise.

A member can also connect other apps (such as Jira or GitHub) for their own assistant in chat, with their own secret for that app, unless someone who manages the organization turned that off. The assistant then sends calls to those apps as that member, and what it sends (which can include what it read from the organization) goes to that app, under the member's or their company's agreement with it. Rabbinatix keeps the secret encrypted, adds it only to calls to that app's address, never shows it again and never sends it to the AI provider, and deletes it when the member removes the app, leaves the organization or deletes their account.

Webhook receivers get event details only when an admin of your organization connects them. They are the organization's choice, not our processors. We don't sell or rent personal data, and we share it with authorities only when the law requires it.

7. How long we keep it

  • Your account: until you delete it.
  • Time away: with the organization's content, until you leave it.
  • The org chart: with the organization's content; your place in it until you leave it.
  • An organization's content: until an owner deletes the organization. Deleting it removes its documents, files, URL, tokens, the APIs it published and its chat presence at once. A workspace on a paid plan has its subscription canceled first.
  • When you delete your account, your Personal workspace and the organizations where you were the only member are deleted, and you leave the others. What you made there, and the audit entry that you left, stay with that organization, under your name.
  • Some records are removed on their own sooner: notifications after 90 days, webhook delivery logs after 30 days, activity and audit log entries and ticket history after a year, exports a week after they were made, app error reports 90 days after the error was last seen, contact form messages and closed abuse reports after a year.
  • Backups: daily backups, each deleted after 7 days.
  • Emails we sent, in the mail queue: 30 days, then deleted automatically.

8. Who at Rabbinatix can see it

Only the people who run Rabbinatix, and only to keep it working and safe: to answer you when you ask for help, to handle a report about abuse or a privacy request, and to fix errors. Our admin tools record every change we make, a change to your organization shows in its own activity log as "Rabbinatix support", and we don't read your organization's content for any other reason.

9. Your rights

Depending on where you live, you can ask to see, correct, export or delete your personal data, object to or limit how we use it, and complain to a data protection authority. Much of this you can do yourself:

  • Correct: change your name and preferences in the app.
  • Export: an organization's admins can download all of its data as one JSON file in Settings → General → Export data. Secrets (webhook signing keys, the values of test data's secret fields), members' private chat state and unpublished draft changes are left out.
  • Delete your account: My profile → Account & security → Delete your account, confirmed by typing your email address. If you are the only owner of an organization with other members, hand ownership over or delete it first.
  • Delete an organization: its owners can, in Settings → General.

For anything else, write to us through the contact form at rabbinatix.com/?contact=privacy#contact (topic: Privacy or my data). We answer within one month. You can also complain to the National Privacy Commission of the Philippines (privacy.gov.ph).

10. Security

Data travels over HTTPS and is encrypted at rest by Google Cloud. Database rules check your role on every read and write; server-only data such as signing keys and tokens can't be read by the app at all, and the audit log can't be changed by anyone. If a breach puts your data at risk, we tell you and the authorities as the law requires.

11. Children

Rabbinatix is a tool for work and is not meant for anyone under 16.

12. Changes to this policy

When we change this policy we update the date at the top of this page, and email account holders about changes that matter to them before they apply.