1. Who we are and what this covers
Sanchay is provided by Idrish Khan. This policy describes the Sanchay mobile app, this website, and support correspondence. Contact idrish011@gmail.com with privacy questions.
The mobile app works without a hosted Sanchay account or a bank login. Core financial record keeping works offline. Financial records are local; advertising, consent, store purchases, and some third-party SDK functions can connect to the internet. The website and mobile app have different data practices.
2. Your accounts and financial records
Sanchay processes the accounts, balances, transactions, payees, categories, notes, budgets, and settings you enter or choose to import. It uses them to display your records, calculate account and budget summaries, and provide the features you request.
Saved financial records and saved insight conversations are stored in a local SQLCipher-encrypted database. A randomly generated key is stored through platform secure storage: iOS Keychain or Android Keystore-backed storage. Sanchay does not operate a first-party server that receives or synchronizes this database. Financial amounts can also be hidden using the Home visibility control.
Preferences may use separate app or secure platform storage. Not every temporary file is a SQLCipher database record. Device encryption, permissions, operating-system backups, keyboards, and other software have their own behavior. Protect your device and its access credentials.
3. Receipts, messages, and optional permissions
Choosing a camera or photo-library action lets Sanchay read the image you select and perform receipt text recognition with Google ML Kit on the device. Suggested details are a draft: you review and confirm them before they become financial records. You can use manual entry without camera or photo access.
Receipt images are staged in separate app-private temporary files. On iOS these use file protection and backup exclusion. The app attempts cleanup after save, cancel, replacement, or leaving receipt review, with stale-file cleanup on restart or a later scan. Cleanup failures may be retried. Originals in Photos or another provider are not deleted.
Explicitly pasted or shared transaction SMS or email text is parsed locally into a draft. The app does not connect to a mailbox or request a bank login. Standard release builds do not scan the Android SMS inbox, and iOS Messages history is not read. The iOS share extension temporarily holds one item in a protected App Group container until it is processed, dismissed, or replaced. Raw text is not saved in the transaction database; a derived fingerprint helps identify duplicate imports.
The current app has no system-assistant voice-entry feature. Device-level dictation, keyboards, or accessibility services you choose are separate from Sanchay. Manage camera, photo, and system permissions in your device settings.
4. Optional on-device AI
After the in-app disclosure and your choice to use Insights, Sanchay supplies your question and a limited context from recent transactions to the system model. Apple Foundation Models is used on compatible iOS devices; AICore / Gemini Nano is used on compatible Android devices. Saved questions and responses stay in the encrypted local database.
The current context builder limits the data to at most 50 recent transactions and 7,200 serialized characters, using dates, amounts, currency, payees, categories, and transaction classifications. Raw receipt text and database identifiers are excluded from that context. Sanchay does not fall back to a cloud AI service when the local model is unavailable.
AI availability depends on hardware, OS, language, region, settings, and model readiness. The operating-system provider manages system models and their downloads or updates. Google states that ML Kit inputs and outputs remain on-device, but technical API performance and utilization metrics can be sent to Google. AI and OCR output can be incorrect; review it before acting.
5. Advertising, consent, and technical information
The Free plan can show Google AdMob ads. The app includes Meta Audience Network mediation; serving through Meta depends on the live partner configuration and availability. Sanchay checks Google User Messaging Platform consent status before requesting ads and provides an in-app Privacy choices entry when required by the provider.
Depending on the SDK, configuration, choices, and device permissions, providers may process IP addresses, IP-derived approximate location, device and advertising identifiers, ad requests and interactions, app interactions, crash information, and performance information. Purposes include ad delivery, measurement, fraud prevention, and operation of the services. Non-personalized ads are not automatically anonymous or consent-free.
Sanchay does not add financial records, receipt text, AI prompts, or AI responses to ad-targeting requests. Pro suppresses app ad requests and display. It does not disable purchase services or all non-ad SDK communication. Optional local ad diagnostics are disabled by default and exclude financial content.
Advertising consent and Apple’s tracking permission are distinct. This website cannot change the mobile SDK’s consent. Use the app’s Settings → Privacy choices entry where available and any relevant system controls. See the linked guide for local record deletion and provider requests.
6. Store purchases
Apple or Google Play processes store purchases and purchase restoration. Sanchay receives purchase status and transaction information needed to grant the Pro entitlement. It does not receive your payment-card number. A local entitlement cache allows the app to preserve its known purchase state while offline; changes such as refunds or revocations may appear after store updates.
On iOS, Sanchay checks purchase entitlements through StoreKit. On Android, Sanchay uses Google Play Billing to obtain purchase and restoration status. Store providers handle their records under their own policies.
7. Backups and files you choose to share
You can create a portable password-encrypted backup and choose its destination using the system document picker. The backup contains logical financial records, not the device-bound SQLCipher key. Sanchay does not retain the password or a server copy. A selected cloud or document provider may synchronize the exported file under its own policies.
The app configures the financial database to be excluded from ordinary operating-system backups; iOS shared-import files also have backup exclusion. There is no automatic first-party cloud backup or sync. Safely keep an encrypted Sanchay backup before changing devices or removing the app.
Restoring a backup replaces the current local dataset after confirmation. Back up any current records you want to keep before restoring. Sanchay cannot recover a lost backup password or remotely reconstruct a database whose required key is unavailable.
8. This website and support email
This website serves static pages, images, and locally bundled fonts. Its code includes no analytics, ad tags, Meta Pixel, session replay, fingerprinting, contact form, remote fonts, or automatic third-party embeds. It does not set cookies or use persistent browser storage. Clicking an external link opens a service that follows its own practices.
The website is hosted by Render. Hosting services process request and security data, which can include IP address, requested URL, browser information, timestamps, and errors. Retention: Render retains provider-held information under its privacy policy and applicable service settings. Sanchay does not set a separate fixed retention period for Render’s operational records.
If you email idrish011@gmail.com, Idrish Khan and the email provider process your address, message, and any attachments to answer your request. The configured mailbox uses Gmail. Please do not send statements, card details, bank passwords, database keys, backup passwords, or unredacted financial records. Support correspondence retention: As needed to respond, handle follow-up, and meet applicable recordkeeping obligations.
9. Data handling at a glance
This table separates local financial content from technical information handled by service providers. Provider retention is governed by the relevant service and its actual configuration; no fixed provider retention period is asserted here.
| Data | Source | Purpose | Location / recipient | Retention | User control |
|---|---|---|---|---|---|
| Financial records & budgets | Your entries and confirmed imports | Ledger, summaries, budgets | Encrypted local SQLCipher database | Until local removal or confirmed dataset replacement | Edit/delete records; create encrypted backup |
| Receipt images & OCR text | Camera or photo you select | Prepare a reviewed transaction draft | On-device ML Kit; separate temporary image files | Staged copies cleaned after review; retries on failure | Skip scanning; revoke permission; manage originals separately |
| Shared message text | Explicit paste or share action | Prepare an editable transaction; duplicate detection | Local parser; iOS pending item in App Group; derived fingerprint in database | Pending item until processed, dismissed, or replaced | Review/discard draft; delete saved transaction |
| AI context & history | Your question and recent local records | Optional on-device Insights | System model; saved history in encrypted local database | Saved history until local deletion | Skip AI; delete a conversation or clear history |
| Settings & database key | App choices and locally generated key | Preferences, visibility, unlock local database | App / platform secure storage | Varies by value and OS; Keychain may persist | Change settings; protect device; manage OS data |
| Ad & consent data | SDK and device/request information | Consent, ads, measurement, fraud prevention | Google AdMob / UMP; configured Meta partners | Provider practices and configuration | In-app Privacy choices; system permissions; Pro removes app ads |
| Technical SDK metrics | ML Kit usage and performance | Operate, maintain, and improve SDKs | Google; optional local diagnostics | Provider practices | Avoid optional scanning/AI; review provider controls |
| Purchase status | App store transaction / restoration | Grant and reconcile Pro access | Apple / Google Play; local entitlement cache | Store practices; local cache until updated or removed | Restore purchase; contact store for purchase records |
| Encrypted backups | Your explicit backup action | Recovery and device transfer | Destination you select, including cloud providers | Until you remove all saved copies | Choose destination; retain password; delete copies separately |
| Website requests & support | Browser requests; email you send | Serve pages, security, answer support | Render for website requests; operator and Gmail for email | Render provider practices; support retention as described above | Avoid sensitive attachments; contact operator about correspondence |
10. Retention, deletion, and your choices
Financial records and saved conversations remain locally until removed with available app controls, replaced by a confirmed restore, or removed with the app’s data. You can delete individual transactions and clear saved Insights history. These controls do not delete previously exported backups, original receipt images, or records held by other providers.
Removing an iOS app can leave Keychain entries behind. A remaining key is not a recoverable copy of the database. Android and device-transfer behavior can differ by OS and device. Do not assume uninstalling clears all operating-system, store, advertising-provider, cloud-storage, or email records.
There is no hosted Sanchay account to close. Idrish Khan cannot inspect, correct, or remotely erase a database that exists only on your device. To ask about support correspondence or exercise rights available under applicable law, email idrish011@gmail.com. Use the relevant provider’s privacy-request process for records it controls. Sanchay may need information sufficient to identify and respond to your request without collecting unnecessary financial content.
11. Children and international processing
Sanchay is intended for adults aged 18 and over and is not directed to children. If you believe a child has sent personal information to our support address, contact idrish011@gmail.com so we can review the request and delete information where appropriate. The app does not operate a hosted user account or a server containing your financial records.
Advertising, app-store, hosting, email, and any storage providers you choose may process technical or support information in countries other than your own. Their linked privacy policies describe their processing and safeguards. Sanchay does not upload your local financial database to these providers.
12. Security, updates, and contact
Sanchay uses local database encryption, protected key storage, and password-encrypted backups. No device, application, or storage method guarantees absolute security. Keep your operating system updated and protect both your device and backup password.
When data practices change, the policy will be reviewed and its update date changed. Material changes will be communicated as required by applicable law.