Spendarc.ai
Spendarc.ai · Legal & support

Privacy Policy

How Spendarc.ai collects, uses, protects and deletes your information, including financial records, optional capture features and AI assistance.

Who we are and how to contact us

Last updated: October 7, 2026. This Privacy Policy covers the Spendarc.ai mobile app, its supporting services and these public support pages. Spendarc.ai is operated by Tyfora.

For privacy questions, access or correction requests, deletion requests or complaints, email info@tyfora.com or call +1 (832) 865-0076. Please identify Spendarc.ai in your message. Do not send passwords, verification codes or full bank credentials.

You can request account and data deletion without installing or signing into the app.

At a glance

  • We process the account details and financial information you provide to deliver expense tracking, budgets, goals, reminders and related features.
  • Camera, photo selection, voice entry, notifications and biometric sign-in are optional. Manual entry remains available without camera or microphone access.
  • The current Android app does not read your SMS inbox, receive background SMS or automatically import bank SMS.
  • AI processing may involve a configured service provider. Review suggestions before saving; a suggestion is not a completed payment.
  • We do not sell your personal financial information or use it for targeted advertising. The app does not include an advertising SDK.
  • Signing out or uninstalling does not delete your server account. Use the deletion options below.

Account, profile and security information

We collect your name, email address, password and account identifier when you register or use account services. We process country, currency, language and other preferences you select. Country selection is a preference, not GPS location tracking. An optional cropped profile photo is saved with your account settings.

We store password hashes rather than readable passwords. Verification and recovery flows process email addresses, expiring verification challenges, attempt counts and delivery status. Email-change requests also process the proposed new address and may send a security notice to your previous address. Session credentials, session/device information and security events support sign-in, session management and abuse prevention.

The introductory onboarding stores a completion preference on your device. It does not itself create a financial account or authorize microphone, camera or notification access.

Financial records and information you provide

Depending on the features you use, we process:

  • Income and expenses, amounts, currencies, dates, categories, merchant names, notes, payment-account labels and recorded balances.
  • Budgets, savings goals, subscriptions, recurring commitments, instalments, committee contributions, planned payments and reminder preferences.
  • Hisaab records, including names you enter for people, money owed or receivable, repayments and settlement history.
  • Household invitations, member names and email addresses, shared expenses, splits, settlements and attachments you supply.
  • Imported statement information, financial reports, tax-planning inputs and documents you choose to upload.
  • Smart Add text, speech transcripts, receipt text, drafts, corrections, confirmations, questions and feedback.

Records and pending changes may be stored on your device and synchronized with our servers. Unfinished Smart Add drafts can be saved before you confirm a transaction. Removing a draft from view or starting a new capture is not necessarily a request to erase its stored data.

Spendarc.ai records financial information; recording a transfer, debt or payment does not move money or give us access to your bank account. Do not submit bank passwords, card security codes or verification codes. Names entered for Hisaab do not give the app permission to read your address book.

Receipt photos, screenshots and imported files

When you use the receipt scanner, the selected or captured image is uploaded to the Spendarc.ai server for text recognition (OCR). The current server processes receipt-image bytes for the request and does not intentionally maintain an archive of original receipt images. In the on-device Smart Add image flow, Google ML Kit extracts text locally and the extracted text is submitted for interpretation. These are different capture paths.

Receipt text may contain merchant information, purchased items, totals, dates, tax amounts and any personal details visible in your image. Extracted text, proposed entries and corrections can be retained as drafts and financial records. Crop out information you do not want processed. Original receipt images are not sent to an external language model by the current OCR path; extracted text may be used by configured interpretation services.

Selected-photo access uses the system picker rather than permission to browse your entire library. Temporary app copies are removed during normal cleanup; an interrupted session may leave temporary copies until later cleanup or app-data removal. We do not delete the original photo from your gallery.

If you import a statement or another supported file, its extracted content is used to prepare records for review. Exported reports and files you share are handled by the destination or app you choose.

Voice entry and biometric sign-in

Voice entry starts when you choose it and grant microphone permission. Your device’s speech-recognition service processes speech and may send audio to its provider depending on the device, service and settings. Spendarc.ai uses the recognized text to prepare your entry and submits that text for processing. The current app does not send a separate audio recording to Spendarc.ai or operate an always-listening microphone. You can type instead and revoke microphone permission in device settings.

