Privacy Policy
This policy explains how Odyssey Developments (“Odyssey”, “we”) handles personal data when you visit wardeye.tech or use the Wardeye web app, Mac app and mobile apps. Biometric data has its own Biometric Data Notice.
1. Who is responsible
For account, website and billing data, Odyssey is the controller. For the data an organisation puts into Wardeye about its own people and counterparties (confirmation requests, enrolled people, mailbox flags), the organisation is the controller and Odyssey is its processor/service provider, acting on its instructions. Contact: wardeye@odysseydevelopments.dev.
2. What we collect
| Category | Examples | Why |
|---|---|---|
| Account | Work email, name, sign-in identifiers (including Microsoft account ID if you use Sign in with Microsoft), organisation name, roles, invitations | Create and secure accounts; run organisations |
| Confirmation requests | Who asked whom, the reason text typed by the requester, template type, timestamps, outcome (approved, denied, expired) | Deliver the “Is this you?” check and keep an audit trail |
| Devices | Device name, platform, push-notification token, device public key | Deliver confirmations to the right phone; verify devices |
| Email protection (optional) | If an individual connects their Microsoft 365 mailbox: read-only access to recent message headers; we store sender, subject, received time, a risk score and reasons for flagged messages. We do not store message bodies. An encrypted refresh token is stored to keep the connection alive. | Flag possible impersonation or business-email-compromise |
| Consent records | Which consent version a person accepted and when; withdrawal | Prove consent and honour withdrawal |
| Billing | Plan, seat counts, Stripe customer and subscription IDs, invoices. Card details go to Stripe, not us. | Charge and support subscriptions |
| Sealed enrolment media | Encrypted files a person uploads to enrol (see Biometric Notice). We cannot read them; the intended Mac decrypts and then deletes them. | Let a person enrol remotely without exposing raw media |
| Technical | IP address and request logs from our hosting and database providers, error information | Security, abuse prevention, reliability |
| Website | Standard server logs. The home page asks GitHub for the latest release number, which discloses your IP address to GitHub. | Show the current version |
On your Mac. The Mac app notices that a call is happening by checking whether a microphone or camera is in use. It does not record or upload call audio or video. Where live verification is enabled, matching runs on the Mac, and call events are kept in memory. If Listen is enabled for an organisation, transcription of the other side of a call happens on the device. Voice and face templates are stored locally and are not uploaded to our cloud.
3. How we use personal data and legal bases
- To provide the Service you asked for (contract).
- To secure the Service and prevent abuse and fraud (legitimate interests).
- To bill and meet tax and accounting obligations (contract, legal obligation).
- To respond to you and give support (contract, legitimate interests).
- To process biometric data, only with the explicit, separate consent described in the Biometric Notice.
We do not use Customer Data for advertising, do not sell or “share” personal data for cross-context behavioural advertising, and do not use it to train shared machine-learning models without a separate written opt-in. We do not make decisions with legal or similarly significant effects solely by automated means; Wardeye produces a risk signal that a person acts on.
4. Who we share it with
Only service providers that help us run Wardeye, under contract and only as needed, listed on our Subprocessors page: hosting and database (Supabase, Vercel), payments (Stripe), push notifications (Apple, and Google if Android is enabled), email-code delivery, sign-in (Microsoft, if you choose it), mailbox access (Microsoft Graph, if you connect one) and release hosting (GitHub). We may disclose data where required by law or to protect rights and safety, and in a merger or sale (with notice). We do not sell personal data.
5. International transfers
We are based in the United States and our providers may process data in the US and other countries. Where required, transfers rely on the providers’ standard contractual clauses or equivalent safeguards.
6. How long we keep it
- Account and organisation data: while the account is active, then deleted within 90 days of closure, unless law requires longer.
- Confirmation requests and audit trail: for the life of the organisation’s account, or shorter if the organisation configures it, then deleted with the account.
- Email flags: deleted when the mailbox is disconnected or the account is closed. Disconnecting removes the stored token.
- Sealed enrolment files: deleted after the Mac processes them; unprocessed uploads are removed when the enrolment is cancelled or the account is closed.
- Biometric templates: see the Biometric Notice.
- Billing records: as required for tax and accounting (generally 7 years).
- Server and security logs: up to 90 days.
7. Your rights
Depending on where you live (including the EEA/UK, California and other US states, and Canada) you may have the right to access, correct, delete, restrict or object to processing of your personal data, to receive a portable copy, to withdraw consent at any time, and to complain to your regulator. We do not discriminate against people who exercise their rights. To exercise a right, email wardeye@odysseydevelopments.dev. If your data is held for an organisation (for example your employer), we will direct the request to that organisation, which decides, and we will help it respond. We will reply within 30 days (45 days where the law allows). We may need to verify your identity.
8. Security
We use encryption in transit, row-level access controls, encrypted mailbox tokens and device-bound keys for sealed enrolment. See Security. No system is perfectly secure; if a breach affects your personal data we will notify you and regulators as the law requires.
9. Children
Wardeye is for businesses and is not directed to anyone under 18. We do not knowingly collect data from children. If you believe we have, contact us and we will delete it.
10. Cookies and local storage
We use only essential storage. See Cookies. We do not use advertising or analytics cookies and do not respond to “Do Not Track” signals because we do not track you across sites. We honour Global Privacy Control signals as an opt-out of sale/sharing, although we do not sell or share personal data.
11. Changes
We will post updates here and, for material changes, notify account holders. The date above shows the latest revision.
12. Contact
Questions, requests or complaints: wardeye@odysseydevelopments.dev. EEA/UK residents: we have not yet appointed an EU/UK representative; until we do, please use this address.