Security
Safety is built in, not bolted on.
Data separation, consent, access keys, human approval, and audit trails are part of how Aether stores data — not settings you have to remember. Aether doesn’t claim certifications it hasn’t earned.
Six protections on every record.
Three kinds of key. Each does only its job.
Pick one to see what it can do.
CanSend data into Aether
Can’tRead or change anything
Usually held byWebsites, apps, integrations, server jobs
Sign-in sessions live only in the app — public sites never store passwords. Older API keys are shown once when created, and can be rotated from Settings.
Your data stays yours.
OwnershipYou own your raw data and records.Your data is never shared with another customer.Nothing is exported without your approval.
Keeping and deletingYou choose how long data is kept.Deleting removes your raw data and stops collection.Export first if you want a copy.
Hiding sensitive fieldsPasswords, keys, and tokens are removed from exports.The SDKs strip sensitive fields before anything is sent.
Run it where you need it.
From shared cloud to fully offline. The protections stay the same.
Shared cloudthe defaultDedicatedyour own resourcesSovereignkept in your regionOn-premiseyour infrastructureOfflineno outside network
What Olympus Labs won’t build.
Secret monitoring of peoplePolitical manipulationAdding data people didn’t agree toUnlawful targetingSharing one customer’s data with another
Designed to be ready for GDPR and SOC 2. No certification is claimed today — current documents are shared through a security review.
Ask for what your review needs.
Answers come from the live system, not a marketing sheet.