Biometric sign-in is handled by the operating system. Spendarc.ai receives the authentication result, not your fingerprint, face image or biometric template. Protected session credentials may be retained on the device when you enable biometric sign-in. You can disable it through the app’s security controls.

AI assistance, personalization and improvement

Spendarc.ai uses deterministic calculations, category rules and available models to interpret entries and explain recorded finances. Some features run on our servers or private model infrastructure. If a configured external interpretation service is enabled, it may receive the capture text, currency, local date and input source needed to interpret your entry.

Optional OpenAI-backed financial assistance can send your financial question and a limited selection of relevant financial facts to OpenAI. When the deployed Smart Add fallback permits external AI interpretation, unresolved entry text and its context may also be sent to the enabled provider, including OpenAI. Text you type or extract from a receipt can itself contain personal information. We do not send your password or session credentials as model context.

AI results, answer history, feedback, cached responses and request metadata, such as provider, processing status, usage and timing, may be stored to deliver the feature, troubleshoot failures and control service usage. Our OpenAI adapter requests that responses are not stored through the response-storage option; this does not mean all provider-side records have zero retention. Provider handling depends on the service and applicable configuration.

Optional personalization uses your records and interactions to identify recurring activity, category patterns and suggestions. Manage it using the personalization controls in Privacy & account. Disabling personalization does not delete your underlying transactions or necessarily disable separately available AI features.

Our separate global-improvement collection requires a specific opt-in when offered and enabled. The implemented collection selects synthetic examples from explicit feedback; it does not copy your private transaction amounts, names or original text into those global examples. The optional analytics preference is not training consent. Ask support about withdrawing an existing improvement opt-in if the control is unavailable in your app version.

AI and OCR can make mistakes. Review titles, amounts, categories, dates and account choices before confirming. Do not include secrets or unrelated sensitive information in financial questions.

Households, Hisaab and sharing with other people

Authorized household members can see the information needed for the shared ledger, including member identities, shared transactions, split amounts and settlement history. Household information is not a public profile. Your personal ledger is not automatically made visible to every household member.

When you invite someone, we process the invitation details and email address you provide. Enter or share another person’s information only when you have authority to do so. Other members may retain historical shared records and files they exported. Leaving a household does not automatically erase its historical ledger.

Personal Hisaab records and household records are separate workflows. If you export or share information, the recipient and the selected sharing service receive that information under their own practices.

Tax-planning documents

If you use the optional tax-document feature, uploaded documents and extracted fields can include sensitive income, employment, withholding, identification and other financial information. Uploaded document content is encrypted on the server using a server-managed key; authorized server processing can decrypt it. This is not end-to-end encryption.

A configured document-extraction service may process the document or extracted information for this feature. Saved documents and linked tax evidence follow their account and record lifecycle, not the receipt-image processing lifecycle. The self-service document flow may require linked evidence references to be removed before an upload can be deleted. Contact support if you cannot remove a document.

Permissions, notifications and device information

  • Camera: optional receipt capture and supported profile-photo capture.
  • Selected photos/files: the items you choose for receipts, profile images or imports; no broad gallery access is required by the current Android manifest.
  • Microphone: user-started voice entry through the device speech service.
  • Notifications: reminders and financial activity alerts. Local scheduling and, where enabled, Google Firebase Cloud Messaging use delivery information and device registration tokens. Notification content may be visible on your lock screen; choose private notification content where offered or adjust device settings.
  • Biometric authentication: optional operating-system authentication.
  • Boot events: restore scheduled local reminders after an Android restart.
  • Network access: account services, synchronization, selected uploads and optional online features.

The current Android app does not request SMS access, contacts access, precise location or unrestricted external-storage access. You can revoke optional permissions in device settings; the corresponding optional feature may stop working. Permission withdrawal does not erase already-saved records.

Requests expose an IP address, request time and network/device metadata to our service and hosting infrastructure. We process session and delivery identifiers, error information and security events for operation and protection of the service. The Optional analytics setting stores your preference; the current app does not include a separate product-analytics SDK. Essential security logs and operational request metadata are separate from optional analytics.

Why we process data and who receives it

