Briohush
Privacy
This page describes information handled by Briohush’s current member, guest, wellness, and optional visitor-analytics features.
Accounts and sign-in
When you create a member account, Briohush stores the name and email address you provide. Email and password sign-in is handled by Better Auth; the password credential is stored as a hash, not as the password you entered. Sign-up attempts to send an email-verification message, but the current flow creates a session without waiting for verification.
Briohush stores sign-in session records with an expiry. A session record may also include the IP address and browser user-agent received with a request.
Wellness information for members
Your member preferences can include selected wellness categories—movement, rest, or mindfulness—and preferred check-in weekdays. For each saved weekly goal, Briohush stores its text (up to 160 characters), optional category, target number of days, private goal notes (up to 2,000 characters), preferred check-in weekdays, an optional reminder weekday, and pause history. A selected reminder weekday can show an in-app prompt while that day’s check-in is open.
Goal check-in history includes its date, whether you marked it complete, and a completion time when applicable. You may also save an optional private reflection of up to 2,000 characters with an individual check-in; it appears with that date in your recent history. The app also stores goal pause periods. Separately, when a member dismisses a weekly achievement message, Briohush stores a dismissal marker for that member and the week it applies to.
Using Briohush as a guest
Without signing in, you can save a separate guest goal with its text, optional category, target number of days, preferred check-in weekdays, and dated daily check-ins with completion status and time when applicable. Guest records do not contain a member account ID, name, or email. The database key is a SHA-256 digest of a random token held in the briohush_guest cookie; guest goals do not store member notes, reminder choices, or pause history.
The cookie is HttpOnly and SameSite=Lax, is marked Secure in production, and is set to expire after one year. Cookie expiry or clearing the cookie stops that browser from presenting the token, but does not itself delete the guest database record. Briohush does not define automatic cleanup or a retention period for those records.
If you successfully claim a guest goal after signing in and your account has no active weekly goal, Briohush copies the goal, target, preferred weekdays, and daily check-ins to your member account, then deletes the guest record and clears the cookie. If your account already has an active goal, it is not replaced and the guest record is not removed by that claim.
Optional visitor analytics
Visitor analytics runs only when the deployment provides an analytics app slug. On a page load, Briohush reuses or creates a random visitor ID named polsia_vid in browser local storage and requests a page-view pixel from the configured Polsia API base with the app slug and visitor ID.
Briohush does not set an expiry or provide an in-app deletion control for this browser ID. Account deletion does not clear polsia_vid from this browser or request deletion of analytics beacon data. The app does not specify how long Polsia’s analytics platform keeps beacon data or how that platform handles deletion.
Account deletion and retention
Account deletion currently requires an authenticated member whose account passes Briohush’s active-subscription access check. If the request is signed out or does not pass that check, the deletion endpoint does not delete the account. After a successful request, Briohush deletes the member account, its linked sign-in account and session records, the member preferences record, and the member’s weekly goals. Each goal’s check-in and pause records are removed through the database cascade.
The deletion endpoint does not remove the separate weekly achievement-dismissal markers described above, and it does not look up or delete anonymous tracker records. A guest goal that was successfully claimed has already been removed from the guest records; an unclaimed guest goal and its check-ins are outside the account-deletion request.
Account deletion does not clear the browser’s visitor analytics ID or request deletion of analytics beacon data. The app does not establish whether deleted records remain in backups or how the analytics platform handles retention or erasure. It also defines no retention period or automatic cleanup schedule for member-account, preference, or wellness records. Session rows have an expiry timestamp, but cleanup of expired sessions is not specified.
If you have access to your member account, open Settings to delete your account. For questions about this page, email hush-3@polsia.app.