Privacy Policy

This policy explains how NoteBound collects, uses, shares, and retains information when you use our iOS app, website, and browser reader. It also explains your choices and what happens when you delete your account.

1. Who we are

NoteBound lets you write, organize, share pages, and exchange messages. It is operated by Chreia Labs, LLC (“NoteBound,” “we,” “us,” or “our”). Where applicable data protection law uses that term, Chreia Labs, LLC is the controller of the information described here.

Contact us at theteam@chreialabs.com. Our website is chreialabs.com/notebound.

2. Information we collect

Accounts and profiles

We collect your account ID, email address, display name, unique @handle, optional profile photo, and account settings. Supabase handles authentication; passwords are not stored in plaintext. You can use email and password, Sign in with Apple, or Sign in with Google. These providers supply sign-in identifiers and may supply your name and email. Apple’s Hide My Email can supply a relay address.

Verifying an email to read an invited-only browser link creates or signs in to a NoteBound account. Anyone-with-the-link access does not require an account.

Other signed-in users can discover your display name, @handle, and profile photo through search and people suggestions. Suggestions use accepted friendship relationships to find possible connections, or suggest other eligible profiles. We do not show mutual-friend identities or expose the underlying friendship graph in suggestions. Profile photos are stored at public URLs, so someone with the image URL can view the photo.

Pages and organization

We store pages locally. When you are signed in, titles, body content, icons, content links and organization, creation and update times, trash state, and sharing settings sync to our cloud database. Images embedded in synced page content are part of that content.

Files attached to pages are currently stored on the device where you add them. Page syncing and browser sharing do not upload those attachment files. This differs from chat files.

Friendships, messages, groups, and chat attachments

We store friend requests and their status, accepted connections, conversations and group names, membership and permissions, message text, sent times, read positions, and page deliveries. Photos, voice recordings, and other files you send in chat upload to private cloud storage, with their filename, type, size, and storage reference. Voice recordings also include their duration and a waveform used for playback. Authorized participants retrieve files through temporary download links.

Conversation participants receive the messages, photos, voice recordings, files, and pages you send. Group members can see membership and relevant profile information. New members see messages sent after they join; removal ends conversation access, but cannot erase copies already saved.

Sharing and browser links

We store recipients, access levels, invitations and responses, exclusions, and legacy block selections where they still apply. Browser-link records include an access token, optional name, access mode, selected pages and blocks, invited emails, and creation, update, and revocation times.

In-app sharing can include connected descendant pages, subject to exclusions and permissions. Edit access lets recipients change authorized content. Adding a received page to a Notebook records that the recipient saved it. Group removal does not automatically revoke saved pages; an owner can separately revoke page access.

Browser links are view-only:

• Anyone with the link: anyone who obtains or is forwarded the URL can read the authorized content without signing in.
• Only invited people: readers must sign in with a confirmed email on the invitation list. The signed-in owner can also read the link.

Whole-page links include future additions and reachable nested pages belonging to the same owner. Selected-content links include selected blocks and separately selected nested content. New blocks stay private, while edits inside selected blocks remain shared. Shared titles and icons can appear in the reader. Our server filters unauthorized content before sending it to the browser.

Disabling a link, removing an invited email, or changing scope affects future reads. Trashing the original page permanently disables its browser links, even if restored. Browser and in-app permissions are managed separately. Ending access cannot erase screenshots, downloads, exports, or other copies already made.

Notifications and device information

If you allow push notifications, we store a push token linked to your account, device platform and model, and registration times. Expo processes an installation identifier and the device push token to register and deliver notifications. App update requests also send Expo an installation identifier, platform, app runtime information, and any previous fatal update error needed for recovery. We store notification preferences and activity records for messages, friend requests, and sharing updates.

Expo and Apple deliver push notifications. Delivery payloads include push tokens and routing identifiers. Chat alerts use a generic new-message notice rather than message text; friendship and sharing alerts may include a handle or page title. Device settings control lock-screen visibility.

Purchases and subscriptions

Apple processes NoteBound Plus purchases through the App Store; we do not receive your full payment card number. The app and our server verify Apple-signed purchase and subscription records, transaction identifiers, and the account association used to restore access and determine subscription status. We store plan and entitlement information, including subscription source and expiration, to apply features and limits.

Support and technical requests

When you contact us, we receive your email address, correspondence, and information or files you provide. In-app abuse reports include the reporter and reported account identifiers, the selected reason, optional details, relevant profile information, and a limited snapshot of recent messages the reporter could already read. Reports are private to NoteBound rather than other app users. Hosting, authentication, storage, and delivery providers process technical request information such as IP addresses, approximate country or city inferred from an IP address, request times, browser or app information, and error or security logs to operate and protect the service. We do not use device location services to obtain your location.

3. Permissions, local storage, and exports

You choose which photos and files to provide. Chat photo selection uses the system picker; setting a profile photo may request photo-library permission. Saving a received photo requests permission to add to Photos. File selection and archive import use the system file picker. Recording a voice message requests microphone permission. Recordings stay on your device until you send them; sent recordings use the same private storage and participant access controls as other chat files. Manage photo, microphone, and notification permissions in iOS Settings.

Current features do not request access to your device address book, location, or camera. Friendship and group relationships created within NoteBound are stored to provide messaging, sharing, and people suggestions. We do not use the advertising identifier (IDFA) or request App Tracking Transparency permission.

The app stores a local page database, attachments, account information, preferences, caches, and pending messages and files. Authentication tokens and remembered account information use iOS secure storage. One account is signed in at a time; device account listings do not grant account access.

