Last updated 2026-10-10
This policy describes how Skycat handles data on the Skycat Platform (the "Service"), both an organisation's own data ("Customer Data") and personal data about the people who sign in to use it.
Account data and Customer Data are used only to provide the Service to the organisation that owns them: authentication, processing pipelines (e.g. NDVI/raster analysis, 3D reconstruction), and the features an organisation's members use directly. Skycat staff access an organisation's data only for support, and only through the platform's own impersonation tool, which is time-limited, read-only, and recorded in that organisation's own audit log with the staff member's name and reason.
The Service runs on infrastructure operated by Fly.io (application hosting and database) and Cloudflare (object storage and edge delivery of shared links). Transactional email (invitations, password resets) is sent through Resend. None of these providers is given access to Customer Data beyond what is necessary to host or deliver it.
While an organisation remains a customer, Customer Data is kept for the life of the account. Members free storage through Trash on Usage; content in Trash still counts toward the organisation's storage until emptied. Removal at the end of an agreement follows the offboarding process below.
When an organisation's agreement with Skycat ends, its administrator (or Skycat staff, acting on that administrator's instruction) can export the organisation's data before it is removed. Purging an organisation is irreversible: every product's records and stored files for that organisation are deleted, pending invitations and memberships are removed, active share links are revoked, and any member account with no other organisation is anonymised. A departing member's account is never left holding an identifiable record purely because deleting it would break an audit trail Skycat is required to keep for other organisations.
Every organisation's data is isolated at the database level (row-level security keyed to the organisation), and the underlying database is backed up automatically; see the platform's deploy documentation for the backup schedule and restore procedure available to Skycat staff.
A person whose account data is held on the Service can ask their organisation's administrator, or Skycat directly, to correct or delete it, subject to the offboarding and retention rules above.
Questions about this policy, or a request concerning personal data: hello@skycatdrone.com.
← Back to sign in