Privacy Policy

1. Who we are

Dooit is a personal finance tracking app built for users in Malaysia, although people in other countries may also use it.

For privacy questions or requests, contact Dooit at [email protected].

2. Waitlist and landing page information

When you join the Dooit waitlist, we collect the email address you submit, a source marker showing that the signup came from the landing page, and anti-spam information submitted with the form.

The waitlist form sends submissions to a Supabase Edge Function for processing and storage.

Our waitlist form uses Cloudflare Turnstile to help confirm that submissions are legitimate. Cloudflare may process verification tokens, browser signals, and similar technical information according to its own service terms and privacy practices.

3. App information you enter

By default, Dooit is local-first. Financial information you enter in the app, such as transactions, amounts, categories, budgets, accounts, notes, preferences, and saved receipt images, is stored on your device unless you choose to use a feature that sends or backs up that information.

Dooit does not connect to bank accounts. You record transactions manually, from receipts you upload, on Android from bank and e-wallet notifications on your device if you grant notification access, or on iPhone (iOS 27 or later) from bank and e-wallet notifications that a Shortcuts automation you set up passes to Dooit (see section 10).

If you contact us for support, we may collect your email address, message contents, and related troubleshooting information.

4. Optional cloud backups

Dooit offers optional point-in-time backups to Google Drive and, on supported Apple devices, the current Apple Account's private iCloud storage. Cloud backup is not live ledger sync and is never enabled merely because a cloud account is available. You must deliberately connect or enroll each provider.

A cloud snapshot may contain the active local owner's backup-eligible finance database, saved transaction and scheduled-payment receipt attachments, profile preferences, and profile avatar. Payment profiles and their device-bound secure values or QR files, authentication credentials, Support tickets and attachments, and backup-control settings are excluded.

Google Drive backups are stored in the Google account you connect. iCloud backups use Apple's private CloudKit database, count against your iCloud quota, and do not appear in the Files app. Apple isolates private CloudKit data by Apple Account; Dooit additionally separates histories by local owner and source-device installation.

Manual backup, browse, restore, and deletion are available without Pro where the provider is supported. Automatic cloud backup is a Pro feature, runs only for the one provider selected on that device and owner, and may be delayed by operating-system scheduling. Restoring replaces the active owner's local ledger rather than merging devices.

Turning off a provider stops future writes but retains its recovery snapshots until you delete them. Dooit provides controls to delete iCloud restore points, device histories, or all iCloud backups for the active local owner. Deleting cloud backups does not erase the active local ledger.

These provider backups use the security supplied by Google Drive or Apple's private CloudKit service. Dooit does not add a separate user-held encryption key or claim that these backups are Dooit-managed end-to-end encrypted.

5. AI features and the third-party AI service we use

Dooit offers four optional features that use artificial intelligence: receipt scan, statement scan (multi-transaction extraction), AI column mapping for file imports, and, on Android and iPhone, AI learning of bank notification formats. Receipt scan, statement scan, and AI column mapping run only when you deliberately start them. Notification format learning runs only after you turn it on, and then only for notifications from supported bank and e-wallet apps that Dooit cannot read yet, when you open the app. None of them reads your transactions, accounts, or files on its own.

The third-party AI service is Google Gemini, operated by Google LLC. Dooit's own server receives your request, forwards the content to the Gemini API, and returns the result to your device. No other AI provider receives your data.

Before anything is sent to Google Gemini for the first time, the app shows an in-app disclosure that names the data being sent and names Google Gemini as the recipient, and it sends nothing unless you agree. You can withdraw that permission at any time in Profile, Preferences, AI and data sharing. While it is off, all AI features stay disabled and nothing is sent. Notification format learning also has its own separate switch in the notification capture settings on Android and in the Bank notifications setup on iPhone.

Receipt scan sends: the receipt image or PDF you selected and the text visible on it (which typically includes merchant, date, totals, line items, taxes and service charges); your category, account, and tag names so the result can be matched to them; your currency and country setting; and any correction prompt you type.

Statement scan sends: the statement image, PDF, or text you selected, including merchant names, dates, amounts, and any account or card labels printed on it; your category, account, and tag names; and your currency and country setting.

AI column mapping sends: the sheet names and column headers of the file you are importing, placeholders that describe each column instead of your real values (for example <amount>, <date>, <text:12>), and currency codes and transaction type labels found in the file. If you separately choose the improved detection option, a small sample of real rows from that file is sent as well, which can include merchant names, descriptions, dates, and amounts.

Notification format learning sends: the title and text of one bank or e-wallet notification that Dooit could not read, after Dooit masks long account, reference, and phone numbers on your device (amounts and merchant or sender names stay visible so the result can be checked), and the bank app's identifier (Dooit uses the Android package name for the same bank on both Android and iPhone). Google Gemini returns a format template, which Dooit stores on your device and uses to read later notifications in that format without sending them again. Dooit's server does not store the notification text and does not write it to logs.

