Privacy at OurLore
Private by design, from invitation to Lore.
OurLore is made for small groups of people who already know one another. The product keeps group activity inside its approved membership boundary and avoids the public profiles, follower graphs, and open discovery that change how people tell honest stories.
Membership controls the audience
A reusable Join link creates a request that an administrator must approve. An email invitation is single-use and tied to the invited address. Neither route exposes the group’s stories before membership begins. Group profile and contribution access follows the person’s approved membership and role.
Hidden participation stays hidden
Some games depend on private answers or photos before reveal. OurLore enforces that boundary in the data layer, including against group administrators. Members see the shared result only when the round reaches the right state. This is a product rule, not a visual promise made by one screen.
Photos are prepared before publication
Still images are prepared as metadata-minimized derivatives before they become published contributions. Transfers use private storage and server-owned processing. Optional push delivery connections can be revoked independently, and notification preferences control which categories may alert a member.
Safety and account choices
Authenticated Safety reports are confidential. They include the reported material, essential server-derived context, and an optional explanation, without copying unrelated conversation into the case. Account deletion starts only after fresh proof and immediately fails closed for ordinary account access while the deletion workflow finishes.
For a question about these practices, email hello@getourlore.com. Do not send passwords, sign-in codes, private group conversation, or raw invitation and recovery links by email.