Privacy Policy
Hazel 1.1 puts a member community beside the welcome you prepare. Your profile, messages, and purchases now reach Hazel's systems; the letters you write for your group stay on your phone. This policy keeps those two apart.
The short version
The community side of Hazel needs an account, so your profile, messages, photos, reports, blocks, membership state, and postage balance are held on our systems. The Welcome side has not moved: group material, private sources, reviewer keys, and finished letters remain on your device. We do not sell personal information, we run no advertising, and we do not follow you across other companies' apps. Apple takes the payment; what reaches us is a record that a purchase happened.
1. Scope
This policy covers the Hazel application for iPhone, the member community it connects to — profiles, discovery, chats, notifications, reports, and the House store — the Welcome authoring tools, and these legal pages. "Hazel," "we," "us," and "our" mean the Hazel product and its operator. "You" means the person using it.
Hazel is distributed through Apple's App Store. Apple's handling of App Store transactions, device services, iCloud, and Apple IDs follows Apple's own privacy policies; this policy does not describe Apple's independent processing.
Hazel is offered to people in the United States. If you live elsewhere, please do not use the app; access from another country is your own decision, and your information is handled as described here and under the law that applies to you.
Versions up to 1.0 worked entirely on the device. Version 1.1 replaces that with a signed-in community, and this policy describes what is sent to Hazel's systems and what is not. A future feature that adds a new kind of recipient will be disclosed before it is used, not after.
2. Information Hazel handles
What we hold depends on which half of the app you use. Community features need information in order to reach other people; the Welcome tools do not, and their material is not uploaded.
2.1 Account and sign-in
Sign in with Apple is the way in. Apple returns an opaque user identifier and an account state and, depending on what you authorize, your name and email address. We store those with the date you joined and whether the account is active.
During sign-in you confirm that you are 18 or older. We record that the declaration was made and when. It is a statement by you, not a check of any document.
A session credential is issued to the app so you stay signed in. Signing out ends that session on the device and releases the push token described below.
2.2 Profile and photos
Your profile carries the name you enter, your age, gender, the ZIP code or region you give, an optional description, and any photo you upload. Members you have not blocked can see it, so put in only what you are willing to show them.
Photos chosen for your profile or for a chat are uploaded and kept so they can be displayed and delivered. Hazel does not read your photo library; the system picker hands over the images you select.
2.3 Messages
Chats contain the text, images, GIFs, participants, timestamps, and delivery and read states of each conversation. Messages are stored on our systems so they can be delivered, kept in order, and shown again when you reopen the app or sign back into the same account. They travel over encrypted connections.
A chat opens only after a first letter has been accepted, and that state is recorded against the pair of accounts. The number of messages you send is counted so the free allowance and the postage charge can be applied.
2.4 Discovery, ZIP, and distance
Addresses places you roughly using the ZIP code or region in your profile. It shows an approximate distance rather than a pin on a map. If you grant location access, the app uses it while the screen is open to refine that distance; it does not collect location in the background.
The filters you set — age, gender, distance — and the profiles you open are recorded so the list can be built, ordered, and paginated.
2.5 Welcome content kept on your device
Group names, newcomer names, optional role and interest context, source credits, private source text, selected excerpts, authored lore, audiences, reviewer names, review decisions, correction summaries, publication dates, reading periods, and Welcome Editions are stored in the app's local cabinet. This material is not uploaded to Hazel. It may contain personal information about other people, and handling it correctly is your responsibility.
2.6 Reviewer keys and signatures
A reviewer may create a Curve25519 signing key on the device. The private key stays in the iOS Keychain, accessible only while the device is unlocked. Public keys, fingerprints, signed approvals or rejections, request digests, and signing times are kept with the local group they belong to.
A fingerprint identifies a key, not a person. Comparing the full string through a channel you already trust is part of the review workflow, and nothing in the app does that for you.
2.7 Purchases, membership, and postage
Apple processes every payment, and we never receive card numbers or billing credentials. What reaches us is a transaction identifier, the product bought, the receipt needed to verify it, the membership state or postage that follows, and the ledger entries recording what was spent and when.
Membership status, its renewal date, the postage balance, and the purchase history stay with the account so they are there when you sign in on another device. Postage granted as a first-purchase bonus is recorded separately from postage bought outright.
2.8 Reports and blocks
A report carries the reason you pick, the account, message, or photo it concerns, the details you write, and the time you sent it. Reports go to our review systems; they are no longer a note that sits only on your phone. Block lists are synced so the same people stay hidden the next time you sign in.
2.9 Device, notifications, and product events
We receive the device model, operating system, app version, language, the IP address seen by our servers, and the push token Apple issues for this installation. That token lets a reply or a first letter reach you, and it is released when you sign out.
Product events are logged: launch, sign-in, screens opened, purchase steps, notification delivery, and permission prompts, each tied to the account and device that produced it. These records keep the service working and show which parts are actually used.
2.10 Support
Messages you send to support, with any details or attachments you include, are kept to answer the question and to spot a pattern if the same problem keeps returning.
3. What Hazel does not do
Hazel carries no advertising SDK, no advertising identifier, and no cross-app tracking. We do not sell personal information, do not share it for cross-context behavioral advertising, and do not assemble advertising profiles. The product events described above belong to Hazel's own operation, not to a data broker.
Photo access is requested only when you add an image, location only while Addresses is open, and notifications only when you ask to be notified. Any of them can be refused, and the rest of the app keeps working.
Private sources and Welcome letters are not sent to our systems, and no part of Hazel passes them to an artificial intelligence provider for drafting or for training a model.
Lore is still written and approved by people through the workflow in the app. Chat messages are stored so they can be delivered; they are not fed into a model.
4. How information is used
Hazel uses the information described above to:
- create and recover your account, keep you signed in, and record the adult declaration;
- show your profile to members and build the Addresses lists and filters you ask for;
- deliver messages and photos, preserve their order and read state, and show them again when you come back;
- issue first letters, apply the daily allowances, and track where each conversation stands;
- verify App Store transactions, apply membership benefits, keep the postage balance and ledger correct, and restore purchases;
- send the notifications you enabled and route a tap to the right screen;
- review reports, enforce blocks, and act on misuse, fraud, or attempts to get around the allowance and billing rules;
- measure how the app is used and diagnose failures, and
- meet legal obligations that apply to us.
We do not make automated decisions that produce legal or similarly significant effects about you. Allowance and billing checks apply the rules configured for the product, and a person reviews the reports that may lead to a restriction.
5. Legal bases where required
Where data protection law asks for a legal basis, Hazel relies on the following as applicable:
- Performance of a contract: processing needed to run the account, the community features, the store, and the welcome tools you request.
- Legitimate interests: keeping the service secure, preventing misuse of allowances, signing tools, or billing, answering support questions, and improving reliability, without overriding your rights.
- Consent: optional actions such as signing in with Apple, allowing notifications, granting location or photo access, or sharing an export. You can withdraw by changing the setting or by not using the feature, though copies already received by other people stay with them.
- Legal obligations: retaining or disclosing information when the law requires it.
6. Storage and security
Community records — account, profile, messages and media, reports, blocks, membership, and the postage ledger — are held in Hazel's hosted systems. Welcome groups sit in a SQLite cabinet inside the app's Application Support directory, excluded from device backups and protected by iOS file protection. Reviewer private keys stay in the Keychain.
Traffic between the app and our systems uses encrypted connections. Cached copies of chats and images remain in the app container so screens open quickly, and they clear when the account is deleted or the app is removed.
No system is perfectly secure. Protect your passcode and your Apple account, keep the device updated, and tell support if you think someone else has reached your account.
7. Sharing and disclosure
We share information only in the situations below, and never for someone else's advertising:
- Apple — handles sign-in and processes every purchase under its own policy;
- Communications providers — carry messages, media, and push notifications, under our instructions and with no right to use the content for their own purposes;
- Hosting and storage providers — keep the service and its records running;
- Measurement providers — operate the tooling that records the product events described in section 2.9;
- Safety and review providers — where we use them, they help assess reports and abusive content;
- Authorities — where the law, legal process, or a valid government request requires it, or where disclosure is reasonably necessary to protect rights, safety, or security.
Each supplier is bound by a contract that requires confidentiality, limits its use of the data to the tasks we assign, and requires safeguards no weaker than those described on this page. None of them receives your private sources or Welcome letters, because we never hold them.
8. Retention
Account, profile, messages, media, blocks, membership, and postage records are kept while the account is open and for the short period needed to close it. A report may be kept after the content it describes has been removed, so that repeated behaviour can be recognised and a decision explained later.
Welcome groups and letters stay on the device until you delete them, delete the account, or remove the app container. Signing out leaves them where they are. Exported files are held by whoever received them, under their own arrangements; Hazel cannot recall one.
9. Deleting your account
Deletion starts in the Me tab. After you type the confirmation, Hazel asks its systems to remove the account, the profile, the messages and media attached to it, the block list, the membership state, and the postage balance. The action cannot be undone.
The Welcome letters on your device are not part of that server deletion. They remain in the app until you remove them there or remove the app, which is how the local side of Hazel has always worked.
Deleting an account does not cancel an Apple subscription; that is done in Apple ID settings. Messages another member has already received stay in their conversation. If deletion reports an error, treat the account as still open, retry once the error is addressed, or contact support.
10. Your choices and rights
You can edit or remove profile details, delete messages in a conversation, block a member, turn off notifications, withdraw photo or location access in iOS Settings, or delete the account in the app. Declining an optional permission limits only the feature that needed it.
Subject to applicable law, you may have the right to know what personal information is held about you, obtain a copy, correct it, delete it, restrict or object to certain processing, or withdraw consent. The app's screens handle most of that directly; for anything else, write to feedback@hazelcusk.com and describe what you need.
We may need to confirm that the request comes from the account holder. We will not discriminate against you for exercising a privacy right, and mandatory rights under your local law are not limited by this policy.
11. Regional privacy rights
California and other United States privacy laws
If you are a California resident, the CCPA and CPRA may give you rights to know, access, correct, and delete personal information and to receive a copy. Hazel does not sell personal information, does not share it for cross-context behavioral advertising, and does not use sensitive personal information to infer characteristics about you.
Residents of other states with comprehensive privacy laws may have similar rights to access, correct, delete, obtain a portable copy, or object to certain processing. Use the in-app controls first, and the support channel where assistance is needed.
EEA, UK, and Switzerland
If the GDPR or UK GDPR applies, you may have rights of access, rectification, erasure, restriction, portability, and objection, and rights concerning automated decision-making. Hazel does not make decisions with legal or similarly significant effects by machine alone. You may also complain to your local supervisory authority.
Where Hazel decides why and how information is processed for the community and the store, it acts as a controller for those operations. For Welcome material kept on a device, the person who entered it decides what is collected and who receives an export.
12. Children and age
Hazel is for adults of at least 18, or the age of majority where you live if that is higher. The app is not directed to children, and nobody below that age may create an account or publish content.
The declaration at sign-in is the only age check the app performs, and it is a click rather than a document review. If you believe someone under 18 has an account, report the profile or contact support, and the account will be reviewed and closed where appropriate.
13. International processing
Hazel offers the Service in the United States, but the providers that host, deliver, and measure it may operate in other countries. Information described in this policy may therefore be processed outside the country where you are, under written terms and the safeguards our providers maintain.
Welcome material that never leaves the device is not transferred by Hazel at all. If you export a letter and send it somewhere, the destination and its rules are your choice.
14. Changes to this policy
We update this policy when the app, our providers, or the law changes. The revised page carries a new effective date, and a change that materially affects how information is handled is announced before it takes effect where the law requires it.
A new feature that would send information to a new kind of recipient gets its disclosure first, and its own control where one is needed.
15. Contact
Hazel privacy and support
Privacy requests and support questions go to feedback@hazelcusk.com. Include the app version, device, operating system, and the steps that led to the issue.
Do not attach private source material, reviewer keys, exported letters, or another person's details unless the issue needs them and you understand where the message will go.