Privacy policy

1. Who is responsible and how to contact us

Seizurely is operated by Kyle Davies, United Kingdom, who is the data controller responsible for this service and responding to privacy requests. Contact [email protected] about access, correction, deletion, withdrawal of consent or any privacy concern. Do not send passwords, authenticator setup keys or recovery codes in your enquiry.

2. Information we collect

• Account details: your name, email address, account identifier, sign-in method, registration date, email-verification and administrator-approval status.
• Google sign-in information: your Google account identifier, email address, whether Google has verified that email, and your name. Google's identity token may also contain a profile picture URL or other basic profile claims; Seizurely does not store or use your Google profile picture. The token is processed to validate your identity, and the Google account identifier is stored as a keyed lookup value.
• Health-journal information you choose to enter: seizures and other symptoms, dates, times, duration, potential triggers, headache start/end times, activity, location descriptions, notes, medication names, doses, treatment periods and adherence information.
• Optional profile information: date of birth, a location you enter, hospital and care-team names and contact details. Location is entered manually; the app does not request GPS access. Only enter other people's contact details when you are entitled to do so.
• Security and preferences: a salted password hash for email/password accounts, encrypted authenticator information, hashed recovery codes, temporary activation and sign-in challenges, failed-attempt/lockout records, consent version and time, and theme preferences. We do not store your password as readable text.
• Technical information: session cookies, network addresses used for request limiting, and operational/error and mail-handoff logs. Our hosting and email providers may also process connection, delivery and security logs when providing the service.

Information is supplied by you, received from Google when you select Google sign-in, or generated while operating and protecting your account. Uploaded journal backups are processed only when you choose to import them.

3. How we use your information

We use account and Google sign-in information to identify you, create or connect your account, verify access and display your name. We use your journal and profile information to save your records, show summaries and patterns, and produce reports you request. Security information protects accounts, applies MFA and lockouts, prevents misuse and supports account administration. Your email address is used for activation, approval/welcome messages and responses to your requests.

Before accessing the journal, you are asked to explicitly agree to the storage and processing of your health information. The app records the notice version and acceptance time. You can decline and sign out or delete your account. Creating an account necessarily stores basic registration information before that first-login consent step.

Seizurely does not use journal data for advertising, sell personal information, create advertising profiles or use your information to train general-purpose AI models. The current app does not include advertising or third-party analytics trackers.

Legal grounds for processing

We process basic account information to provide the service you request. Health-journal processing is based on your explicit consent. We rely on legitimate interests in protecting accounts and maintaining a secure, reliable service for necessary security and operational processing, taking your rights into account. We may also process information to meet applicable legal obligations. Optional health and care-team details are not required merely to register an account.

4. Google user data and permissions

Sign in with Google is used for identity and account access. Seizurely does not request access to your Gmail messages, Google contacts, Calendar, Drive documents or Google password. It does not request ongoing Google access or refresh tokens for those services. Journal contents are not sent to Google as part of the sign-in integration.

Seizurely's use and transfer of information received from Google APIs will adhere to the Google API Services User Data Policy, including the Limited Use requirements. Google information is used only for the account and sign-in purposes explained here, not for advertising or unrelated profiling.

You can manage the Google connection in your Google Account connections settings. Removing that connection does not itself delete your Seizurely account or journal; use account deletion or contact us for that.

5. Who can access information and when it is shared

Other members do not have access to your journal or account credentials. The app associates records with your authenticated account and restricts access accordingly. The administrator can view registration/account details, approve accounts, delete account data and reset local passwords. The administrator cannot retrieve an existing password. Hosting operators and authorised maintenance personnel may have technical access required to operate or support the service; the app does not provide end-to-end encryption that prevents all operator access.

GoDaddy provides the hosting/database environment. The configured mail-delivery service processes recipient addresses and account-notification content. Google processes sign-in interactions under its own privacy policy. These providers receive information necessary for their functions. Activation and welcome emails do not include your seizure journal.

Reports are not automatically sent to your nurse or health team. If you export, print, download or share a report, you control who receives that copy. We may disclose information when legally required or necessary to investigate misuse or protect the service, subject to applicable law.

6. Storage and security

Account profiles and journal records are encrypted before database storage. Passwords are individually salted and hashed, sign-in requires MFA, and server-side access checks separate user records. Activation links and recovery codes are limited-use; repeated failed sign-ins trigger temporary lockouts. Sensitive API responses are marked not to be cached, and the service worker caches app assets rather than journal API responses.

