1. Who we are and where this policy applies
Rich Logic AI (also written RichLogic AI) is a personal-finance planning service operated by DealToClose Pvt. Ltd. This policy covers our public website, web app, Android app, support communications and related services. DealToClose is responsible for the processing described here. It does not cover a bank, sign-in provider or other third party's separate service or privacy policy.
Our legal and privacy contact is Contact@DealToClose.AI. Our postal address appears at the end of this policy. Please read this policy before creating an account or enabling optional features.
2. The most important distinction
Rich Logic AI is not an entirely offline app. Account information, household membership, transactions you save, envelopes, budgets, reports and AI chat history are synchronized through our cloud service so they can be available on web and mobile to authorized household members. Optional Android financial-SMS capture is different: new raw message bodies and unconfirmed capture drafts are processed and stored on the phone, not uploaded to our servers. A structured transaction enters the cloud only after you review and confirm it.
When you choose to use the AI Assistant or upload a document for extraction, relevant information is sent to an external AI provider. We do not sell personal or financial information or use transaction content for targeted advertising.
3. Information we access, collect and create
The categories below depend on the features you use. We do not require every optional field from every user.
- Identity and account: email address, name, optional phone or profile details, authentication provider, session and account identifiers, and support or deletion requests.
- Household and permissions: household name, membership, invitations, roles, audit history and settings. Other authorized members can see information shared in that household according to their role.
- Financial records: accounts and optional account/card last-four digits, payees, titles, transaction amounts and dates, categories, envelopes, allocations, budgets, goals, loans, notes, imports and reports you create or confirm. We do not directly connect to your bank or obtain your banking password.
- AI interactions: the questions you ask, limited conversation history, generated replies, selected household context and any file you choose to submit for extraction. Confirmed extracted fields may become part of your financial records.
- Device and service operation: app version, device or browser type, IP address, session identifiers, request times, security events and technical errors needed to operate, protect and troubleshoot the Service. We do not use your SMS text or transaction amounts as advertising analytics.
- Communications: messages you send us, account and security emails, delivery status, and any optional notification preferences.
4. Why we use this information
Where law requires consent, we seek it before the relevant processing. Optional SMS capture is separately opt-in; declining it does not prevent manual transaction entry. You can stop using optional AI features without losing the core planning tools.
- Provide sign-in, household access, cloud synchronization, offline retry, transaction entry, envelope planning, reports, exports and customer support.
- Process optional SMS alerts locally into reviewable drafts and, only if you confirm, synchronize the resulting structured transaction.
- Answer your AI questions and extract proposed transactions from files you deliberately submit, without allowing the AI to post an unreviewed transaction.
- Protect accounts and households, detect misuse, investigate errors, maintain accurate audit trails, deliver essential service communications and meet legal obligations.
- Improve reliability using technical information that should not contain raw SMS, uploaded document bodies, payees, amounts or AI conversation text in ordinary product analytics.
5. Android SMS permission and on-device handling
Financial-SMS capture is off by default. If you turn it on, Android asks for RECEIVE_SMS permission so the app can examine new incoming transaction alerts. The current app does not ask for permission to send SMS, change your messages or read the entire historical inbox for this feature. It attempts to reject obvious OTP and non-financial messages. We cannot guarantee every message will be classified perfectly.
Potential financial messages are held temporarily in an Android-Keystore-protected queue and parsed into encrypted local drafts. Raw bodies are not sent to our server, OpenRouter, the web app, email or analytics. The app may use an account's last four digits and your own confirmed history to suggest a destination. You review and can change the payee, account, category, amount, date and other details before saving. Confirmed structured transactions synchronize to your household and may then appear on web and on other members' devices. Dismissed or confirmed local drafts are removed from the local capture queue. Turning capture off or signing out clears the pending local capture data described in the app.
A former version of the service included a raw-financial-SMS upload path. That path is disabled for new uploads, but any historical raw-message records that were already uploaded have not been silently erased. If such records exist for your account, contact us to request access or deletion. We will verify and handle the request under the retention and deletion section below.
6. AI Assistant, files and generated results
The AI Assistant runs through our authenticated server and OpenRouter, which may route a request to the model provider selected for that request. A question may include your prompt, recent chat context and relevant data from the household you are authorized to use. When you choose to upload a supported receipt, image, PDF, spreadsheet or document, that file is transmitted to the extraction provider. The current extraction route holds the upload in request memory rather than placing the original file in a public storage bucket. Your chat messages and generated replies are stored in the cloud so you can revisit them; you can clear or delete eligible conversations in the app.
Our current AI requests ask for zero-data-retention routing and deny provider data collection. That setting is not a guarantee about every downstream provider or legal retention obligation; their processing is governed by their actual terms and technical controls. We do not send raw Android SMS to AI. Do not submit confidential third-party material you are not entitled to process. AI may invent or misread information: every extracted transaction is a draft that requires your review and confirmation before it is recorded.
7. Where information is stored and who can see it
Cloud account and household records are stored through our service providers and protected by authenticated access and household-scoped database permissions. Your signed-in Android app also keeps an encrypted local cache and offline transaction outbox so certain features can work without a connection. Uninstalling the Android app removes its local app storage, but does not delete the cloud account or records that have already synchronized. Likewise, signing out of a device does not by itself delete the cloud account.
Household Owners, Editors and Viewers have different capabilities. Members with permitted access can see shared records, including financial details, so invite only people you trust. AI chats are intended to be private to the signed-in user within the household. Support personnel should access user data only when necessary and authorized for support, security or legal purposes.
9. Security and permissions
We use transport encryption, account authentication, household-scoped authorization and restricted server credentials. On Android, supported offline data and local capture drafts are encrypted at rest; device security and optional biometric lock add protections. These measures reduce risk but cannot eliminate it. Protect your device and password, sign out of shared devices, and contact us promptly if you suspect unauthorized access.
The app does not require camera, microphone, contacts or location permission for SMS capture. You may select an existing image or document through the device's file picker for AI extraction. Android notification and biometric capabilities, if used, have their own device controls. Permission availability can vary by app version and platform.
10. Retention and deletion
We retain account and household data while needed to provide an active account and requested features. We retain service, audit and security records only as needed for integrity, misuse prevention, disputes or law. A transaction deletion may leave a reversal and audit trail so the ledger remains accurate. Local unconfirmed SMS capture data is removed when dismissed, confirmed, capture is disabled, or the signed-in session is cleared, as applicable. Uninstalling removes local app storage but not synchronized cloud data.
You can request account deletion in app Settings or from our public Account Deletion page at richlogicai.com/delete-account. That starts a protected request; it is not an instant erase button. We verify the requester, review shared-household ownership and delete or de-identify associated data and ask processors to do likewise, except limited records we must retain for legitimate legal, security, fraud-prevention or dispute reasons. We will explain any retained categories when responding. The current product has a request queue, not a fully verified automated end-to-end deletion worker; operational processing must be completed before a Play release. Historic raw-SMS rows, if any, are included in this review rather than presumed absent.
We do not promise a fixed retention or deletion number of days that our present systems cannot verify. We will respond to verified requests and complete them without undue delay, subject to applicable law and justified exceptions.
11. Your controls and privacy requests
You can edit many account and financial fields, use manual entry instead of SMS, turn off optional SMS capture, stop submitting AI requests, clear or delete eligible chats, export a household snapshot and submit an account-deletion request. You may also ask us for access, correction, withdrawal of optional consent, erasure or a response to a grievance by emailing Contact@DealToClose.AI from your account address. We may verify your identity and take account of the rights of other household members and legal obligations. Withdrawing a permission stops future processing for that feature; it does not automatically undo a transaction you already confirmed.
The web service uses authentication and security cookies or comparable session storage. We do not use financial transaction content for advertising cookies. Your browser may let you block cookies, but essential sign-in functions may then fail.
12. Children
Rich Logic AI is intended for adults, not directed to children. We do not knowingly invite children to create accounts. If you believe a child has supplied us information, contact us so we can investigate and take appropriate action.
13. Changes, questions and complaints
We may revise this policy when our features, providers or legal obligations change. We will update the date above and provide additional notice for material changes when required. For questions, access or deletion requests, or a privacy complaint, email Contact@DealToClose.AI. You may also write to DealToClose Pvt. Ltd. at 223, Shree Punjan Plaza, Beside Limbayat Zone Office, Parvat Patiya, Surat, Gujarat 395001, India. We will review your request in accordance with applicable law.
Contact DealToClose
For questions about this document or the Service, email Contact@DealToClose.AI or write to 223, Shree Punjan Plaza, Beside Limbayat Zone Office, Parvat Patiya, Surat, Gujarat 395001, India.