Sensitive data protection

Security at ResetHive

ResetHive is built for recovery work that can be personal, sensitive, or hard to talk about. This page explains how private tools, community identity, encryption, notifications, exports, and account deletion are handled inside the product.

End-to-end encryption

No one, including ResetHive, can read your encrypted journals or craving logs without your privacy password or access to an unlocked trusted device.

Public activity uses a different identity

Community activity is stored encrypted and tied to a separate public identity.

Discreet notifications

Hive reply alerts use generic previews without post content.

Export or delete your data

You can download your data or delete your account from the account page.

What is protected

Private recovery tracking

Your device encrypts private recovery data before saving it. ResetHive cannot decrypt that history. Your privacy password unlocks it on your devices.

Recovery history

Counter dates and periods, reflections, mood, setbacks, and the full craving log, including notes, timing, intensity, triggers and outcomes, use end-to-end encryption.

Reading and preferences

Article reading history, favorites, private topic preferences, country and appearance preferences are also encrypted end to end, along with any previously saved gender information.

Your privacy password

Create a strong privacy password. Sign in by email and enter it on a new device. ResetHive cannot see it, email it to you, or recover it. You can change it from an unlocked trusted device without re-encrypting your history.

Used for sign-in and account support. Public community activity uses a separate identity.

Exports and deletion

Export decrypts your history on your device into a readable file. Keep that file private. You can erase private history or delete your account without recovering lost encryption keys. Active data is removed; historical provider backups may remain until their retention expires.

What can be seen

What other people can see

ResetHive is private by default, but it is not a secrecy tool. These are the main visibility boundaries to know before you post or ask for support.

In the Hive

Your display name, posts, replies, reactions, and anything else you choose to share in that space.

To the ResetHive team

We retain operational data such as account details, recovery memberships, language, time zone, notifications, broad feature-use counts and service logs. Encrypted record sizes and sync times are also visible. We do not read or use the contents of your private recovery history.

To service providers

ResetHive runs on established providers such as Supabase, Render, Resend, OpenAI, Google/Firebase, and Apple. Where sensitive data is processed by providers, we choose services with mature security and compliance programs.

Limits

What this does not promise

If you forget your privacy password and lose access to all trusted devices, your private data cannot be recovered. Email sign-in alone cannot unlock your history on a device without remembered access. You can erase private history and start again or delete the account.
Hive posts, replies, article reactions and a recovery counter you choose to share are deliberate shared content. They remain accessible to the service and are not part of private end-to-end encryption.
Hive posts are public inside the Hive. Use a display name, but avoid sharing details that could identify you if you do not want them connected to you.
Your email provider, device, browser, operating system, app store, and network can still create their own records outside ResetHive.
No app can promise perfect anonymity or perfect security. ResetHive focuses on reducing exposure, protecting private recovery data, and making privacy boundaries clear.

Control

You can export your data or delete your account.

You can export or delete your data from the account page. Deleted account data is removed from active records.