No internet service can guarantee absolute security. Keep your password and recovery codes private, sign out on shared devices and protect reports you download. The application is hosted in Europe through GoDaddy’s Europe hosting plan. Google sign-in, email delivery and provider support may involve processing outside Europe under the relevant provider arrangements. Contact us for information about providers and any applicable international-transfer safeguards.

7. Retention and deletion

Account and journal information is generally retained while your account exists, unless you or the administrator delete it earlier. This includes registrations still awaiting activation or approval; they are not automatically erased merely because registration is incomplete. Temporary activation links expire after 24 hours, MFA challenges after 10 minutes, and ordinary sessions after 14 days. Expired credentials no longer grant access; some security metadata remains with the account.

In Settings, choose Delete my account and data and confirm your email. Deletion removes your account, Google-account association, consent record, profile, journal, medications, security state and sessions from the live application database. You can also contact us if you cannot sign in. We may need to verify ownership before acting. Administrators can delete journal data while retaining an account.

Account deletion withdraws your consent to continued health-journal processing in the live service. It does not remove files you exported or shared, emails already delivered or copies held independently by recipients. Backups are created once a month and retained for an additional month before expiry. The in-app deletion button does not immediately rewrite existing backups. Deleted account information may remain in a restricted backup until that backup expires; it will not be used for ordinary service operation. If a backup is restored, deletion requests must be reapplied before the restored data is returned to use. Operational and mail-delivery logs are separate from the live account database; contact us about their retention and inclusion in a deletion request.

8. Cookies and browser storage

If you enable offline access, this browser stores an encrypted copy of your profile and journal plus new records waiting to upload. A separate offline passphrase unlocks this copy; we do not store that passphrase on the server. Password hashes, authentication tokens and MFA secrets are not part of this offline copy. Sync requires a valid session for the same account. When connected, the app prompts you to enter your offline passphrase before uploading pending records; choosing Later keeps them on this device. Minimal record identifiers are retained with your account to prevent duplicate uploads, including after an individual record is deleted.

Signing out locks the offline copy but retains it, including pending records. Use Settings to remove it from this browser. Account deletion through this browser also removes its offline copy. Copies on other devices cannot be remotely erased while those devices are offline; remove them on each device or clear its site storage. A deleted account cannot upload queued records. Clearing storage or losing the offline passphrase can permanently lose unsynced records. Use offline access only on a device you trust.

Essential cookies maintain your sign-in session and temporary MFA challenge. Browser storage/service-worker caches support app loading and installation. If older journal data exists in your browser, the app can offer an import; account deletion does not automatically remove independently stored legacy files or exports. Google sign-in may use browser storage and cookies governed by Google's policies. Blocking essential cookies can prevent sign-in.

9. Your choices and rights

You can edit your profile and journal, export a report and delete your account. Depending on the law applicable to you, you may also have rights to access, correct, erase, restrict processing, object, receive a portable copy of information or withdraw consent. Contact the address above to request help. Withdrawal does not affect processing already carried out before withdrawal. Requests are assessed under applicable law, and identity checks may be needed to protect your information.

If UK data-protection law applies, you can raise concerns with the Information Commissioner's Office. You may also contact the relevant data-protection authority where you live.

10. Children and information about others

Health information about children or another person requires particular care. Do not enter another person's records unless you have appropriate authority to do so. Contact the administrator before using the service for a child or submitting records on someone else's behalf so suitability and permission can be addressed.

11. Changes to this policy

We will update this page and its date when our practices change. If we materially change consent-based health-data use, we will provide an updated notice and seek renewed consent where required. You can contact us to ask about a previous version.

Monthly check-ins, connected health and optional AI

Monthly scores and comments are encrypted and retained until you remove the individual check-in or delete your account/data. Removing a check-in clears its score and text; only its month and timestamps remain so the monthly prompt stays completed. Connecting WHOOP authorises Seizurely to import sleep, recovery and cycle summaries. Access and refresh tokens are stored encrypted. Disconnecting removes those tokens and imported readings from Seizurely; you can also revoke access in WHOOP.

The optional assistant sends your question, up to six recent chat messages, up to 90 days of symptom and health summaries, relevant medication periods and recent monthly comments to OpenAI only with your explicit consent. Account names, email addresses, care-team details and general journal notes are excluded, but text you enter may itself identify you. Seizurely does not store AI answers and requests that OpenAI not store responses for retrieval. Other provider retention, including abuse-monitoring logs, may still apply. See OpenAI API data controls. The assistant does not diagnose or recommend treatment changes.