Stored in Morocco
Telemetry, imagery, mission records and backups are written to infrastructure located on Moroccan territory. Not a regional edge cache — the primary store.
Data residency
Survey imagery is infrastructure data. Inspection footage is asset data. Both tend to leave the country the moment a fleet is flown on a foreign cloud. Ours does not.
Four commitments
Telemetry, imagery, mission records and backups are written to infrastructure located on Moroccan territory. Not a regional edge cache — the primary store.
The hosting contract, the operating entity and the data are all under national jurisdiction, and disclosure follows Moroccan legal process alone.
Nothing leaves without an export you trigger. Every export is logged, signed and attributable to the account that requested it.
Encryption at rest and in transit as standard; on request, key custody sits with your organisation rather than with us.
Specification
Primary storage — Casablanca
Mission data is written to the national datacentre first and replicated within the territory.
Retention set by you
Retention windows, purge schedules and legal hold are configured per fleet at onboarding.
Foreign-cloud payloads flagged
If a payload vendor phones home, we detect it during integration and either block it or tell you exactly what it sends.
No silent egress
Any outbound route not declared in the residency plan is treated as a fault and stops the flight record from being signed.
Specification
| Item | Standard | Note |
|---|---|---|
| Primary storage | Morocco | National datacentre |
| Backup | Morocco | Second site, same jurisdiction |
| Encryption at rest | AES-256 | Per-fleet keys |
| Encryption in transit | TLS 1.3 | Aircraft link included |
| Key custody | Client-held | On request |
| Export | Client-triggered | Signed and logged |
| Retention | Configurable | Default 24 months |
| Audit trail | Immutable | Per access and export |
Primary storage
Morocco
National datacentre
Backup
Morocco
Second site, same jurisdiction
Encryption at rest
AES-256
Per-fleet keys
Encryption in transit
TLS 1.3
Aircraft link included
Key custody
Client-held
On request
Export
Client-triggered
Signed and logged
Retention
Configurable
Default 24 months
Audit trail
Immutable
Per access and export
Where exactly the data sits, who can compel access, what happens if you leave. We would rather answer those before a contract than after.