pepdoserAccount information stored on the server
The account service stores your name, email address, a salted password hash, account role and status, signup date, last account activity, whether the account returned after its first day, secure session records, and password-reset security records. It also records account-signup events and clicks on the optional third-party resource. pepdoser does not receive order details from the external provider through this click event.
The administrator can view names, emails, signup dates, last account activity, return-after-day-one status, and aggregate resource-click counts. For account support, an administrator can manually mark an account's email as verified after confirming ownership; that action records the administrator ID, target account ID, action, and time in an audit log. The administrator cannot use the admin dashboard to view medication plans, desired doses, schedules, dose logs, label instructions, personal notes, reminders, or inventory details.
Tracker records stored for account sync
Plans, dose logs, label instructions, notes, inventory, reminders, settings, onboarding confirmation, and consent choices are sent over HTTPS under your authenticated account. They are encrypted by the application before database storage using an authenticated encryption key held by the server environment. The database stores ciphertext rather than readable tracker JSON. Optional image storage is not enabled in this MVP.
This is server-side application encryption, not end-to-end encryption. The service must decrypt records to return them to an authenticated account. The admin dashboard does not expose these records, but authorized service infrastructure and code can technically process them.
Typography request
The current visual demo requests Bricolage Grotesque and Inter font files from Google Fonts. That provider may receive ordinary connection information such as an IP address, browser details, and referrer, but tracker record values are not included in the font request. Self-host approved font files before a privacy-sensitive production launch.
Device cache and exports
Each signed-in browser caches a readable copy in localStorage. Anyone with access to that browser profile, device, developer tools, backups, or an exported JSON file may be able to view it. Use an appropriately secured device and profile, and log out on shared devices.
Sync and data-loss limits
Network outages can delay sync. The app shows when records are synced or waiting on a connection; do not switch devices until the latest device reports a completed sync. Clearing browser data removes the device cache but normally does not remove the account copy. An export contains sensitive plain-text information, so protect it accordingly.
Your controls
- Export all tracker collections to a JSON file.
- Import a validated backup by merging or replacing current data.
- Delete individual records.
- Delete synced tracker data and the current device cache with an explicit confirmation.
- Change public-page consent choices from the footer.
Authentication cookie and security data
Signing in sets an essential, Secure, HttpOnly, SameSite=Strict session cookie. The server stores only a cryptographic hash of the session token. Failed login protection may temporarily store an opaque keyed value derived from network and account information; it is used only to limit repeated login attempts.
Account deletion and password recovery
An administrator can create a short-lived, one-time password-reset link after verifying the account owner, or permanently delete a server account. Account deletion also deletes that account's encrypted tracker record through a database foreign-key cascade and revokes server sessions and reset records. Historical signup or resource-click events may remain only after their account identifier is removed so all-time aggregate counts can remain accurate. The administrator dashboard does not display tracker contents.
No HIPAA claim
This MVP does not claim HIPAA compliance and has not been presented as a covered-entity system. Obtain appropriate privacy, security, and legal review before deploying it for others.