# Orgma Quality privacy notice
Version quality-2026-10-15.
## Who uses information and why
Triton Safety Limited trading as Orgma, company 11602941, is controller for its account administration, billing, support, security and legal records. Write to support@getorgma.com or 7 Bournemouth Road, Chandler's Ford, Eastleigh, SO53 3DA, United Kingdom.
The organisation operating a Quality account normally controls personal data in its project records. Orgma processes that material on its instructions under the Quality data processing schedule. Contact that organisation about its project use; Orgma will assist or forward requests where appropriate.
| Information | Purpose and controller basis |
| --- | --- |
| Name, business email, organisation, account identifiers and access roles | Administer accounts and invitations; perform a contract with an individual customer, or pursue the legitimate interests of providing the organisation's service to authorised users. |
| Subscription, invoice, tax and payment references | Administer payment and the service contract; meet applicable accounting and tax obligations. Card details are handled by the payment provider. |
| Support correspondence and request verification | Resolve problems and requests; legitimate interests in service administration, or applicable legal duties. |
| Authentication, activity, delivery and error records, including IP and device information where logged | Protect access, investigate incidents and operate a reliable service; legitimate interests in security, prevention of misuse and fault diagnosis, or applicable legal duties. |
| Agreement version and acceptance records | Establish the contract and demonstrate authority, notices and compliance; contract, legitimate interests in keeping business records, and applicable legal duties. |
Project material may contain names, employers, roles, inspection notes, photographs, signatures, location references, evidence and decisions about individuals' work. The account organisation determines its lawful basis, notices, appropriate retention and recipients. Orgma does not use Quality evidence to train an AI model or make automated decisions about a person's competence. Quality has no AI processing feature.
Operational email providers may use automated security and abuse screening, including AI-assisted processing, under their disclosed terms. This is distinct from analysing project evidence in Quality. Resend stores email content and delivery records in the United States; selecting an Ireland sending region does not change that storage location.
Information comes from users, inviting organisations, their project records, support interactions and operational providers. Authentication and necessary account details are required to supply access; declining them can prevent account use. Avoid unnecessary personal information in photographs and free text. Special category or criminal offence information is outside the intended routine use and requires a separate lawful assessment and suitable safeguards.
## Access, recipients and transfers
Internal users have access according to their account role. A project client invitation permits reading the records and evidence across that project, not just a single assigned inspection. Ask the inviting organisation to change access where necessary.
Orgma uses Supabase for authentication, database and evidence storage, Netlify for hosting and server functions, and Resend for transactional email. Stripe handles billing and payment activities under the applicable payment terms and its privacy notice. Backblaze stores separate recovery copies of original evidence. Authorised support personnel and professional advisers receive information only as needed. Orgma may disclose information where lawfully required or necessary to establish or defend legal rights.
A database region is not a promise that all email, support and hosting processing stays in that region. Before restricted transfers occur, Orgma must establish the applicable adequacy arrangement or contractual safeguards and required transfer assessment. Ask support for information about the arrangements used.
## Retention and choices
We retain information for the purposes below, subject to specific legal requirements and documented holds. These periods do not authorise indefinite retention of project evidence.
| Category | Retention and review |
| --- | --- |
| Routine support correspondence | 12 months after the case closes; remove temporary diagnostic attachments within 30 days, or sooner when no longer needed. |
| Routine security and diagnostic records controlled by Orgma | Up to 90 days. Necessary evidence for a specific incident or claim is separated, access restricted and a review date recorded. Provider logs follow the provider's applicable schedule. |
| Agreement acceptance and material contract records | For the service term and six years after the relationship ends, subject to a documented continuing claim. |
| Company accounting and necessary billing records | Six years from the end of the last company financial year to which they relate, or longer where required. This does not justify keeping project photographs or inspection contents. |
| Shared sign-in identity | While needed for any remaining Orgma service. Closing one Quality account must not delete another account's access. Review redundant identity records after the last applicable service closes. |
| Free allowance and abuse-prevention claims | Review within 90 days after closure and at least annually thereafter; retain only the identity link still necessary to prevent repeated allowance claims, with a recorded reason and next review. This is not anonymous data or authority for indefinite retention. |
| Recovery suppression, closure and integrity metadata | Keep the minimum needed to prevent erased records returning while any recoverable copy may remain. Review backup-expiry evidence at closure and at least every 90 days until final disposal can safely be confirmed. Never remove the suppression record while an affected recovery copy could still be restored. |
A documented legal hold must identify the reason, scope, responsible person and next review date. Access is restricted. No controller-retention exception permits keeping unrelated project contents. Orgma reviews these categories through its controlled retention register; this does not imply that every category has an automatic deletion job.
Project data follows the controller's documented return and deletion instructions. At closure, an authorised support administrator verifies authority and confirms return, live erasure and applicable backup expiry arrangements. Separate temporary export copies are removed within seven days of confirmed receipt, with a maximum of 30 days from creation. Minimal return-receipt metadata is retained for 12 calendar months after case closure unless a specific recorded hold requires longer; this does not include the exported project contents. Where immediate deletion from recovery copies is not feasible, records are put beyond routine use until secure expiry and erasures are reapplied during recovery. Subscription cancellation alone is not an erasure request.
Depending on the legal basis and circumstances, individuals can request access, correction, erasure, restriction and portability. **You can object to processing based on legitimate interests.** Where consent is used, it can be withdrawn without affecting earlier lawful processing. Orgma will explain any applicable limitation and respond within the applicable legal deadline. Verify identity proportionately; do not send passwords or complete payment-card details to support.
Send privacy requests or complaints to support@getorgma.com. Orgma will acknowledge and investigate them and provide a response or progress update under applicable requirements. You can also complain to the Information Commissioner's Office at https://ico.org.uk/make-a-complaint/ without first exhausting Orgma's process.
The service uses necessary session storage for sign-in and security. Any future optional analytics or marketing tracking requires an appropriate notice and choice before use. Material changes to this notice will be communicated through the service or appropriate account contact.