CATEGORIED · IOS APP · PRELAUNCH
Categoried iOS privacy notice
Last updated October 13, 2026. This notice describes the current development app and services. Categoried has not been released on the App Store; Production public services and account deletion are not ready. This notice is separate from the website privacy notice.
Operator and intended audience
Eateri, Inc., United States, operates Categoried. Contact support@eateri.co about this notice or your app data. Categoried is intended for adults aged 18 or older in the United States. Signup requires you to confirm age and U.S. residence; it does not independently verify either. This development scope does not announce a release date or additional distribution regions.
Information we handle and where it comes from
The information depends on what you provide, your account, and the features you use.
- Account and profile. Sign in with Apple supplies an account identifier and authorization data, and may supply your name and an email or Apple relay address when requested. We store account identifiers, username and username claims, selected profile photo, interests, friend/share code and optional profile details. Your username, photo, interests and other profile information can be discoverable by other users. The app moves an available email into private CloudKit account settings before clearing an older public profile copy; an unsuccessful migration or dormant development record can leave an older copy.
- Messages and organization. Conversation and category names, text, context labels, participants, timestamps, replies, reactions and attachments are stored in Apple iCloud/CloudKit and account-scoped device caches. Private/shared conversations use CloudKit sharing: their owner and accepted participants can access the shared content. The app does not claim end-to-end encryption. Drafts, offline sends, thumbnails, search/organization state and records of pending operations can remain locally while work is pending.
- Public spaces and photos. Public space/category names, posts, author/profile references, reactions and published attachments are intended to be publicly readable and may be copied by others. Public spaces and photos remain in the planned release scope, but service publishing, photo upload/review, ownership transfer and account-cleanup rollout are currently disabled. Draft commands and photo preparation data may remain on the device. A future enabled public-photo review would make a submitted photo and associated post/account context available to authorized reviewers before publication; that rollout is not live.
- Reports and review. A report can contain the reporter/account binding, target identifiers, reason, optional details, copied text evidence, and submission time. The Development service stores private report records and staff decision/status records; an authorized staff console has returned a decision for a development test report. The current Release client is prepared to use the service and refuses unavailable Production reporting rather than falling back to the older direct CloudKit report path. Production reporting and moderation have not been accepted or enabled.
- Preferences and notifications. Privacy preferences, notification-preview choices, follows and blocked-user identifiers are stored in private CloudKit records and local account-scoped preferences. Enabled notification previews can include conversation names and message text. Notifications, screenshots, saved photos and device backups can remain under your device and Apple settings.
- Photos and links. We process photos you choose or capture, resize/re-encode message images and create thumbnails before upload. The photo picker does not require uploading your whole library. Saving a received image is a separate user action. Profile photos and private-message attachments are separate from the disabled public-photo rollout. Link previews are enabled by default in preferences and can be turned off. Opening or previewing a link may send a request, IP address and other network information to that website.
- Account verification and service records. Our Cloudflare-hosted Apple account service receives Apple identity proofs and authorization codes, verifies enrollment and stores encrypted refresh grants and limited account-operation state. Development public-identity verification also receives a temporary CloudKit web proof to bind the Apple profile to its CloudKit actor and lifecycle, and returns short-lived session credentials. Native CloudKit web tokens/session capabilities are held in memory rather than saved by the client. Request IP information is processed for hashed rate-limit keys; Cloudflare also processes network/routing/security metadata. Fixed application events and status codes are logged. The Apple service configuration enables sampled traces; report-service traces and invocation logs are disabled. This is not a promise that the provider processes no metadata.
- Support. If you email us, we receive your address, message, any attachments you supply and the information needed to follow up. Avoid sending passwords, verification codes, payment details or entire private conversations.
Purposes
We use this information to authenticate and bind accounts, show discoverable profiles, deliver and organize conversations, sync shared content, apply preferences and notifications, support offline work and recovery, operate public-space features when enabled, receive and review Development reports, prevent abuse, protect account/service integrity and respond to support or privacy questions. Recovery and verification records help prevent repeated or unauthorized changes after a failure. A disabled feature is not represented here as a live Production service.
On-device tools, purchases and SDKs
Category suggestions use Apple on-device language processing. Summary, idea and custom-prompt tools use Apple's on-device Foundation Models on supported devices with Apple Intelligence available. They analyze an excerpt of loaded messages; the current implementation sends no such excerpt to a Categoried cloud AI provider. Results can be incomplete or wrong and are not automatically posted to a conversation.
Purchases and premium enforcement default off, and cloud-AI allowances are zero. StoreKit entitlement code exists; it does not establish that paid products are offered. No active advertising, third-party analytics, third-party crash-reporting or external AI SDK was identified in the current source/dependency review. The app privacy manifest declares no tracking; it does not substitute for App Store privacy disclosures. A final signed build and enabled services must be checked again before distribution.
Recipients and providers
Other users can access discoverable profiles, accepted shared conversations and public content as described above. Authorized Eateri operators can access Development report/evidence and decision records and support messages; the development console restricts staff access. It does not establish a staffed Production moderation service or a response-time promise.
Apple provides Sign in with Apple, iCloud/CloudKit, notifications, operating-system services and on-device tools; StoreKit code supports purchases if separately enabled. Cloudflare hosts the Apple account service, Development public identity/report services and protected staff console. These providers process the information necessary for those services. Websites you open or preview receive their own requests. Their privacy information is available from Apple and Cloudflare. Provider storage, network metadata and backups are separate from data visible in the app. This notice makes no unverified claim about global storage location, immediate physical erasure or provider backup deletion.
Storage and retention during prelaunch
Records can exist in Apple CloudKit, local app storage, Cloudflare account/report/operation storage, our support mailbox and provider-managed logs or backups. During prelaunch, account, conversation, public-content, report and related service records may remain until a supported removal or verified cleanup actually removes them. There is no currently verified automatic inactivity or closed-report purge schedule. A staff report decision does not itself erase the report or evidence. Expiry of an authentication session does not delete the account's data. Local caches can be trimmed by size/count, but that is not a guaranteed erasure deadline. Signing out or deleting a visible item does not establish that all related records have been erased.
Records needed to resolve an interrupted operation can remain while its outcome is unresolved. Full account deletion is currently unavailable. Our approved account-deletion design removes the departing user's reports and evidence and retains only a minimal safety receipt with the account/CloudKit binding, lifecycle ID, deletion operation ID and completion status until a safe replacement-account transition supersedes it. It contains no messages, reports or evidence, but the identity binding is not anonymous. No fixed 90-day report or 30-day receipt promise applies.
We keep support correspondence needed to handle and follow up on requests; no automatic mailbox purge period is currently verified. Provider-managed logs, backups, notifications and other users' copies may remain; we do not promise an unverified erasure deadline for them. This explains the current prelaunch limits, rather than a commitment to retain everything indefinitely. We will revise this notice to match the completed retention/deletion operations and enabled services before public distribution.
Account deletion and recovery limits
Account deletion is currently unavailable in the normal app runtime. Readiness is checked before a new deletion journal or destructive cleanup begins. Development implementations and automated tests do not establish complete Production cleanup. Apple revocation/cold-start recovery, safe account replacement, provider temporary/orphan assets, legacy record coverage and connected two-account acceptance still require completion or verification.
The implemented owner policy would, after informed confirmation and verified ownership, close a departing owner's private conversation zone and erase its entire cloud history, including other participants' messages/photos in that zone. It must preserve other users' original content in conversations they own and in public spaces. Referenced removed messages may need minimal unavailable-message placeholders; unknown ownership, sharing, pending work or provider outcomes block completion. Public-space ownership may require transfer before account deletion. These are implemented safeguards and intended behavior, not a claim that deletion is enabled or has succeeded.
The account-deletion design removes the departing user's reports/evidence and verifies report/public-content cleanup before Apple revocation; Production rollout remains closed. Existing downloaded/shared copies, saved images, notification history, older public development records and provider backups can remain. Emailing support or disconnecting Apple sign-in does not itself delete CloudKit or other app records. See account data and deletion.
Choices and requests
You choose the profile details, photos, messages and public posts you provide. Change link-preview and notification-preview preferences in the app; manage camera/photo/notification permissions in iOS Settings. Blocking hides an author's content in your app, including shared-conversation views; it does not delete the author's account, remove them from a share or erase other participants' copies. Uninstalling or signing out does not delete server records.
Send privacy questions or access, correction and deletion requests to support@eateri.co, identifying Categoried and the request. Your rights depend on applicable law. Do not send passwords, Apple codes or identity documents in an initial email. Eateri’s owner checks this inbox each business day and handles or escalates privacy requests. Reliable account verification may be needed before disclosing data or making changes; an email claim alone is not authority to release information or delete an account. We explain available actions and unresolved limitations. No universal reply or deletion deadline is promised here. An acknowledgement is not a deletion receipt.
Security and updates
The app uses account binding, CloudKit access controls, HTTPS service calls, encrypted stored Apple refresh grants and restricted staff access. These controls do not guarantee absolute security. Historical development conversation records or public email copies may still have their original visibility until verified cleanup. We date this notice when updated and revise it to match material changes in the actual app/services before public distribution.
Contact
Eateri, Inc., United States. support@eateri.co. Intended canonical app notice: https://categoried.com/app-privacy/. This notice covers current prelaunch processing; it does not establish completed Production deletion or release readiness.
Drafting acknowledgement
Earlier drafting materials used General Legal, PC's publicly available CC0 U.S. privacy template. General Legal has not reviewed this adapted product notice, does not endorse it and has no attorney-client relationship with readers of it. The disclosures here must follow Categoried's verified practices and approved operator decisions.