Privacy Policy

1. Who we are and what this covers

Walletypes provides expense and income tracking, AI-assisted entry and search, receipts, reminders, budgets, optional bank connections and document storage through its website, mobile apps, Telegram bot and authorized integrations. This policy explains our personal-information practices. Subscription and liability provisions are in our Terms of Service.

Operator: [full legal company name]. Registered in: [US state and country]. Business/contact address: [address]. These details must be completed before this draft is published. Privacy requests and security reports: support@walletypes.com.

2. Information we collect and its sources

From you and your sign-in provider: name, email address, profile image, provider identifiers, and Telegram ID or username where applicable. From your use of the service: currencies, languages, timezone, notification settings, session and API-token records, IP address, browser/device information and security or error logs.

From your entries and uploads: spending and income, merchants, amounts, currencies, dates, categories, tags, notes, budgets, expected money, recurring records, reminders, conversations, AI actions, voice recordings and transcripts, receipt images, PDFs, screenshots, CSV imports, extracted text and derived search representations. Content may include information about other people.

If you use document storage: uploaded files and previews, names, document numbers, issuers, dates, extracted text, summaries, fields and search indexes. Identity, financial and medical documents may contain sensitive information. Upload only material you have the right to provide and only what is necessary. This is not a service for healthcare providers to store regulated patient records.

If you connect a bank: Plaid and your institution provide account identifiers, names, types, masked account numbers, transaction amounts, dates, merchants, locations and categories. We retain an encrypted connection token and synchronization records. Bank sign-in is handled through Plaid or your institution; do not send us bank passwords.

From Stripe: customer and subscription identifiers, selected plan, currency, billing interval, payment status and billing dates. Card details are collected by Stripe at checkout; our application does not store full payment-card numbers or security codes.

3. Mobile permissions, automatic entries and location

Microphone, camera and photo access let you submit voice notes and selected files. Optional device authentication uses your operating system; we do not receive fingerprint or facial templates. Push registration supplies a push token, device name and platform. Notifications may contain financial or document details and may appear on your lock screen.

If you enable automatic entries, Android notification access can inspect notifications on your device. The app filters the enabled SMS, Google Wallet or selected bank-app sources and forwards matching payment-related text to our server for AI processing. Filtering may capture unrelated or sensitive text. App names may be kept locally to help you choose sources. On iPhone, user-configured Siri, Shortcuts and payment automations send the text or payment fields you configure. Disable sources in Settings and revoke device permissions to stop future collection; this does not erase previously saved entries.

Location is optional for device-based lookup. The app may use device coordinates to resolve a city, country and area; area information can include a district, street or place name. Web lookup sends coordinates to BigDataCloud; a Telegram location share is sent to our server and Nominatim/OpenStreetMap for resolution. Mobile lookup uses operating-system geocoding. We save resolved place information rather than a dedicated GPS-coordinate history, but coordinates or addresses you put in uploads or messages can remain in that content.

We may also infer a place from timezone or send your IP address to ipapi.co for approximate city/country lookup. Denying device location permission does not prevent this IP-based lookup. You can decline location access and omit location from your content.

4. Why we use information

We use information to authenticate you, maintain your records, import and categorize entries, answer your questions, search documents, synchronize integrations, deliver reminders, process subscriptions, provide support, prevent abuse, diagnose failures and meet legal obligations.

Corrections can improve your own future suggestions. Merchant, city and standard-category votes with a hashed account identifier may contribute to shared categorization; other users do not receive your individual payment amounts or documents. A hashed identifier is pseudonymous, not a promise of anonymity.

Where applicable law requires a legal basis, core account and service processing is necessary to perform our contract; security, diagnostics and limited improvement rely on legitimate interests subject to your rights; legally required recordkeeping relies on legal obligations; optional processing that requires consent relies on that consent. Device permission alone is not consent to every legal purpose. Sensitive-data processing requires the additional authorization or legal condition required by your location.

We do not sell personal information, share it for cross-context behavioral advertising, or use your financial records to target advertisements.

5. AI processing and sensitive content

Depending on the deployed configuration, OpenAI or Google Gemini processes messages, relevant record context, images, PDFs and document pages to extract, categorize, summarize or answer questions. Voice may be processed by Google Cloud Speech-to-Text or the configured AI provider. Search embeddings are derived from relevant text. Uploaded documents can be decrypted on our server and sent to AI for extraction.

This is not end-to-end encrypted storage: the service can process readable content and extracted text. AI providers process submitted content under the terms of the account and service we use, including their applicable retention and security practices. We do not promise zero provider retention or that every provider configuration excludes model training. Avoid unnecessary sensitive information. AI can make mistakes; review results. These features do not make legal or similarly significant decisions about you.

6. Providers and other disclosures

