Privacy Policy

1. ACCOUNT AND PRODUCT DATA

Ari stores the account details you provide, such as your name, email, optional phone number and profile preferences. It also stores records you choose to add: transactions, descriptions, notes, budgets, goals, planning inputs, tax-profile inputs and shared-expense information.

Information you enter in a shared group is used to show group expenses and settlements to its members. A UPI ID is used when you choose to provide one for payment links. Linked-bank data is processed only through the bank-linking features you choose to use and their separate approval flow.

Country, currency and language preferences are selected in the product. This page does not claim that Ari infers your city from your IP address. Hosting and security services may process connection information when handling requests.

2. VOICE AND AI FEATURES

Voice input uses the speech-recognition service available on your device. Ari does not force on-device-only recognition; processing can depend on your operating system, speech provider, language and settings. The current Ari voice-capture implementation receives transcription text rather than uploading an audio recording to the Ari API.

Transcribed or typed text may be sent to Ari to parse an entry. When you use Tomo or other AI-assisted features, your message and relevant recorded financial context may be sent through the backend to its configured AI provider. The implementation supports DeepSeek and Google Gemini; the provider used depends on server configuration and availability. Avoid entering passwords, payment credentials or other unnecessary sensitive information.

3. OPTIONAL PRODUCT MEASUREMENT

Product measurement is off until you opt in. It is first-party and linked to your account, rather than anonymous browsing analytics. It records allowlisted actions, event identifiers, server receipt times, a consent identifier and a timezone for local-day activity. It may include report and insight actions, confirmed entry creation, planning saves, trial starts, notification delivery/open attribution and verified billing lifecycle events.

Measurement payloads exclude amounts, notes, merchants, message contents and recordings. Consented billing observations also store event kind, provider event time, optional subscription cycle start/end, and a consent-scoped pseudonymous subscription reference. Raw provider/customer identifiers, product IDs, currency and payment details are not copied into measurement. These observations expire within the same 90-day history. The optional measurement flow does not use PostHog or session replay. Billing and notification records needed to operate those services are separate from optional measurement.

Event history expires after 90 days. Reports exclude expired events; physical cleanup runs through maintenance and applicable measurement operations. Minimal consent state and timezone remain until withdrawal or account deletion. An expired-activation flag prevents old accounts from being incorrectly counted as newly activated. Staff/test exclusions, where applied, remain until removed or the account is deleted.

Turn off Help improve Ari in Settings to withdraw measurement consent and erase retained measurement data. Opting in again starts a new consent identifier. Mobile Private Mode suppresses device measurement calls; it does not withdraw account-level consent or stop server-side billing/notification measurement. Use the measurement control to stop that collection.

4. NOTIFICATIONS, DIAGNOSTICS AND SERVICE PROVIDERS

Notification features use your permission, preferences and an Expo push token to send supported reminders. Permission or preference changes affect notifications separately from measurement consent.

Crash and performance monitoring can use Sentry when configured for a build or backend. Mobile diagnostics may include your account ID, name and email, error details, breadcrumbs, device/build information and performance traces. Mobile screenshot attachment is disabled. Product-measurement consent and Private Mode do not control this separate diagnostic configuration; this policy does not promise universal removal of personal data from errors.

The product integrates Supabase for authentication/data storage, Railway for backend hosting, Vercel for this website, Expo for push delivery, configured AI providers, and supported sign-in providers. Optional paid features can involve RevenueCat, the relevant app store or a configured payment provider. Optional bank linking involves Setu and the bank approval service. Availability depends on the feature and service configuration; provider-hosted pages have their own privacy information.

5. RETENTION AND YOUR CONTROLS

Your active account records support the features you use until you remove them or delete the account. You can review and correct supported records, download an account export, withdraw optional measurement consent, change notification preferences, and request account deletion.

Account deletion removes the account and associated application records through the authenticated deletion flow. Copies in infrastructure backups and external billing, diagnostic or other provider systems have separate retention and deletion processes. We do not represent a fixed backup-erasure deadline as verified here.

See account deletion instructions. For account-access or privacy questions, contact privacy@pinegrass.in.

6. SECURITY AND CHANGES

Hosted application requests use HTTPS and account-scoped access controls. No service can guarantee that every security incident will be prevented. This page does not certify provider contracts, data residency or compliance with every jurisdiction.

Ari is not intended for users under 18. We may update this page as the product changes; the date above identifies this version.

7. CONTACT

Pinegrass Technologies Pvt Ltd
Email: privacy@pinegrass.in
Phone: +91 7629001131
Registered address: Pinegrass Technologies, Al Haj Jalal Manzil, Hatta Mana Ingkhol, Imphal, Manipur, 795001.