We collect this data only from what you hand to the feature: the image, PDF, text, or file you pick, plus the category, account, tag, currency, and country settings already stored in the app. We use it only to produce the extraction or mapping result you asked for, to show that result to you for review, and to run basic reliability and abuse-prevention checks on the scan service.

Dooit does not use your receipt, statement, or import content to train any Dooit model, and does not sell or rent it. Google processes it as our service provider to return the result. Under the Google Gemini API terms that apply to Dooit's paid API use, Google does not use content submitted through the API to train its models, and Google is bound by confidentiality, security, and data protection commitments comparable to those described in this policy. Google's own handling is also described in Google's privacy policy and Gemini API terms.

Uploaded files are kept only as long as needed to complete the scan and deliver the result. Extraction results are stored on your device; if Pro cloud backup is enabled they follow the backup rules in this policy. Receipt images may be saved on your device, and are backed up only if you opt in to receipt image backup.

6. Accounts and sign-in

If you create an account or enable cloud features, Dooit uses Supabase Auth to provide authentication and account management.

Dooit may support Apple Sign in and Google Sign-In. Depending on the provider and your settings, we may receive account identifiers such as your name, email address, or provider user ID.

You are able to delete your account and associated cloud data in the app. You may also contact us for help with privacy requests.

7. Support requests

When you submit an authenticated Support request, Dooit stores the ticket messages and any images you deliberately attach, associates them with your account, and records public lifecycle updates and private administrative audit events.

Support includes a limited diagnostic snapshot: app and build version, platform and operating system, device model, locale, timezone, account identifier, subscription state, and the source screen. It does not collect your finance records, receipt contents, passwords, authentication tokens, or app logs for this purpose.

Supabase provides database and private image storage for Support. Resend may process transactional staff email alerts, and Apple or Google notification services may process user push notifications. Support images are private and made available through short-lived authorized links.

Closed Support tickets and their messages, events, and attachments are normally retained for 24 months after closure. Account deletion schedules associated Support data for deletion within 30 days unless a narrow legal or billing hold applies. Support may permanently redact sensitive messages or images while preserving a non-sensitive record that redaction occurred.

If you cannot sign in, you may use the emergency support email shown in the app. Email sent through that fallback is not automatically added to the authenticated ticket system.

8. Purchases and subscriptions

Pro purchases are handled through Apple App Store or Google Play in-app purchases. Those stores process payment details under their own terms and privacy practices.

Dooit uses Adapty for subscription entitlement management. Adapty may process purchase receipts, product identifiers, subscription status, app user identifiers, and related subscription lifecycle information needed to unlock and manage Pro access.

Dooit does not need to receive your full payment card details when purchases are handled by Apple or Google.

9. Analytics and diagnostics

Dooit uses privacy-conscious analytics and diagnostics to understand reliability and improve the app.

We use PostHog for analytics events. We do not use PostHog session replay or screen recording.

We do not intentionally send transaction amounts, notes, receipt images, or financial record contents to PostHog for analytics.

You can opt out of analytics in the app.

10. Device permissions and notification capture

Dooit may request camera or photo library access so you can capture or import receipts.

Dooit may request notification permission to send user-controlled reminders, budget alerts, important account or service notices, and product updates about new features and important changes. Dooit does not send promotional push notifications.

When you allow notifications, the app registers with Dooit's server even if you do not have an account. The server stores the device push token issued by Apple or Google, a random identifier for this app install, the platform (iOS or Android), the app language, the app version, whether Product updates is on, and when the app last registered. If you are signed in, the install is also linked to your account so receipt scan and Support notifications reach you; signing out removes that link. This information is used only to deliver service notifications and product updates. To stop product updates, turn off the switch in Profile, Product updates, or turn off notifications for Dooit in your device settings.

On Android, Dooit can capture transactions from bank and e-wallet notifications if you grant notification access. Dooit inspects only notifications from a fixed list of supported financial apps and ignores all others. For notifications it can read, the amount, merchant or sender, card or account suffix or name, and time are saved on your device as a transaction for you to review. A local diagnostic log of notification fields from those apps is kept on your device to help add support, and leaves the device only if you choose to share it. You can revoke notification access at any time in Android Settings.

