Original receipt-image processing requires acceptance of the receipt-processing terms. Acceptance covers future submitted receipts until you turn processing off. Original images, including visible personal information, may be sent to OpenAI without local redaction. Turning processing off does not delete saved records or cancel billing.
Effective date: September 19, 2026. Contact: beta@chie.house.
1. Scope
This Privacy Policy applies to Chie websites, app pages, private beta signup flows, receipt and order processing features, family-account features, support workflows, and related services that link to this policy. Chie currently includes a purchase-intelligence service that helps people capture receipts and online order records, organize purchases, search purchase history, and understand spending patterns.
This policy does not apply to websites, stores, payment processors, email providers, phone carriers, device makers, or other third-party services that you use outside Chie, even if their records are later submitted to Chie.
2. Privacy Commitments
- Purchase data is private by default. Chie is designed to organize purchase records for you and your household, not to sell shopping behavior to advertisers.
- Admins do not need purchase contents. Administrative tools are designed to show masked contacts, account status, usage counts, limits, job status, and aggregate trends, not user receipt, order, item, or purchase contents.
- AI calls are minimized. When Chie uses OCR, vision, language, or embedding providers, prompts and payloads should be limited to the data needed for the specific operation. For text operations, account identifiers and incidental personal information are stripped, tokenized, or avoided where they are not needed. Original receipt-image reading sends the submitted image without local redaction after acceptance of the receipt-processing terms.
- Aggregate reporting uses thresholds. Admin keyword and category reporting is intended to use cohort thresholds so a keyword or category is not shown when too few accounts contributed to it.
- Deletion should remove reconstructable content. Permanent deletion is intended to remove receipt/order/search/embedding content that could reconstruct a deleted purchase record, while preserving only limited structural audit metadata where needed for security, abuse prevention, and system integrity.
3. Information We Collect
Account, signup, and invite information
We collect information used to invite, create, secure, and manage accounts. This may include email address, phone number, first name, last name, preferred name, optional gender, ZIP code, derived city/state locality, account status, invite status, family membership, policy acceptance records, and support preferences.
Gender and ZIP code are optional. Chie validates a provided ZIP code and derives its city/state for the account. Beyond those setup steps, Chie may use these optional fields in cohort-thresholded aggregate analysis to understand broad patterns and improve the service. Administrative reporting is not intended to use these fields to identify a person or expose an individual's receipt, order, item, or purchase history.
If you request private-beta access by text, we collect the phone number you use, your request message, message timestamps and delivery status, and records of your SMS consent and opt-out choices. We use this information to operate the beta-access text program, send the messages you requested, and honor your messaging preferences.
Passwords are stored as password hashes, not plaintext passwords. If you create or use a passkey, Chie stores passkey credential metadata and public-key material needed to verify future sign-ins. Chie does not receive your device's private passkey material.
Purchase, receipt, and order information
When you submit receipts, receipt photos, order confirmations, forwarded order emails, pasted order text, or related records, we collect the content needed to process them. This may include merchant name, store location if present on the receipt, purchase date and time, item names, quantities, prices, totals, taxes, fees, discounts, order numbers, tracking or delivery metadata, return or warranty details, product categories, and the original image or text you submitted.
Receipts and order emails may incidentally contain personal information such as your name, email address, phone number, partial address, loyalty number, payment method label, or the last digits of a card. Chie does not need full payment card numbers, government identifiers, financial account credentials, health records, or highly sensitive personal documents. Please avoid submitting those details when possible.
Family and sharing information
If you use household or family features, we collect information needed to manage family membership, invitations, member roles, sharing status, visibility settings, receipt-credit or limit workflows, and records marked private or shared. Records marked private are intended to be visible only to the submitting account and authorized support/security processes. Records marked shared may be visible to family members according to the app's sharing rules.
Usage, device, log, and security information
We collect service logs and usage metadata needed to operate Chie, protect accounts, investigate errors, enforce limits, and improve reliability. This may include session events, login attempts, rate-limit events, CSRF/security events, feature usage counts, upload and processing status, model/provider operation metadata, approximate request time, browser or device information, IP address or IP-derived information, hashed IP or user-agent values for policy acceptance, and error diagnostics.
Communications and support
If you contact us, request an invite, request support, report a bug, or send legal/privacy requests, we collect the contact information and message content needed to respond.
For the Chie beta-access text program, you can reply STOP to opt out or HELP for help. Opting out of text messages does not remove an email-based request you made separately.
4. How We Use Information
We use information to:
- create accounts, verify invite links, authenticate users, support passwords and passkeys, and maintain sessions;
- confirm beta-access requests and deliver requested invite links by email or text message;
- process receipts, receipt images, order confirmations, forwarded emails, and pasted order records;
- extract merchants, dates, totals, items, categories, warranty or return cues, and purchase history;
- provide dashboards, analytics, search, exports, family sharing, usage limits, and account settings;
- run privacy-preserving consolidation, deduplication, categorization, and product normalization workflows;
- provide support without exposing purchase contents to administrators unless a future support workflow asks for explicit user-provided content;
- monitor security, prevent abuse, enforce rate limits, debug failures, and maintain audit trails;
- measure aggregate product usage and improve Chie's reliability, privacy protections, and feature design;
- comply with applicable law, respond to legal process, and protect rights, safety, and service integrity.
5. AI, OCR, and External Processing
Chie may use OCR, document parsing, vision models, language models, embedding models, and similar processors to read and organize purchase records. Depending on configuration, these processors may be local or external. External processors may receive receipt images, extracted text, order-like metadata, redacted snippets, or bounded prompt context needed for a specific operation.
For text model operations, Chie is designed to avoid sending account names, emails, phone numbers, postal addresses, stable account identifiers, raw forwarded email identifiers, freeform personal profiles, and source identifiers when those fields are not needed. Purchase consolidation should use item/order fields and ephemeral run identifiers. Forwarded-email template learning should use extracted order-like metadata and redacted snippets rather than raw full email content.
Receipt vision may involve sending a receipt image to an external vision provider if that operation is enabled. Chie records provider and operation metadata for security, accountability, cost control, and policy tracking.
See the AI and Data Processing Notice for additional details.
6. How We Disclose Information
We may disclose information in the following limited ways:
- Service providers and processors. We may use hosting, storage, database, authentication, email/SMS, OCR, AI, logging, security, analytics, and support vendors to operate Chie. They should process information only for Chie's service purposes.
- Family members you share with. If you join or create a family account, records you mark shared may be visible to authorized family members according to the product's sharing settings.
- Legal, safety, and security reasons. We may disclose information if we believe it is necessary to comply with law, respond to valid legal process, protect users, prevent fraud or abuse, investigate security incidents, or protect Chie's rights and service integrity.
- Business transactions. If Chie or NIXA Inc. is involved in a merger, acquisition, financing, reorganization, or sale of assets, information may be transferred as part of that transaction, subject to appropriate confidentiality and privacy commitments.
- With your direction or consent. We may disclose information when you direct us to do so or explicitly consent.
We do not sell your purchase records. We do not use purchase contents for cross-context behavioral advertising.
We do not sell or share mobile phone numbers, SMS opt-in data, or SMS consent with third parties or affiliates for their own marketing or promotional purposes. We may provide this information to communications vendors only as needed to deliver and operate Chie messages, or disclose it for the legal, safety, and security reasons described above.
7. Admin Access and Internal Controls
Chie's administrative model is built around support and security needs rather than content access. Admin views are intended to show opaque account identifiers, masked contact information, account status, signup and invite state, created date, usage counts, limits, aggregate provider usage, and job status. Admin-triggered consolidation can run for an account to provide support, but the result should return job status and metrics rather than receipt or purchase rows.
Aggregate keyword, category, and trend reporting is intended to avoid attributing sensitive patterns to a single account. Where aggregate reporting is shown to admins, minimum cohort thresholds should be enforced.
8. Cookies and Similar Technologies
Chie uses cookies or similar browser storage for authentication sessions, CSRF protection, security, and basic site operation. Private beta login requires a session cookie. We do not currently describe any third-party advertising cookies as part of Chie's service.
9. Data Retention
We keep account and purchase data for as long as needed to provide Chie, maintain your account, support exports and search, operate family-sharing features, comply with legal obligations, resolve disputes, prevent abuse, and maintain security. You can delete individual receipts where the app supports deletion, and you can request account deletion by contacting us.
Permanent deletion is intended to remove the purchase content, receipt/order source content, search documents, embeddings, provenance, and derived content that could reconstruct the deleted record. Limited non-content audit metadata may remain when needed for security, system integrity, abuse prevention, accounting, or legal compliance. Backups and logs may retain deleted information for a limited time until they rotate or are securely deleted.
Aggregated, deidentified, or anonymized usage statistics may be retained after deletion if they cannot reasonably be used to identify you or reconstruct your purchase records.
10. Your Choices and Privacy Rights
Depending on where you live, you may have rights to request access to personal information, correction of inaccurate information, deletion of personal information, a portable copy of certain information, information about categories of data collected or disclosed, and appeal or review of certain privacy decisions. You may also have the right to opt out of sale or sharing for targeted advertising and to limit certain uses of sensitive personal information.
Chie does not sell personal information or use purchase contents for cross-context behavioral advertising. If that changes, we will update this policy and provide any legally required choices before doing so.
You may withdraw consent for Chie beta-access texts at any time by replying STOP. Reply HELP for help or contact beta@chie.house. Message and data rates may apply.
To make a privacy request, contact beta@chie.house. We may need to verify your identity and account ownership before acting on a request. We will not discriminate against you for exercising privacy rights, but some deletion or restriction requests may limit the features we can provide.
11. Sensitive Information
Chie is not designed to collect Social Security numbers, full payment card numbers, bank login credentials, government IDs, precise geolocation, health records, biometric identifiers, or children's sensitive information. Optional profile fields, ZIP code, receipt contents, and purchase patterns may still be sensitive depending on context. We use them only for the service purposes described in this policy, safety/security, legal compliance, or with your direction.
12. Children
Chie is not directed to children under 13, and we do not knowingly collect personal information directly from children under 13. Family or household purchase records may incidentally relate to children, such as purchases of household goods. Do not submit children's sensitive information unless it is necessary for your own household purchase records. If you believe a child provided personal information directly to Chie, contact us at beta@chie.house.
13. Security
We use administrative, technical, and organizational safeguards intended to protect Chie accounts and purchase data. These may include password hashing, optional passkeys, session rotation, CSRF protection, login throttling, secure-cookie settings when hosted over HTTPS, access controls, masked admin views, audit metadata, data minimization for AI prompts, and monitoring for abuse or malicious activity.
No online service can guarantee absolute security. You are responsible for using a strong unique password, protecting your devices and passkeys, keeping invite links private, and notifying us promptly if you suspect unauthorized access.
14. International Use
Chie is currently designed for a U.S.-focused private beta, including U.S. ZIP-code locality validation. If you access Chie from outside the United States, your information may be processed in the United States or other locations where Chie or its providers operate.
15. Changes to This Policy
We may update this policy as Chie changes, as we add providers or features, or as legal requirements evolve. If changes are material, we will provide notice appropriate to the change, such as updating the version date, notifying beta users, or requiring renewed policy acceptance during signup or login.
16. Contact
For privacy requests, security concerns, support questions, or legal notices, contact Chie at beta@chie.house.