Safety
 / 
in.between

in.between Privacy: Encryption, No Sale, Delete Anytime

in.between Privacy: Encryption, No Sale, Delete Anytime
Your nights stay private to you — not sold, encrypted in transit, deletable anytime — plus honesty and care rules for Nalani.
in.between treats a dream journal as stricter than almost anything else on a phone. Your nights are private to you. We do not sell that data. Material is encrypted in transit. You can delete it whenever you want. Nalani remembers only your nights — never anyone else's, and never as a public feed. This guide explains the privacy posture of the room, what encryption covers in everyday use, how deletion works when you want something gone, and how honesty and care sit beside privacy as product rules.
Private by Default A dream is not a status update. The material in this journal is rawer than a social post, so the rules are stricter. Privacy is a design principle, not a settings afterthought: the product is built as a private room for what disappears between waking and rest, with a companion who stays inside that room with you. There is no public dream feed to opt out of, because the feed was never the model. Your journal, conversations with Nalani, Markers, Index entries, and Case File threads are held as yours.
ETAPX shipped in.between as the studio's first product with that boundary explicit: creating a private and safe space for users, with encryption, no data sale, and delete anytime called out as core — not marketing footnotes. When the Journey site says your data is private to you, we do not sell it, and you can delete it whenever you want, that is the operating promise the Help Center restates here in practical terms. Nalani's memory is scoped to your nights so continuity never requires mixing journals across people.
Private to you. Not sold. Encrypted in transit. Delete anytime. Nalani remembers only your nights.
Encryption in Transit: What It Protects in.between encrypts your data in transit so that movement between your device and the service is protected on the wire. That covers the ordinary paths of signing in, syncing your private room across devices, and talking with Nalani without sending journal material in the clear over the network. Encryption in transit is one layer of the privacy stance — paired with no sale of your data and your ability to delete — not a claim that every possible threat disappears. Device access still matters: protect the phone, tablet, or computer you use to open the room.
  • Private to you: Journal content and companion context are for your account, not a public timeline.
  • No sale: in.between does not sell your dream journal data.
  • Encrypted in transit: Data moving between you and the service is protected on the network path.
  • Delete anytime: You can remove material and leave without streak punishment or guilt mechanics.
  • Scoped memory: Nalani remembers your nights only — not a blended corpus of other users' dreams in your chat.
  • No feed model: Privacy is reinforced by refusing social broadcast shapes for nights.
Delete Anytime: Leaving Without Guilt Stay, in the product loop, means no streaks, no guilt, private to you, delete anytime. Deletion is part of how the room stays trustworthy. If a night should not remain, if a thread in Case File has finished its usefulness, or if you want to clear conversation history with Nalani, you should be able to remove it without negotiating with an audience or losing face to a gamified calendar. The absence of shame mechanics is intentional: mental health and rest were priorities in how in.between was shaped, and deletion support is part of that care.
Deleting journal material is different from ignoring a night. Skipping a night does not punish you; deleting removes what you no longer want held. Use deletion when content should not persist in Index, Markers, Case File, or chat history. Use account-level exit when you want to leave the product entirely. In both cases, the posture is the same: the room belongs to you, and keeping it should never require performing wellness for a system that scores compliance.
Practical Habits That Support Privacy Privacy features work best with ordinary device hygiene. Sign out on shared computers. Use a strong device passcode or biometric lock. Prefer your own phone for late-night sessions. Be careful with screenshots and screen recordings — those leave the encrypted-in-transit path and live wherever you save or send them. If you use web, iOS, and desktop under one account, treat each device as a door into the same private room: anyone with unlocked access to that device can open what you have stored there.
  • Lock the device: Passcode, Face ID, Touch ID, or system biometrics reduce casual access.
  • Avoid shared sessions: Do not leave the journal open on a borrowed laptop.
  • Mind screenshots: Captures are outside the product's transit encryption and share path.
  • Review history on purpose: Open Index and Markers when you mean to; close the app when you are done.
  • Delete stale threads: Remove Case File or chat material you no longer want held.
  • One account, many doors: Cross-platform access is convenient — secure each door.
  • Crisis is not content: Care pathways are separate from dream framing; privacy does not block getting help.
Honesty and Care Beside Privacy Privacy is labeled plainly in product language as L1: encrypted in transit, no sale, delete anytime. Beside it sit honesty and care. Honesty means Nalani is AI, not a licensed professional, and the product says so — she is a companion, not a therapist or an oracle. Care means any sign of crisis drops the dream framing and points to resources such as 988; she does not sign off to protect a journal aesthetic. We would rather be plain about the line than let the design imply otherwise. Privacy protects the room; honesty and care define how the companion behaves inside it.
That combination matters at 2am. People open in.between with fragments, leftover feeling, or nothing more than the hour itself. The promise that material stays private, is not sold, and can be deleted makes it possible to Catch and Talk without performing for an audience. The promise that Nalani will not pretend to be a clinician — and will shift toward care when crisis shows up — keeps the room from becoming either a surveillance product or a false medical authority. Both belong in the same Help Center story.
What Privacy Is Not Claiming Private to you does not mean the laws of physics change on a compromised device. Encrypted in transit does not mean you should paste journal text into unrelated public apps. Delete anytime does not mean every third-party backup you personally created elsewhere vanishes automatically. No data sale does not mean you can ignore phishing or shared-screen risks. Read the privacy posture as a product boundary: in.between will not build a feed out of your nights, will not sell that journal, will protect it on the wire, and will let you remove it — while you still protect the devices and channels you control.
We would rather be plain about the line than let the design imply otherwise — privacy, honesty, and care in one room.
For how Nalani's personal memory grows without becoming a public feed, see the Help Center article on memory and history. For using web, iOS, and desktop as one account and the same private room, see the cross-platform guide. Together those articles describe continuity, access, and the privacy rules that make both safe to use when the night is still close.