Privacy policy
F.R.I.D.A.Y is an operations console: it watches servers, containers and databases for the organisation that runs it, and the companion mobile app lets an approved person acknowledge an alert or approve a fix. This policy explains what the console and the app store, why, and how to have it removed.
Who controls the data
This installation is run by Seattle Aviation Solutions. That operator is the data controller: they decide who gets an account and what the console monitors.
Privacy questions and deletion requests: ashi@seattleav.com.
What is collected
Account and sign-in
- Name, email address and password hash. The password itself is never stored; only a one-way hash is.
- Single sign-on identity — the email address, display name and directory object id returned by the organisation's identity provider when you sign in that way. No access token from that provider is kept.
- Session records — a session cookie, its expiry and the time of last use, so an administrator can sign a user out.
The mobile app
- Device details — platform, device name, model, OS version, app version, locale and timezone, so a notification can be delivered and an administrator can tell which device approved what.
- A push token from Apple or Google, used only to deliver alert notifications to that device.
- A public key generated on the device, when the app signs approvals. The private key never leaves the device.
- A jailbreak or root flag reported by the app. Such a device may read but never approve.
- Refresh tokens and notification preferences such as quiet hours.
The app does not collect your location, contacts, photos, health data, advertising identifiers, or a list of other apps. It uses no advertising SDK and does not track you across other apps or websites.
Operational data
The console monitors the infrastructure its operator points it at. That data belongs to the operator, not to the person using the app:
- Host and container metrics — CPU, memory, disk, network, container state and restarts.
- Logs, with secrets masked before a line is stored or sent to a model.
- Application traces — timings and errors for requests.
- Database metrics — connections, query rates and space usage, when database monitoring is enabled.
- An audit trail — who approved or ran an action, and when. This is a security record and is kept even after an account is closed.
Alert email
When an alert is mailed it contains the relevant host, service and log excerpt, and is sent through the operator's own mail provider to the recipients they configured. A reply to such a message is stored so the conversation can continue in the console.
Automated analysis
When the remediation assistant is enabled, it sends the incident's evidence — the alert text, relevant log lines, metrics and container state — to a large-language-model provider for analysis. Credentials and secrets are redacted first. The model only suggests: a person approves every action before it runs. The assistant makes no decision about you and is not used to profile individuals.
Cookies
The console sets one session cookie (and, during single sign-on, a short-lived state cookie) so you stay signed in and requests cannot be forged from another site. There are no advertising, analytics or third-party tracking cookies.
Why it is processed
- To operate the service — sign you in, show the state of the monitored systems, deliver the alerts you asked for.
- To keep it secure — the audit trail, session revocation, and the device signature required before an approval is trusted.
- To meet the operator's legal obligations — retaining security records where the law requires it.
Sharing
Nothing is sold and nothing is shared for advertising. Data reaches:
- The operator and the administrators they appoint.
- Infrastructure providers the operator chose — the server running the console, the mail provider that delivers alerts, and any model provider named above.
- Apple or Google, for push delivery only.
- The organisation's identity provider, which authenticates you.
- Authorities, where the operator is legally required to disclose.
How long it is kept
- Account details — while the account exists.
- Session and refresh tokens — until they expire or are revoked.
- Logs and metrics — per the operator's retention setting.
- Audit records — retained after account closure, because they record what changed on the operator's systems.
Your choices
You can ask for a copy of your account data, ask for it to be corrected, or ask for the account to be deleted. The steps are on the account deletion page. Write to ashi@seattleav.com.
Security
Traffic is served over HTTPS. Passwords are stored as salted hashes, credentials the console needs to reach a host are encrypted at rest and used only for the one approved action, access is limited by role, and every action on a host is recorded.
Children
The console is a workplace tool. It is not directed at children and is not intended for anyone under 16.
Changes
Material changes are published here with a new date. Continuing to use the console after a change means the updated policy applies.
Contact
Seattle Aviation Solutions
ashi@seattleav.com
Governing law: Washington, USA
console.seattleav.cloud