What this application does
EverydayMe stores account details, prescribed treatment records, injections and locations, purchases, personal pharmacy quotes, weight, symptoms, check-ins, optional health trackers, photographs, voice notes, saved recaps and preferences you choose to enter. These are self-reported records, not a medical assessment. Health fields are optional; a feature may need particular details to work. Observations describe recorded information and missing entries remain unknown. The app does not diagnose, explain causes or recommend treatment changes.
Your information
Records belong to your signed-in account. The application checks account ownership on diary pages, downloads and API requests. Trusted hosting operators and superusers can access the database and private files for administration. This application has its own database, separate from the existing sleep diary and any school or safeguarding systems.
There are no advertising SDKs, remote fonts or external analytics. External AI is disabled by default and requires the separate choices described below. Opening medicine, pharmacy or other source links takes you to an external website; personal quote links are not fetched by EverydayMe. Imports require source-specific permission. If an operator configures the optional USDA food catalogue, you must choose to send food search words to USDA for each search. Account details and diary entries are not sent to USDA. Selected food data is copied into your private library with its source.
Storage and downloads
The development database and private photo/audio files are on this computer. They are not encrypted by this application. Use an encrypted device and restrict local access. Hosted deployments require HTTPS, encrypted storage and backups, secrets management and tested restore procedures. PDF reports are generated locally on the server without sending records to a report provider, and are delivered without saving a report file on the server. Downloaded PDFs, JSON, CSV, photographs and audio are unencrypted files: store and share them carefully.
The generic offline shell does not cache diary pages or API responses. If you prepare an offline notebook, its account binding, treatment snapshot and unsynced health entries are encrypted with AES-GCM using a key derived from your separate passphrase. The key and passphrase are not stored. The notebook locks when hidden or idle. The application cannot recover a forgotten passphrase; clearing browser data erases unsynced entries. Signing out locks open notebooks; encrypted local entries remain until you erase the notebook. Delete notebooks on devices you stop using. Account deletion blocks their uploads but cannot remotely erase an offline device.
Private voice notes
Microphone access starts only when you choose Start recording and allow the browser permission. Recordings stay in the page until you explicitly save the private note. Recording stops when you hide or leave the page, or reach two minutes. You can listen before saving, upload a compatible PCM WAV or use a typed transcript without microphone access.
Optional live transcription starts only when the browser reports that on-device recognition and its installed language model are available. Support varies. There is no remote speech-recognition fallback and no automatic language-model download. Audio and transcripts are never sent to the optional AI summary service. Saved audio is re-encoded to remove file metadata, kept outside public directories and served only through your signed-in account.
A limited local text parser suggests diary entries from your reviewed transcript. It can misunderstand words, quantities and timing. Nothing enters your diary until you select the suggestions, review the values and confirm. Injection mentions remain in the transcript and require the usual injection form. Deleting a voice note removes its transcript and active audio file after the database action commits; previously confirmed diary entries stay.
Optional AI-selected highlights
Local observations and recaps work without an external service. Optional AI highlights additionally require operator enablement, an active Plus pilot and your consent for each request. The page displays exactly the aggregate statements that would be sent to OpenAI. These can still reveal health information. Do not consent unless you want that processing.
The request excludes account identifiers, source rows, dates, medication doses, free-text notes, custom measurement labels, photographs, audio and transcripts. OpenAI may select up to three supplied observation IDs; EverydayMe displays only the existing calculated statements, with their methods and limits. Generated clinical prose is not accepted. Requests are limited and failures keep the local recap available.
The server requests store=false. This does not guarantee zero provider retention; provider abuse-monitoring and account-specific retention terms may still apply. The operator must review the provider's data controls and publish the applicable processing terms before enabling it. Request consent and an audit event are stored, including for failed attempts.
Native Health Connect
The optional Android companion reads only selected weight, steps and sleep types from one selected source app through Health Connect. It never writes to Health Connect. The first scan reads the available last 29 days. Subsequent syncs mirror source updates and deletions while a valid change cursor exists. Weight can appear in the main diary; steps and sleep stay in a separate source view to avoid adding overlaps with manual entries. Records are sent only to the EverydayMe server you pair. Credentials and pending uploads are encrypted with Android Keystore and excluded from backup. Credentials expire after 90 days and can be revoked. If a change cursor expires, imports stop for review. The browser cannot read Health Connect; Apple Health needs a future native iOS adapter.
Your choices
You can change reading size, contrast, reduced motion, tracker and weight-visibility preferences; export selected records; revoke import permission; or permanently delete your account from Settings. Financial sections are opt-in in reports. The Android companion can show generic reminders without medicine, dose, weight or symptom details. Notification and Health Connect permissions are separate. Paired devices can be revoked in Mobile & offline.
Progress photographs are optional and private. Downloads require sign-in. Image metadata is removed and photos are re-encoded as JPEG without changing body shape. Deleting a photo or account removes associated active files after the database action commits.
Free accounts retain core diary features, local observations, voice notes and exports. Plus pilot access adds saved report presets and eligibility for optional AI highlights. Access is granted by an operator, can expire, and never changes existing health records or export rights. Pilot requests are stored for the operator; no payment, billing or automatic subscription is created.
Retention and commercial release
Records stay until you delete them or your account. Demo accounts can be removed by the demo-cleanup command. Backups need a separately defined deletion schedule; deleting active records cannot erase copies you have downloaded. A commercial operator must identify the controller and contact details, establish purposes, recipients and applicable Article 6 and Article 9 conditions, complete a DPIA, define retention and backup schedules, support rights requests and publish a production privacy notice before accepting real customers. This development notice does not establish production compliance.
Medicine information
The initial UK Mounjaro configuration records the reviewed leaflet version and links its sources. Follow the leaflet supplied with your own device and speak to your prescriber or pharmacist for treatment decisions. The application does not prescribe, choose a dose, make missed-dose decisions or provide device modification instructions.
Injection maps show illustrative tracking regions and are not anatomical measurements. The app cannot verify that a point on your own body is an appropriate injection site.
For urgent concerns use the official safety information for your medicine. In the UK, call 999 for difficulty breathing or swelling of the tongue or throat; contact NHS 111 urgently for suspected serious side effects. Outside the UK, use your local services.
NHS tirzepatide information ↗ · MHRA Yellow Card reporting ↗