Privacy policy
Last updated: 14 November 2026.
Who we are
Orgbright is provided by Ironbit Ltd, a company registered in Northern Ireland (company number NI729290), registered office 15 Longfield Lane, Desertmartin, Magherafelt, BT45 5NW, Northern Ireland. We are registered with the Information Commissioner's Office, registration ZC265119. Contact: privacy@orgbright.app.
Our role
When an organisation installs Orgbright, that organisation is the controller of its staff's data and we act as its processor, under our data processing agreement. For our own customer accounts, billing and website, we are the controller.
What Orgbright accesses and why
| Data | Source (Google permission) | Why | Stored? |
|---|---|---|---|
| Name, email address, job title, department, location, work phone, profile photo address, organisational unit, manager | Google directory, read-only (admin.directory.user.readonly), through a service account the organisation's admin authorises | To draw the org chart and staff directory for people in that organisation | No. Held in a temporary cache for at most 10 minutes to keep the chart quick, then discarded. Never written to our database |
| Whether a person is a Google Workspace™ administrator | Google directory, read-only | To decide who can change Orgbright settings | Cached for up to 10 minutes |
| Your email address | Google sign-in (userinfo.email) | To identify you in the Gmail™ side panel and find your organisation | In the activity log of actions you take |
| Custom attributes, employee ID, cost centre, employee type, mobile number, desk, and dotted-line manager and assistant relations on each profile | Google directory, read-only (admin.directory.user.readonly) | To show the fields and reporting lines your admin chooses | No. Same 10-minute cache as above |
| Settings an admin chooses (company name, logo link, colours, department colours, which fields show and their labels, people and teams to hide, extra admins, open roles). These include the email addresses of people you hide and of extra admins, the addresses of the managers open roles report to, department names, and the address of the admin who installed Orgbright | Orgbright settings | To run the service | Yes, until deleted |
| Values your Orgbright admins enter in your own fields, such as teams or start date (only if you turn on editing) | Entered in Orgbright, saved straight into your Google directory (admin.directory.user, admin.directory.userschema) | To show them on the chart and directory | No. They are kept in your Google directory, not by Orgbright |
| Field definitions (names, types, dropdown choices such as team names, which are required and who can see them) and which Google field fills location and phone | Orgbright settings | To run the service | Yes, until deleted |
| Activity log (who changed settings or billing, who edited whose details and which fields, and when; never the values) | Orgbright | So admins can see what changed | Yes, until deleted |
| Billing contact and company name | Stripe Checkout | To take payment and issue invoices | Held by Stripe; we keep the Stripe customer and subscription IDs |
Orgbright never reads, stores or sends the content of your email, files or calendars. It only changes your Google Workspace™ if you turn on editing, and then only the Orgbright custom attribute group, when one of your admins saves a person's details.
Google API Services User Data Policy
Orgbright's use and transfer to any other app of information received from Google APIs will adhere to the Google API Services User Data Policy, including the Limited Use requirements.
In practice: we use Google user data only to provide the org chart and directory features you see in Orgbright. We never sell it, we don't use it for advertising, and it is not used to train AI or machine-learning models. People at Ironbit don't read it, except with your permission, for security investigations, to comply with law, or where it has been aggregated and anonymised for internal operations.
Sub-processors
| Provider | Purpose | Location |
|---|---|---|
| Google Cloud (Apps Script, Firestore) | Running Orgbright; storing settings and the activity log (Firestore); the 10-minute directory cache (Apps Script) | Firestore in London (europe-west2); Apps Script on Google infrastructure |
| Cloudflare | Serving the website and the chart page, payment webhooks | Global edge network |
| Resend | Sending sign-in link emails (recipient address and the email itself) | EU and US |
| Stripe | Payments and invoices | UK, EU and US |
Transfers outside the UK are protected by UK adequacy regulations or the UK International Data Transfer Addendum. We give customers 30 days' notice before adding a sub-processor.
How long we keep data
- Directory details: at most 10 minutes in a temporary cache.
- Settings and activity log: while you use Orgbright. When you remove Orgbright's access in Google Admin™ (domain-wide delegation), we delete them 30 days later. Uninstalling the add-on on its own doesn't remove that access, so remove both, or email us and we'll delete everything straight away.
- Billing records: as long as the law requires (normally six years), held by Stripe and in our accounts.
How we protect your data
Everything travels over HTTPS. Access to Google is read-only and limited to one permission, unless you turn on editing, which adds two permissions used only for Orgbright's own custom attribute group. Sign-in links are signed and expire after 8 hours. They act like a key: anyone who has the link can open the chart until it expires, so please don't forward them. Only people in your organisation's directory can open its chart. Settings are stored in Google Cloud Firestore, encrypted at rest, and only Ironbit staff who need to can reach them.
Your rights
Staff should first contact their own organisation, which controls their data. You can also email privacy@orgbright.app. You have the right to complain to the Information Commissioner's Office.
Changes
We'll update this page when what we collect changes, and tell customers by email before any material change.