Privacy Policy
This page explains, in plain language, what Epilog does and does not do with your information. The short version is simple: your private records stay on your own device in your browser and, if you turn on backup, in your own Google Drive. They are not stored in a medical database run by the people who make Epilog.
Last updated: 6 May 2026
1. What Epilog is
Epilog is a seizure diary and care coordination app for people managing epilepsy and other chronic conditions. It includes event tracking, medication history, appointment records, contact directories, financial tracking, downloadable reports, and optional Google Drive backup.
The public parts of the site also include EpiBlog and EpiMart. Those public pages do not expose a user's private diary records.
2. Plain-language summary
The people who make Epilog do not have a server, dashboard, or admin screen where they can open your seizure diary, notes, profile, uploads, appointments, contacts, or financial entries.
Your private records stay on your own device in your browser and, if you choose backup, in your own Google Drive. That means your private records are not kept in an Epilog-owned medical database.
The main account information handled centrally is the sign-in information needed to let you log in with Google and identify your session.
3. What the Epilog team can and cannot access
Epilog is designed so the site operator does not centrally receive or store your private medical diary data. That includes seizure records, medication history, appointments, care contacts, personal notes, uploaded photos, uploaded videos, uploaded documents, and financial tracking that you enter into the app.
Through the normal operation of the app, there is no Epilog-owned medical database where the team can sit and browse your private diary.
This does not mean no technology risk exists anywhere. It means Epilog is built so your private records are not intentionally stored in a place run by the site operator.
4. Where your private records are stored
By default, Epilog stores your working records in your own browser on the device you are using. That includes events, medications, appointments, contacts, profile details, and financial entries.
If you turn on backup, Epilog writes structured record files into your own Google Drive under Epilog/Data. Drive-backed uploads such as images, videos, and documents are written into your own Google Drive under Epilog/Media.
If you choose to link a file from another cloud storage service, such as Dropbox, OneDrive, iCloud Drive, Box, Proton Drive, or another file host, Epilog stores the link you give it. Epilog does not become the host of that file.
5. Google sign-in and Google Drive access
Epilog uses Google sign-in only. There is no Epilog-managed password system.
When you sign in, Google and Firebase Authentication handle the login process. The main account information involved in that process is your Google account identity information, such as your email address and display name.
If you enable Drive backup, Epilog asks Google for the access needed to create and update Epilog files in your own Google Drive. The Drive scope used is drive.file, which is intended to let Epilog work with files it creates for you rather than browsing your whole Drive.
Google sign-in and Google Drive are governed by Google's own systems, policies, and security controls.
6. Other third-party services you may use
Epilog uses ArcGIS address suggestions in selected forms. When that feature is on, the address text you type is sent to ArcGIS so it can return suggestions. Epilog lets you turn suggestions off and keep typing locally.
If you paste a link from another cloud storage provider or video host, that provider handles the file at the other end of the link. Epilog only stores the reference you give it so it can appear in your record.
7. Public site services
SeizureDiary.com also has public pages such as EpiBlog and EpiMart. Those public sections use Firebase and Firestore for sign-in/admin access and public content management.
That public-content system is separate from your private diary records. It is not the place where your seizure diary, uploads, profile, or notes are stored.
8. What information is involved when you use Epilog
Depending on which features you use, Epilog may work with:
- Google account details needed for sign-in, such as your email address and display name
- profile details you choose to enter, such as name, date of birth, diagnosis date, and address
- health-related records such as seizure entries, medication changes, appointments, contacts, and notes
- media you choose to upload or link, such as photos, videos, and documents
- financial information you choose to enter, such as fees, medication costs, travel costs, and reimbursements
- technical data needed for the app to work, such as local browser storage data and sync metadata
9. What Epilog does not do with your private records
Epilog is not designed to sell your private diary data, package it for research partners, or keep it in a central Epilog-run medical database.
The people who make the app do not use the normal operation of Epilog to read through your seizure records, notes, uploads, or profile entries on an Epilog-owned server, because those private records are not stored there in the first place.
10. Retention, export, and deletion
Local browser data remains on your device until you delete it, clear browser storage, or replace it with an imported or exported copy.
Google Drive backup files remain in your own Drive until you delete them from Drive or remove the relevant folders and files.
Epilog includes export and import tools so you can keep your own copy of your records and move them between devices.
11. Security and your responsibility
Epilog reduces privacy risk by avoiding a central server-side medical datastore for private records. However, the security of your private records also depends on the security of your own device, browser, Google account, and any cloud storage service you choose to use.
- protect your device and browser account
- protect your Google account if you use Google sign-in or Drive backup
- protect any other cloud storage account you choose to link to
- keep your own backup or export copies if the information is important to you
12. Overseas services
Depending on the features you use, data may be processed through services operated outside Australia. This may include Google, Firebase, Vercel, and Esri/ArcGIS.
If you enable Google Drive backup, those backup files are stored in your own Google account subject to Google's own infrastructure and settings.
13. Access, correction, and complaints
Because Epilog is designed around user-controlled storage, you can usually access, correct, export, or delete your own records directly inside the app or within your own Google Drive.
If you have a privacy question, correction request about public account information, or a privacy complaint, you can contact the site operator at skughole@gmail.com.
14. Changes to this policy
This policy may be updated as Epilog evolves. The latest version will be published on SeizureDiary.com with the updated date shown at the top of the page.