# Orgma Quality data processing schedule
Version quality-2026-10-15.
## Processing particulars
The subscribing organisation is controller of personal data placed in Quality. Triton Safety Limited trading as Orgma is processor. Orgma's own billing, account, legal and security controller activities are described separately in the privacy notice.
Processing consists of hosting, organising, storing, presenting, sharing with authorised users, exporting, protecting, returning and deleting inspection and corrective-action records and original evidence. It lasts for the service and the documented return, deletion and recovery-copy expiry periods. Instructions comprise the agreement and authorised service or support requests. The customer determines lawful purposes, access, notices and retention instructions, and ensures it is entitled to supply the data.
Data subjects can include customer personnel, subcontractors, client reviewers and people appearing in project evidence. Data can include names, business contacts, employers, roles, photographs, signatures, project and location references, inspection findings, comments, decisions and access records. Quality has no AI feature for analysing these records and does not perform routine biometric identification. Special category or criminal offence processing is outside the intended routine use. Any exceptional sensitive use requires a separate assessment and agreed safeguards.
## Obligations
Orgma will process on documented instructions, including transfers, unless law requires otherwise, and give notice where lawful. It will tell the customer if an instruction appears unlawful. Authorised personnel must be bound by confidentiality and access limited to their duties.
Orgma will maintain appropriate security measures, help the customer respond to individual rights and complaints, and assist with security, breach assessment, impact assessments and regulator consultation taking account of the processing and information available. It will notify the customer without undue delay after becoming aware of a personal data breach, supply available facts and provide updates. The customer retains responsibility for its regulatory notifications.
The customer generally authorises the providers disclosed in this schedule. Orgma will impose equivalent applicable processing obligations and remain responsible for its subprocessors' performance. It will give at least thirty days' notice of intended direct provider additions or replacements and promptly pass on available onward-provider notices, with a meaningful opportunity to object on reasonable data protection grounds. If notice or safeguards cannot be secured, affected new processing must not begin. The parties will seek a suitable alternative; if unavailable, the customer may end the affected service and receive a proportionate refund for unused prepaid service.
At the customer's choice Orgma will return or delete processed personal data when service ends and delete copies unless law requires retention. It will identify and restrict any retention exception. Orgma will provide compliance information and allow proportionate audits and inspections with confidentiality and security protections; those arrangements must not defeat the customer's legal rights.
## Providers and international processing
| Provider | Processing role and location |
| --- | --- |
| Supabase Pte. Ltd | Authentication, database and private original evidence storage. The customer database is configured in Ireland. Operational and support processing may occur elsewhere under the applicable provider arrangements. |
| Netlify, Inc. | Website hosting and server functions. Customer server functions run in Ohio, United States; hosting delivery can involve other locations. |
| Plus Five Five, Inc., trading as Resend | Transactional authentication and notification email, with message and log storage in the United States. The configured Ireland sending region does not move stored email data to Ireland. |
| Backblaze, Inc. | Separate evidence recovery copies in the selected EU Central region. Support and other processing can occur outside that region. |
Stripe handles Orgma billing and payment activities under the applicable payment agreements; it is not presented as a processor of all project evidence. Quality has no AI analysis feature. Operational providers may use automated security and abuse screening, including AI-assisted processing, under their own disclosed processing terms. Resend states that a small sample of emails is screened on its dedicated RunPod infrastructure; ordinary email API sending is not sent to Anthropic. This onward email processing is distinct from analysis of project records in Quality.
A regional database or bucket does not guarantee that all support and delivery remain there. Before a restricted transfer, Orgma will establish a valid transfer mechanism, any required assessment and supplementary measures. Adequacy reliance requires checking the recipient and the scope of the arrangement; contractual safeguards must include the applicable UK instrument where needed. Details of safeguards will be available on request.
## Security, recovery and closure
Measures include verified sessions, account and project permissions, database row access policies, private evidence storage, bounded upload operations and server-only privileged credentials. Managers must review invitations because internal access is account-wide and client access covers the invited project. Access removal must preserve appropriate historical attribution without leaving the removed person authorised.
Orgma will maintain incident response, vulnerability handling, credential rotation and scoped recovery procedures. Recovery must include records and originals, integrity checks, appropriate monitoring and application of recorded erasures. Original evidence is backed up separately on an hourly schedule. Existing backup copies have a seven-day protection period before eligible obsolete copies can be pruned; this is not a promise that all copies disappear seven days after an account closes. Each customer closure requires a verified instruction, confirmed scope, reconciliation of outstanding processing, review of retention exceptions and a separate record preventing erased data returning through recovery. There is no promised security certification, zero provider retention, guaranteed restoration time or maximum data loss.
An authorised customer representative can request return or deletion through support@getorgma.com, including when paid access is paused. An authorised support administrator will manage each verified request, agree a secure delivery method and record its scope, return deadline, live erasure status, applicable backup expiry and any specific legal exception. The normal supported export window is 30 days after verified closure is confirmed; verified earlier deletion instructions are reviewed separately. This is a support-managed procedure. Cancellation alone does not erase records. No automatic ninety-day self-service export or automatic whole-account erasure is represented for Quality.
Pending secure deletion, recovery copies that cannot immediately be selectively erased must be beyond ordinary use and expire under a disclosed cycle. If a copy is restored, recorded erasures must be reapplied before normal access resumes. Other organisations and shared user identities must remain intact. Completion must be evidenced, including any separately retained billing or security records and the lawful reason. The privacy notice separately specifies the treatment of contract, billing, security, abuse-prevention and recovery-suppression records; these categories are not necessarily erased with project contents.