We process information to create and secure accounts, verify email ownership, synchronize records, calculate summaries, interpret entries, extract document text, provide reminders and requested insights, manage shared ledgers, answer support requests, prevent abuse and meet applicable obligations.

  • Hosting and database providers: host records, run the service, deliver network requests and maintain operational systems.
  • Email delivery providers: the configured SMTP provider (such as Yandex SMTP) or EmailJS and its delivery service receive recipient addresses and message content needed for verification, recovery and security notices. Codes and expiry details are part of those messages.
  • Google/Firebase and device services: process push registration and delivery information or speech-service information as described above. ML Kit text recognition in the local capture path runs on the device.
  • AI and document service providers: receive the bounded input needed for enabled processing, as described in the AI and tax sections.
  • People and apps you choose: authorized household members and recipients of invitations, reports or exports.

Authorized support and operations personnel may access information needed to resolve a request, maintain the service or investigate abuse. We may disclose information where required by law or to protect users, legal rights and service security. We do not sell personal financial information or use it for targeted advertising.

Hosting, email and optional processing services may operate in countries other than yours. Your selected currency or country does not select a storage region. Contact info@tyfora.com for the active providers, processing locations and applicable transfer arrangements.

Storage and security

Release app connections use HTTPS. We use account-based access controls, password hashing, protected session storage and an encrypted local financial database. Some preferences, temporary files and exported documents are stored separately and are not covered by the database encryption. Android app backup is disabled for app data.

Server processing requires access to relevant information; the service is not end-to-end encrypted. Access controls and encryption reduce risk but cannot guarantee absolute security. Protect your device, email account and exported reports, and contact support if you suspect unauthorized access.

How long information is retained

  • Account and financial information: retained to provide your account and records until removed or your account is deleted. Some record deletions use synchronization tombstones or revision history and do not immediately erase every stored version.
  • Drafts, extracted text and AI history: saved with the account or related feature. Confirming, dismissing or starting another capture does not automatically erase all prior draft content.
  • Receipt images: processed for OCR without an intentional server receipt-image archive in the current flow. Temporary device copies are cleaned up normally; your original gallery files remain yours.
  • Profile photos and tax uploads: retained with account settings or linked document records until replaced, removed or deleted with the account, subject to shared-record and linked-evidence restrictions.
  • Authentication challenges and caches: validity expires according to their purpose. Expiration prevents reuse; it is not a promise that the stored row is physically deleted at that instant.
  • Shared household history: may remain in the shared ledger after a member leaves or deletes an account. Contact us to review removal or anonymization of identifying information.
  • Support correspondence, security logs, backups and provider records: follow their operational retention schedules and any applicable legal obligations. Contact support for the periods applicable to your account and deletion request.

The receipt-retention setting records a preference; it does not currently guarantee scheduled erasure of all receipt text, drafts or transactions. A household attachment preference does not automatically remove shared ledger history. We do not promise immediate erasure from backups, other members’ copies or external providers. Where data is retained for security, fraud prevention or legal obligations, we will explain the relevant data, reason and applicable retention when handling your request.

Your choices, rights and account deletion

Open Settings → Privacy & account to manage available personalization and notification choices, view this policy, export personal data and request permanent account deletion using your password. You can correct records through their editors, remove supported records, revoke device permissions or contact support about data you cannot remove yourself.

Without the app: email info@tyfora.com from your registered address when possible, requesting deletion of your Spendarc.ai account and associated personal data. You do not need to reinstall the app. If you cannot access that address, contact us to arrange ownership verification. See the full account-deletion instructions.

Successful self-service deletion removes the account and associated personal records from the active service and clears account data on the current device. Household ownership, unresolved balances or incomplete shared records can prevent self-service deletion; support provides an alternative request path. Some historical household member details currently remain in shared records. Ask support to review their removal or anonymization as part of your request. Copies on other devices, exported files, backups and provider-held records are handled separately as described above.

Depending on your location, you may have rights to access, correct, export, delete, restrict or object to processing, withdraw optional consent, or complain to a relevant privacy authority. We may need to verify ownership before acting. Signing out, uninstalling, disabling personalization or withdrawing a permission does not itself delete your server account. Email requests are handled by support and do not instantly erase data.

Children and changes to this policy

Spendarc.ai is intended for general personal financial management and is not directed to children under 13. Contact info@tyfora.com if you believe a child has supplied information without appropriate authorization.

These public legal pages do not set application cookies or load advertising or analytics scripts. Hosting infrastructure can still process access and security information.

We revise this policy as practices change and update the date above. Where a change requires additional notice or consent, we will provide it through an appropriate channel. This policy does not replace feature-specific disclosure and consent where required.