We use Cloudflare R2 or configured storage for files and backups, our hosting/database providers for records and logs, OpenAI/Google for AI and speech, Stripe for billing, Plaid for optional bank connectivity, Resend for email, Telegram for bot messages, and Expo together with Apple/Google or browser push services for notifications. BigDataCloud, Nominatim/OpenStreetMap and ipapi.co support location lookups. Only providers needed for the enabled feature receive the relevant information. Mobile push and email providers can process message content; Telegram bot messages are not end-to-end encrypted.

Authorized personnel may access information as needed for support, maintenance, security or legal obligations. We may disclose information to professional advisers, to comply with valid legal process, protect rights or investigate abuse, and in a merger, financing or sale subject to applicable safeguards and notice requirements. A successor must handle information consistently with applicable law; a material new use requires the notice or consent the law requires.

7. Where information is processed

Our operator and providers may process information in the United States and other countries, whose laws may differ from yours. Registration in the US does not mean every database, file or AI request stays in the US. Where cross-border transfer rules apply, required safeguards must be in place, such as appropriate contractual safeguards or a recognized adequacy mechanism. Contact us for details applicable to your data. This policy is not a waiver of transfer protections.

8. Retention, account closure and deletion

Account records, financial entries, receipts, imports, documents and settings are generally retained while your account remains open. Feed conversations, agent-run history and voice-note records/recordings have a 30-day retention window; information copied into a transaction, import or document has that record’s longer lifetime.

Closing an account deactivates it and revokes its sign-in sessions. There is a 30-day recovery period: signing in during it can restore the account. After that period, the account is scheduled for deletion. If you need erasure without recovery, contact us; we will assess and handle your request under applicable law.

Backup copies rotate separately: the configured local database-backup window is about 7 days and offsite copies up to 90 days. Deleted information may remain in restricted backup copies until rotation; backups are used for recovery, and deletion must be reapplied after restoration.

We may retain limited billing, tax, security or dispute information for applicable legal obligations, fraud prevention or claims, rather than retain all uploaded content for those purposes. Retention depends on the requirement or claim involved. Provider-held information follows applicable contracts and the provider’s legal duties. Disconnecting an integration, deleting an entry or cancelling a subscription is different from deleting an account; imported entries can remain after a bank is disconnected.

9. Cookies, local storage and visit statistics

We use essential authentication cookies and browser/device storage for preferences, credentials, app-lock settings and enabled features. Self-hosted Umami, when enabled, counts visits, page types, referrers, approximate place and device/browser characteristics without analytics cookies. Query strings and URL fragments are excluded; transaction and recurring-payment identifiers are masked. The analytics service receives network requests but is designed not to retain raw IP addresses. It is configured to respect Do Not Track.

We do not use advertising trackers. Global Privacy Control signals apply to rights such as opting out of sale or advertising sharing where required; we do not conduct those activities. Other providers’ pages, such as Stripe or Plaid, have their own storage and privacy practices.

10. Security and incidents

Security is a priority. We use reasonable safeguards appropriate to the information and risks, including encrypted production connections, authentication and account ownership checks, restricted file access, encryption of stored document files and bank-connection tokens, and device credential protection where supported. Document files are encrypted separately from extracted database text. These measures do not mean every database field or backup is separately encrypted or that storage is end-to-end encrypted.

No system can guarantee absolute security, uninterrupted availability or freedom from loss. If we discover a personal-data incident, we will investigate, take appropriate containment and remediation steps, and notify affected people and authorities when and as required by applicable law. Nothing here excuses failures to meet our legal security duties or removes statutory remedies. Protect your sign-in account and devices, limit notification previews and keep separate copies of important records.

11. Your choices and privacy rights

You can edit records, export transactions as CSV, delete supported content, disconnect a bank, revoke integration/API tokens, change notification settings and revoke device permissions. A transaction CSV is not a complete copy of all personal information, uploaded documents or voice files.

Email support@walletypes.com for access, a copy of personal information, correction, deletion or other rights. Depending on your location and applicable law, rights may include portability, restriction, objection, withdrawal of consent, limits on sensitive-data processing, authorized-agent requests, and appeal of a denied request. Withdrawal does not invalidate earlier lawful processing. We may verify identity and agent authority, request only necessary information, explain lawful exceptions, and respond within the applicable deadline.

We do not discriminate for exercising protected privacy rights. If a request is denied, reply to the decision to request an appeal where available. You may complain to your competent privacy authority or state regulator. California and other state privacy rights depend on the relevant law’s coverage; we do not claim that all statutes apply to every user or business.

12. Children

Walletypes is intended for adults aged 18 or older and is not directed to children. We do not knowingly collect children’s personal information. If you believe a child has provided it, contact us so we can investigate and take appropriate deletion measures.

13. Policy changes and contact

We will publish the updated policy and revision date. For material changes we will provide notice before they take effect, using the app or an available contact address. Where law requires consent for a new purpose or sensitive processing, we will obtain it; continued use alone does not replace that consent. Contact support@walletypes.com for questions or security concerns.