Privacy Policy

1. Information REXO handles

REXO is a personal finance app. Depending on how you use it, we may handle profile details for sign-in, manually entered transactions, account names, balances, subscription records, savings goals, receipt images, receipt text, voice recordings selected for transcription, language settings, device-level settings, and product diagnostics.

• Core finance data is created directly by the user.
• AI input is collected only when the user types text, selects or captures a receipt, records a voice entry, or requests an insight inside a clearly labeled AI feature.
• Cloud data is only used when the user signs in and chooses synced features.
• Subscription status is handled to unlock paid app features and restore purchases.

2. How we use information

We use information to operate the product, sync the user account across devices, restore subscriptions, generate receipt drafts, categorize transactions, improve reliability, prevent abuse, and respond to support issues. We do not use transaction content for advertising.

3. Third-party processors and infrastructure

REXO uses specialized processors only for the parts of the service they support. These providers receive only the data reasonably required for that task. REXO requires each processor, including OpenAI, to maintain the same or equivalent protection for personal data described in this policy and required by applicable law.

• Supabase: authentication, account session management, and optional cloud sync.
• RevenueCat: subscription state, entitlement status, and restore-purchase handling.
• OpenAI: optional AI-assisted categorization, receipt extraction, and finance insight generation.
• PostHog (when enabled): privacy-scrubbed product events and coarse app/device metadata for stability and feature quality; raw financial content is excluded.

4. AI Services and Data Processing

REXO uses OpenAI, LLC as its third-party AI processor for optional receipt analysis, voice transcription, spending insights, smart categorization, and AI coaching. Before any third-party AI request is sent, REXO presents an in-app disclosure that names OpenAI, lists the data involved, explains the purpose, and requires an explicit Allow decision. When a user invokes an AI feature after allowing it, only the limited data needed for that request is securely sent through authenticated REXO backend services to OpenAI.

• Information shared may include receipt images or text; voice recordings selected for transcription and a language hint; merchant names; transaction descriptions, notes, amounts, currencies, dates, and categories; subscription names and amounts; and summarized recent spending patterns.
• This information is shared only to provide the specific AI-powered feature requested by the user.
• REXO does not send bank login credentials, card numbers, passwords, Apple ID, or payment authentication information to AI providers.
• Users can decline consent or revoke it at any time from Settings > AI & Privacy. Third-party AI requests remain blocked while consent is disabled.
• Consent is bound to the signed-in user and disclosure version. Every AI endpoint verifies authentication and current consent before contacting OpenAI.
• AI provider credentials remain server-side. REXO applies data minimization and rate limiting before provider requests.
• REXO does not sell AI input or authorize OpenAI to use it for advertising. OpenAI processes API data under its privacy terms and API data controls.

5. What REXO does not collect for AI

REXO does not support bank-linking credentials and does not request or transmit bank usernames, bank passwords, card numbers, CVV values, ATM PINs, or other financial account authentication secrets for AI processing.

6. Analytics and minimization

REXO is designed to minimize transmitted financial content. Product analytics are configured to avoid raw amounts, merchant names, free-form notes, balances, passwords, phone numbers, and email content whenever those fields are not required for the event.

7. Retention and deletion

Finance data stored only on the device remains local until the user edits, deletes, or removes the app. When cloud sync is used, synced records remain in the backend until the user deletes them, deletes the cloud account in-app, or requests support assistance. REXO does not intentionally retain receipt images or voice recordings in its AI Edge Functions after the requested response is returned. OpenAI handles API request retention under its API data controls and privacy terms. Subscription and minimal consent/audit records may be retained for billing integrity, privacy compliance, fraud prevention, legal compliance, and support operations.

8. User controls

Users can review or change notification settings, subscription status, privacy links, and AI preferences inside the app. Signed-in users can also delete their cloud account from the Settings screen. Users can contact support for privacy questions or operational deletion requests.

9. Security

REXO uses reasonable technical and organizational safeguards intended to protect account access, synced data, and service operations. No internet-based service can guarantee absolute security, so users should also secure their device, operating system, and sign-in credentials.

10. International transfers

Because infrastructure or service providers may operate in multiple countries, user information may be processed outside the user’s home jurisdiction. Where applicable, REXO uses contractual and operational measures intended to protect data during those transfers.

11. Changes to this policy

We may update this Privacy Policy when the product, legal requirements, or operational practices change. The effective date at the top of this page will be updated when material revisions are published.

12. Contact

For privacy questions, support requests, or operational deletion assistance, contact support@rexo.app.