Privacy Policy
This page explains, in plain language, what Epilog does and does not do with your information. The short version is simple: Epilog is private to approved family emails for now. Your working records stay in your browser and sync to a private Firebase server copy for reliability.
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 private server sync.
2. Plain-language summary
Epilog is no longer open public signup. The private diary is restricted to approved family email accounts.
Your private records stay in your browser as the working copy and sync to private Firebase records under the signed-in account.
The main account information handled centrally is the email/password sign-in information needed to identify your private family account.
3. What the Epilog team can and cannot access
Epilog now keeps a private server copy of diary data for the restricted family deployment. That includes seizure records, medication history, appointments, care contacts, personal notes, documents, and financial tracking that you enter into the app.
Access should be controlled through Firebase Authentication, the approved email allowlist, and Firestore security rules that limit records to the signed-in account.
This does not mean no technology risk exists anywhere. It means Epilog is built so your private records are not open to public users or used for public research collection.
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.
After sign-in, Epilog syncs structured records to private Firebase/Firestore documents under your account. Older Google Drive media links may still be displayed, but Google Drive is no longer the normal live backup path.
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. Private sign-in and server sync
Epilog uses private Firebase email/password sign-in for approved family accounts.
When you sign in, Firebase Authentication handles the login process. The main account information involved is your approved email address and account display name.
The private server sync stores the app's existing JSON data stores under the signed-in Firebase user. Google Drive reconnect prompts are no longer part of normal use.
Firebase is governed by Google's 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. 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
8. 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 open it to public users.
The private server copy exists to support Dusty's family workflow, not to create a public medical data product.
9. 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.
Private server records remain until they are deleted through the app or removed from the backing Firebase project.
Epilog includes export and import tools so you can keep your own copy of your records and move them between devices.
10. Security and your responsibility
Epilog reduces privacy risk by keeping access private and allowlisted. The security of your private records also depends on the security of your own device, browser, password, and any cloud storage service you choose to use.
- protect your device and browser account
- protect your Epilog email/password account
- 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
11. 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.
Private server records are stored through Firebase/Google Cloud infrastructure. Linked external files remain governed by the provider that hosts them.
12. Access, correction, and complaints
You can usually access, correct, export, or delete your own records directly inside the app.
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.
13. 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.