On iPhone with iOS 27 or later, you can create a Shortcuts automation that runs when a notification arrives from apps you choose and passes that notification's app name, title, subtitle, body, and time to Dooit's Capture Bank Notification action. Dooit cannot read notifications on iPhone by itself and receives only what your automation passes to it. Dooit processes notifications only from a fixed list of supported financial apps, ignores those from other apps as well as one-time passwords, promotions, and login alerts, and saves the transactions it can read on your device for you to review, as described above. A local diagnostic record of each run, with long account, reference, and phone numbers masked, is kept on your device and leaves it only if you choose to share it. The separate Notification Diagnostic action, if you add it to an automation, records the values it receives without masking, on your device only. You can stop capture at any time by turning off or deleting the automation in the Shortcuts app.

If you turn on AI format learning, notifications Dooit cannot read are handled as described in section 5. Separately, you may choose to share learned formats. When you do, Dooit's server stores only the validated format template, which is the notification wording with its variable parts replaced by placeholders such as {amount} and {counterparty}, together with the bank app's package name and app version. It never stores the notification text, amounts, names, or account details. Shared templates are not linked to your account; Dooit keeps only a salted one-way hash of your account identifier to count distinct contributors and to honour withdrawal. Deleting a learned format in the app withdraws your pending contribution. Templates we approve are included in future app versions for all users.

Dooit does not need access to your contacts. You can control app permissions through your device settings.

11. How we use information

We use information to operate Dooit, manage the waitlist, provide app features, maintain accounts, run the AI features described in section 5 (receipt scan, statement scan, AI column mapping, and notification format learning), improve built-in support for bank notification formats using templates you choose to share, manage subscriptions, respond to support requests, prevent spam and abuse, improve reliability, and communicate product updates where you have consented to receive them.

We may use aggregated or de-identified information to understand feature usage and improve Dooit.

12. Sharing information

We do not sell your personal information.

We may share information with service providers that help us operate Dooit, including Supabase, Cloudflare, Resend, Google Gemini, PostHog, Adapty, Apple, and Google. Google Gemini is the only third-party AI service Dooit uses, and it receives content only through the AI features described in section 5, after you agree in the app.

We share personal information with these providers only under contracts that require them to protect it with safeguards at least equivalent to those described in this policy, to use it only to provide their service to Dooit, and not to sell it or use it for their own unrelated purposes.

We may also share information when required by law, to protect Dooit and users, in connection with a business transfer, or with your consent.

13. Marketing communications

We send marketing or product update emails only with consent, such as when you join the waitlist or enable an in-app email preference.

Transactional messages, such as account, support, purchase, security, or service-related messages, may be sent when needed to provide Dooit.

Product update push notifications cover new features and important changes to Dooit. They are on by default once you allow notifications and can be turned off at any time with the switch in Profile, Product updates.

14. Data retention

We keep waitlist emails until you unsubscribe, request deletion, or Dooit no longer needs the waitlist.

We keep account and cloud backup information while your account or cloud sync is active. If you delete your account or request deletion, we delete or anonymize associated information within a reasonable period unless we need to keep it for legal, security, fraud prevention, dispute resolution, or accounting reasons.

Push notification registrations are kept while the app keeps registering. Installs that have not registered for 90 days no longer receive product updates, tokens are removed when Apple or Google reports them as no longer valid, and tokens linked to your account are deleted when you delete your account.

Local app data stored only on your device is controlled by you and may be removed by deleting it in the app or removing the app from your device, subject to your device backup settings.

15. Your choices and rights

You may choose not to join the waitlist, not to create an account, not to enable cloud backup, not to use the AI features, not to back up receipt images, or not to provide optional app information. Some features may not work without the information needed to provide them.

You can decline the in-app AI disclosure, or withdraw your agreement later in Profile, Preferences, AI and data sharing. Receipt scan, statement scan, AI column mapping, and notification format learning then stay off and send nothing to Google Gemini; you can still record and import transactions manually. You can turn off notification format learning or template sharing on their own in the notification capture settings on Android or the Bank notifications setup on iPhone.

You may opt out of analytics in the app, turn off product update notifications with the switch in Profile, Product updates, and manage camera, photo library, and notification permissions through your device settings.

You may contact us to request access, correction, or deletion of personal information, subject to applicable law and technical or legal limits.

16. Security

We use reasonable technical and organizational measures designed to protect information. No method of transmission or storage is completely secure, so we cannot guarantee absolute security.

17. International processing

Dooit and its service providers may process information in Malaysia, the United States, the European Union, and other countries where they operate. Data protection laws may differ by location.

18. Children's privacy

Dooit is not intended for children under 13. If a higher minimum age applies in your country, you must meet that higher age requirement to use Dooit.

If you believe a child has provided personal information to Dooit, contact us so we can review and delete it where appropriate.

19. Changes to this policy

We may update this Privacy Policy from time to time. If changes are material, we will take reasonable steps to notify you, such as updating the date on this page or providing notice in the app.

20. Contact

For privacy questions or requests, contact Dooit at [email protected].