The browser reader stores its sign-in session and current link in tab-scoped session storage, and its appearance preference in local storage. You can sign out and clear browser site data; that does not delete your account.

Portable page exports are ZIP files containing readable Markdown, editable documents, available local attachment files, and preserved legacy drawings or previews. Missing files are listed. Legacy JSON backups lack attachment bytes. Page exports do not include chat history. Exports can contain private content; a person, app, or service you send them to receives that information.

4. How and why we use information

• Authenticate you, maintain your account, and provide account recovery.
• Store and sync pages, organize content, and enforce sharing permissions.
• Help people find one another, manage friendships and groups, and deliver messages and files.
• Deliver notifications according to your settings.
• Verify purchases, restore subscriptions, and apply plan limits.
• Respond to support and privacy requests, prevent misuse, troubleshoot failures, and meet legal obligations.

Where a legal basis is required, we process information to provide the service under our agreement with you, with consent where required, for legitimate interests in operating and securing the service, or to meet legal obligations. You can withdraw consent where applicable without affecting earlier lawful processing.

5. Who receives information

Other users and browser readers receive profile information and content you make available as described above. We also use these providers:

• Supabase: authentication, database, and storage for profiles, synced pages, chat, and uploaded chat attachments.
• Resend: delivery of account verification and recovery emails, including recipient email addresses and email contents.
• Vercel: website and reader hosting. Share tokens are in URL fragments rather than page request paths; the reader sends them to Supabase to check access.
• Expo and Apple: push delivery; Expo also provides app delivery and update infrastructure.
• Apple and Google: optional sign-in; Apple also distributes the app and processes purchases.
• Apple App Store: payment processing, signed subscription records, purchase restoration, and subscription notifications.

Providers process information for their services subject to applicable privacy, security, and contractual obligations. We may also disclose information when legally required, to address fraud or threats to safety, or in a business transfer such as a merger, subject to applicable protections and notice requirements.

6. Advertising, tracking, and security

We do not sell personal information or share it for cross-context behavioral advertising. NoteBound does not currently include advertising or third-party behavioral analytics SDKs. Our service providers process operational request, security, and error records, including fatal update errors used by Expo for recovery, to deliver and protect the service. These records are not used for advertising tracking.

We use authenticated access controls and encrypted network connections. NoteBound does not provide end-to-end encryption for pages or messages. Sharing controls and private-looking icons are not encryption. No storage or transmission system can guarantee absolute security.

7. Retention and account deletion

We keep account and content records while needed for the service, including syncing, conversation history, and access to saved pages. Trashing a page is not account deletion. Technical and support records may remain as needed for security, troubleshooting, disputes, and legal obligations; provider backups may persist until their normal deletion cycle.

Delete your account in the app from Profile → Delete account, or contact theteam@chreialabs.com for assistance. We may verify that a request comes from the account owner.

Deletion removes your sign-in account, profile, settings, owned browser links, pages no other person saved, and the messages and chat attachments you sent. Saved recipient pages are handled below. It removes your profile attribution and message content from retained conversation records. Other participants’ own messages remain. It also clears the account’s working data and session on the device completing deletion. If interrupted, retry in the app or contact us.

Pages another person explicitly saved before deletion remain available in that person’s Notebook. This includes descendant pages they were authorized to save and files needed to display that content. Saved pages retain the content you chose to share under an archive owner that cannot sign in. The archive owner does not retain your profile name or profile photo. Account deletion does not grant access to previously unshared content. Information we are legally required to retain is kept only for the required purpose and period.

Signing out does not delete your cloud account. Removing a remembered account removes that listing, not the cloud account or all local files. Uninstalling removes files in the app sandbox, but does not delete cloud records, exports, files outside the app, or copies on other devices. Secure-storage entries can survive uninstalling. Copies other people saved outside NoteBound remain under their control.

Account deletion does not cancel an Apple subscription. Cancel Plus in iOS Settings → [your name] → Subscriptions or Apple’s subscription settings.

8. Your rights and choices

You can update your profile, change sharing and notification settings, export pages, revoke links, and delete your account. For access, correction, deletion, or other privacy requests, email theteam@chreialabs.com. Do not send passwords or sign-in codes. We may verify identity and respond according to applicable law.

Depending on your location and applicable law, you may have rights to access, correct, delete, or receive a portable copy of personal information; restrict or object to processing; withdraw consent; or appeal a request decision. Exceptions may apply, including for legal obligations and the rights of others. You can complain to your local data protection authority where that right applies.

For European Economic Area and UK residents, these rights apply as provided by relevant data protection law. California residents may also have rights to information about collection and disclosure and freedom from discrimination for exercising privacy rights. We do not sell or share information for behavioral advertising.

9. Children

NoteBound is not directed to children under 13 or below a higher minimum age required in their jurisdiction. We do not knowingly collect their personal information. Contact us if you believe a child has provided information so we can investigate and take appropriate deletion measures.

10. International processing

Our Supabase services are hosted in the United States. Providers may process information in the United States and other countries where they operate. Information may be transferred to countries whose privacy laws differ from yours. Where required, transfers are subject to legally recognized safeguards.

11. Changes and contact

Updates appear at chreialabs.com/notebound/legal/privacy with a revised effective date. We provide additional notice or obtain consent for material changes where required by law. This policy describes our practices and does not waive your privacy rights.

Privacy questions and requests: Chreia Labs, LLC, theteam@chreialabs.com.