Data & Security

01Where data lives

• Website, database and file storage run on Google Cloud infrastructure via Firebase.
• Raw flight data and working project files are held on access-controlled cloud storage with versioned backups.
• Deliverables are issued through expiring secure links, or pushed directly into your own storage where you prefer.
• Data residency can be provisioned in a specific region where a contract requires it - raise this at the proposal stage.

02Access control

• Administrative access requires an authenticated account with an explicit role claim; there are no shared logins.
• Client files uploaded through the website are never publicly readable. Storage rules deny public read on the upload path outright.
• Access to a project is limited to the team members working on it.
• Every write to project or content records passes through the authenticated API, which is the single authorisation choke point.

03Encryption

• All traffic is served over HTTPS with HSTS. There is no unencrypted route into the platform.
• Data is encrypted at rest by the storage platform.
• Physical media, where a client requests delivery on a drive, is encrypted and the passphrase is transmitted separately.

04Backups and continuity

• Firestore data is backed up daily with point-in-time recovery available within the retention window.
• Project deliverables are retained in redundant storage for the duration of the engagement plus the agreed retention period.
• Raw capture data is retained for 12 months by default so a reprocess is possible without re-flying.
• Backup restoration is tested periodically rather than assumed to work.

05Retention and deletion

• Enquiry data that does not become a project: 24 months.
• Files attached to unsuccessful enquiries: 12 months.
• Project records and deliverables: engagement duration plus 7 years for contractual and tax purposes.
• Raw capture data: 12 months by default, extendable or shortened on request.
• You may request deletion of your data at any point, subject to any legal retention obligation we are under. We confirm deletion in writing.

06Confidentiality of client data

Client site data is commercially sensitive - it shows exactly what is on your site, on a dated basis. We treat it accordingly.

We do not publish client data, use it in marketing, share it with other clients, or use it to train any model. Portfolio entries appear only with explicit written consent, and we are happy to execute your own NDA in preference to relying on ours.

07Flight data and regulatory records

• Telemetry from every sortie is logged and archived with the project, so any question about what the aircraft did on a given day has a factual answer.
• Digital Sky filings, permissions and pilot certification records are retained as required by DGCA regulation.
• These records are made available to you on request where they relate to work flown on your site.

08Incident response

If we become aware of a security incident affecting client data, we will contain it, assess the scope, and notify affected clients without undue delay with a factual description of what happened, what data was involved and what we are doing about it.

Report a suspected vulnerability or incident to hello@xorian.example. We investigate every report and will not pursue anyone who reports a genuine issue in good faith.

09Handover at the end of an engagement

• You receive all deliverables in open, documented formats that do not require a subscription to open.
• Raw capture data is available to you on request at any point during the retention period.
• Coordinate systems, datums, transformations and processing parameters are documented so a different provider could continue the work.
• We do not hold data hostage as a commercial lever. Ever.