Privacy Notice, Slip Tracker

1. Who we are

Slip Tracker is an application for iPhone and for Android phones that reads Thai payment slips you select and turns them into a private spending record kept on your own device.

The data controller responsible for the limited personal data described in this notice is La Win Ko, the individual developer of Slip Tracker, referred to in this notice as "we", "us", or "Slip Tracker". You can reach us by email at privacy@sliptracker.app.

The processing described in this notice is divided as follows.

The application processes your slips and your records on your device. Slip Tracker operates no server for that data.
We generally cannot access those records. They are held in an encrypted database on your device, and the key is held in that device's secure key storage: the Keychain on iPhone, the Android Keystore on Android.
We receive information that you intentionally send to support.
Apple processes App Store purchases, and optional iCloud backup, under Apple's own terms. Google processes Google Play purchases under Google's own terms.
On Android, Google's ML Kit, the software that reads slips on your device, sends Google its own diagnostic and usage information. It does not send your slips, the text read from them, or your records.
Our hosting provider may process ordinary website logs.

2. How to contact us

For any question about this notice or about your personal data:

Privacy contact: privacy@sliptracker.app
General support: support@sliptracker.app

3. Scope of this notice

This notice applies to:

the Slip Tracker application for iPhone and for Android,
this website, including the Privacy Notice and Terms of Use pages, and
support correspondence you send to us.

This notice does not apply to Apple's own processing. When you buy Premium through the App Store, or when you enable iCloud backup, Apple processes that information as its own controller under Apple's terms and privacy policy. Nor does it apply to Google's own processing: when you buy Premium through Google Play, and when ML Kit sends Google its diagnostic information on Android (the What reaches the developer at all section), Google processes that information under Google's terms and privacy policy. This notice also does not apply to any other service you choose to send an exported file to.

4. Words used in this notice

Personal data: Information about an identifiable living natural person, as defined in Section 6 of the Personal Data Protection Act B.E. 2562 (2019).
Data controller: The person who decides the purposes and means of processing personal data.
Data processor: A person who processes personal data on a controller's instructions.
PDPA: The Personal Data Protection Act B.E. 2562 (2019) of Thailand.
PDPC: The Personal Data Protection Committee of Thailand and its Office.
Slip: An image, usually a screenshot, of a bank transfer or payment confirmation from a Thai bank or payment application.
Record: A transaction saved inside the application, whether created from a slip or entered by hand.
Your device: The iPhone or Android phone on which you installed the application.

5. Slips, and what is read from them

Slip images and selected-photo access

The application reads slip images from your photo library. There are three ways it can reach one, and you set up each of them.

You pick an image. The application opens your phone's standard photo picker (the Photos picker on iPhone, the system photo picker on Android), and the phone gives it only the images you selected. This path works even if you have not granted photo access.
You grant photo access so the application can find slips for you. With access, each time you open the application it looks through your recent photos on your device for slips, from today by default or from a date range you choose, and shows you what it found. Nothing is saved until you choose which slips to read. Every search is limited to a window of dates; there is no request that reads your entire library. You can change or remove access at any time, and on iPhone, and on Android 14 and later, you can give access to only the photos you select.
You share an image to the application from another app. The application makes its own temporary copy, reads it, and deletes that copy when the reading has finished. The original stays where it was.

The application has no camera feature. It never opens the camera and never records audio, and it asks for no camera or microphone permission on either iPhone or Android.

Album names, when the application shows them, are read live from your photo library and are never stored.

When a slip is saved as a transaction, the application keeps a local copy of its image so you can check it during review. The copy stays in the application's private files on your device. It is removed when you delete that transaction, replace your records, or delete all app data. It is not included in backup files. Your original photo remains in your photo library.

Information read from a slip

Text recognition runs entirely on your device. On iPhone it uses Apple Vision. On Android it uses Google's ML Kit, whose text and QR-code models are bundled inside the application, and, when you import slips, a Thai text recognition model that is also bundled inside the application. The recognized text is analysed on your device by software bundled inside the application. If the slip carries a Bank of Thailand style verification QR code, it is decoded on your device as well.

The raw recognized text is not stored. Once the fields have been extracted it is discarded. What the application keeps is a hash of the image and a hash of the recognized text, which are one-way values it uses to recognise a slip you have already imported so it is skipped instead of being duplicated.

No slip image, recognized text, or extracted field is transmitted to us or to any third party at this stage. This step works with no internet connection at all. On Android, ML Kit separately sends Google diagnostic and usage information about its own performance, which contains none of these (see the What reaches the developer at all section).

6. Information kept on your device

Transaction values, dates, recipients, banks, categories, and notes

A saved record can contain the following, all of it on your device:

the amount and any fee, and the currency,
the date and time printed on the slip,
the sender's name and bank, and the receiver's name and bank,
the masked account identity printed on the slip, meaning the partly hidden account number, its last four digits, and a bank code,
the transaction reference,
which application the slip came from,
the direction, meaning money out, money in, or a transfer,
the category and merchant the application matched or you chose,
any note you add yourself,
the accounts you tell the application are your own, so it can tell spending from money received,
a confidence value per field and a review flag, so uncertain values wait for you rather than being saved silently.

Some of this is personal data about other people, for example the name of someone you sent money to. You decide which slips to import, and that information stays on your device under your control.

Other information stored only on the device

Everything in the Transaction values, dates, recipients, banks, categories, and notes section is stored in a local database on your device, encrypted with SQLCipher. The encryption key is generated on your device at first launch from the operating system's secure random source. On iPhone it is stored in the iOS Keychain with the device-only accessibility class, which means it is never included in an iCloud Keychain sync. On Android it is stored encrypted with a key held in the Android Keystore, which is removed when the application is uninstalled.

On Android, the application opts out of Android's backup of app data to Google Drive. If you move to a new Android phone with Android's own transfer tool, some small settings files can move with it, but your records and the database key do not; to move your records, use the backup file described in the Backups section.

Also stored only on your device:

your settings and display preferences,
your merchant and category rules,
the count of slips read in the current quota period,
image and text hashes used to avoid duplicates,
local copies of saved slip images, kept outside the encrypted transaction database so you can review them,
if you enable app lock, a salted hash of your passcode, held in the same secure key storage as described in the App lock and biometric behaviour section.

We have no access to any of it.

App lock and biometric behaviour

App lock is optional and off by default. If you turn it on, you set a passcode. We never store the passcode itself. The application stores only a random salt and a hash derived from your passcode and that salt: on iPhone in the iOS Keychain with the device-only accessibility class, on Android encrypted with a key held in the Android Keystore.

Unlocking with Face ID or Touch ID on iPhone, or with fingerprint or face unlock on Android, is a further option, also off by default, and the passcode always remains available as a fallback. Biometric matching is performed entirely by your phone's operating system. The application receives only a success or failure result. It never sees, receives, or stores your face or fingerprint data, and neither do we.

App lock is a screen-access control. It is separate from the database encryption described in the Other information stored only on the device section, which is always on.

7. On-device summaries

The application offers an optional Premium feature that looks for patterns in records you have already reviewed. On an iPhone that supports Apple Intelligence, and where you have enabled it, this uses Apple's on-device Foundation Models framework. On an Android phone that supports Gemini Nano, it uses Gemini Nano through Android's AICore service, on the phone. The application does not download the model; it uses Gemini Nano only if your phone already has it. Availability depends on the device, the operating system version, and your settings.

You control the feature in the application's settings. Until you use its switch, it is on where your phone supports it and off where it does not. You can turn it off at any time.

The model runs on your phone. Its input and its output do not leave the device. On Android, ML Kit, the Google software that connects the application to Gemini Nano, sends Google diagnostic and usage information about the feature, including the languages set for it, but not your records, the model's input, or its output (see the What reaches the developer at all section). The design is also deliberately narrow: the model returns only a query specification, meaning a subject reference, a metric, a comparison, and a direction. It returns no amounts, no names, no dates, and no record identifiers. The application then recomputes the result from your own records and rejects anything it cannot verify, and the sentence you read is written into the application in your language.

On a phone that does not support the feature, the same patterns are calculated on your device with no model involved, and the application tells you which of the two you are looking at.

A separate optional feature can suggest a category for an unrecognized merchant name using the same on-device model. It is off by default.

8. Information we receive

What reaches the developer at all

During normal use, we do not receive or store your slip images or spending records on servers operated by Slip Tracker. There are no such servers. The application contains no advertising software, no analytics or crash-reporting service of our own, and nothing that tracks you across other companies' apps or websites. It contacts one outside service for us, RevenueCat, and only about purchases. See App Store and Google Play purchases below. On Android, one part of the application also reports to Google by itself, as the next paragraph explains.

On Android, Google's ML Kit sends Google diagnostic information. ML Kit is the Google software that reads slip text and QR codes on your device in the Android application, and that connects it to Gemini Nano where your phone has it. When it is used, it sends Google information for diagnostics and usage analytics: information about your device and the application, performance metrics, the ML Kit settings and versions in use, the size of what it processed, event types, error codes, and a per-installation identifier that Google describes as not intended to identify you or your phone. When Gemini Nano is used, this can also include user, device or other identifiers, and the languages set for the feature. It does not send the slip image, the text it read, the model's input or output, or your records, and none of it reaches us. Google uses this information to measure performance, debug, maintain and improve ML Kit, and to detect misuse or abuse, under Google's own terms and privacy policy. The application has no setting that turns it off.

We or our service providers receive personal data when:

you contact support, in which case we receive what you chose to send (the Support communications and attachments section),
you visit this website, in which case our hosting provider records standard access and security logs (the Website access and security logs section),
you buy Premium, in which case Apple or Google provides us with the sales and subscription reporting described in the App Store and Google Play purchases section, or
the app checks or restores Premium through RevenueCat at startup, when it returns to the foreground, or during a purchase or restore. This can occur even if you have not bought Premium.

App Store and Google Play purchases

Premium is sold through Apple's App Store on iPhone and through Google Play on Android, as an auto-renewable subscription or as a one-time Lifetime purchase. Apple or Google, not us, processes the payment and holds your payment details. We never see your payment method, card number, or Apple Account or Google Account credentials.

We use RevenueCat to check that a Premium purchase is real and to give it back to you when you reinstall the app or move to a new phone. When the app starts, when you return to it, and when you buy or restore Premium, it asks RevenueCat whether Premium is active. Your App Store or Google Play purchase details are what RevenueCat checks with Apple or Google to answer.

RevenueCat identifies an app installation with a random id it generates. We do not supply your name or email address as that id. The id can be linked to purchase records and is not a guarantee that purchase information is anonymous. Automatic collection of advertising and device identifiers is disabled on iPhone, and the Android application does not request that collection.

Your slips and your spending records are never sent to RevenueCat. RevenueCat also receives purchase-service technical information, including device type, operating system, and the last time the app contacted it. A network connection also exposes an IP address to the service. Disabling advertising identifiers does not prevent this information from being processed. These connections can occur even if you have not bought Premium.

Apple and Google provide developers with sales, subscription, and payout reporting. That reporting is what we receive about purchases. We do not receive your name, your email address, or your payment details from Apple through it. Google's reports list each order with its order number and the buyer's city, region, postal code and country, and do not include your name, your email address, or your payment details. In Google Play Console we can also look up an order by its order number, or by an email address you give us, for example to help you with a refund.

Website access and security logs

This website is static. It sets no cookies, contains no analytics, no tag manager, no advertising pixel, and no social or video embed. Its fonts are served from this same website rather than from a font network, so visiting a page here does not disclose your IP address to a third-party font host.

Like any website, it is served by a hosting provider, Vercel, which records standard server logs for delivery, security, and abuse prevention. Those logs typically include your IP address, the date and time of the request, the page requested, the referring page, and your browser's user-agent string. We use them only to keep the site available and secure, and we do not use them to build a profile of you.

Retention depends on the kind of log and Vercel's service settings. Vercel documents a one-hour viewing period for Hobby runtime logs; that is not a promise that all access and security information is deleted after one hour. Vercel's separate service and security records are subject to its Privacy Notice.

Saved website language preference

If you use the language control on this website, your browser stores one short value in local storage under the key sliptracker.lang, recording which of the website's six languages you chose.

The stored preference stays in your browser and is not sent as a separate data field. It is not a cookie and is not used to identify or track you. The language of the page you request is visible in its URL and may appear in hosting logs. The preference is stored only after you actively choose a language, and you can remove it at any time by clearing site data in your browser.

Support communications and attachments

If you contact support, we receive the information and attachments you choose to send. That normally includes your email address, the content of your message, and whatever you attach, which may include screenshots.

Please do not send us a slip image, an unredacted screenshot of your records, or a backup file unless we specifically ask for one and you have removed what you do not want us to see. We do not need your financial data to help you, and we would rather not hold it.

Incoming messages to our support and privacy addresses are received through Apple's iCloud Mail and are not forwarded to another email provider. Apple's handling of the service is described in its iCloud terms and Privacy Policy. We retain support correspondence for 12 months, after which we delete our copies.

9. Backups

On both iPhone and Android, you can save a backup file of your records yourself at any time, free of charge. The application makes the file on your device and hands it to your phone's share menu; where it goes from there is your choice and outside our knowledge.

iCloud backup is available on iPhone only. There is no iCloud backup on Android. On iPhone, iCloud backup is an optional feature, available with Premium, and it is off until you turn it on.

When it is on, the application writes a backup file containing your records into your own iCloud account, in the application's iCloud Drive container. It attempts this at most once every twenty-four hours, when you open the application or when it leaves the foreground, and you can also trigger a backup yourself at any time.

If you enable iCloud backup, Apple processes that backup in your iCloud account under Apple's applicable terms and privacy practices. The file goes to your iCloud, not to us. We have no access to your iCloud account and cannot read, restore, or delete that file.

The iCloud backup is the same complete file you can save yourself.

A JSON backup contains all saved transactions and the other record data supported by the backup format, including accounts, categories, rules, and settings. It does not contain saved slip images, the database encryption key, or the secure passcode hash. The application does not encrypt the JSON file. Anyone who can read the file can read its contents. Protection in iCloud or another destination depends on that service and your account settings.

Making or opening a backup, or creating a CSV, Excel, or PDF export, can leave a temporary file in the application's cache. These files may remain until the operating system clears the cache or the application is removed. Delete all data does not itself clear that file cache.

10. Purposes of processing

We and our purchase-service processor handle the limited personal data described above to:

answer your support request and resolve a problem you report,
check and restore Premium entitlements, including when the app starts or returns to the foreground,
deliver this website and keep it available, secure, and free from abuse,
remember, in your own browser only, which language you chose to read this site in,
understand aggregate sales and subscription performance from Apple's and Google's reporting, help you with a Google Play order you ask us about, and meet our tax and accounting obligations,
comply with a legal obligation, and establish, exercise, or defend a legal claim.

The processing that happens inside the application, on your device, serves the purpose you installed it for: reading the slips you choose, keeping the records you create, and showing you your own month.

11. Applicable legal bases under the PDPA

Processing	Legal basis
Answering a support request you send	Necessity for the performance of a contract or steps taken at your request, Section 24(3). Legitimate interest, Section 24(5), where the exchange is not contractual.
Serving this website and keeping server logs	Legitimate interest in delivering, securing, and protecting the site from abuse, Section 24(5).
Saved language preference in your browser	Your action in choosing a language, and our legitimate interest in showing you a page you can read, Section 24(5). The value is not transmitted to us.
Premium entitlement checks, purchases, and store sales reporting	Necessity for the performance of a contract, Section 24(3). Where applicable, compliance with tax and accounting obligations, Section 24(6).
Including Google's ML Kit in the Android application	Legitimate interest in reading your slips reliably on your own device, Section 24(5). Google processes the diagnostic information ML Kit sends under its own terms, and none of it reaches us.
Optional on-device summaries	Your choice in the application's settings. Until you use the feature's switch, it is on where your phone supports it. The processing happens on your device and no data reaches us.
Responding to a binding legal obligation	Compliance with a legal obligation, Section 24(6).
Establishing, exercising, or defending a legal claim	Legitimate interest in handling the claim, Section 24(5), subject to necessity and your fundamental rights.

Processing based on legitimate interest must be necessary for the stated purpose and must not override your fundamental rights. You may object to this processing as described in the Your rights under the PDPA section.

12. Required and optional information

What is required and what is optional

You can use the free application without creating an account with us, providing us with your name or email address, or connecting a bank. The purchase-service connections and Android diagnostic processing described in this notice can still occur. They are not switched off by choosing the free tier.

Optional, and entirely your choice:

granting photo access, so the application can find slips for you,
using the on-device summary features, which you can turn off,
enabling app lock and biometric unlock,
enabling daily reminders,
enabling iCloud backup, on iPhone,
buying Premium,
contacting support.

Required only for the thing it enables:

to buy Premium, Apple requires an Apple Account, or Google requires a Google Account, with a payment method, which you provide to Apple or Google and not to us,
to receive an answer from support, an email address or another way to reply.

Consequences of not providing information

If you do not grant photo access, the application still works. You pick slips yourself through your phone's photo picker, and the application cannot find slips for you.

If you do not enable iCloud backup on iPhone, or if you use Android, your records are not backed up automatically. You can still save a complete backup file yourself at any time, free of charge.

If you do not buy Premium, the free tier remains fully usable, including every record you have created and the complete data export.

If you do not give us a way to reply to a support message, we cannot answer it.

There is no consequence that makes the application unusable.

13. Recipients, processors, and international transfers

Recipients and processors

We do not sell personal data, and we do not share it for advertising or marketing.

Recipient	What they receive	Role
Apple	On iPhone: purchase and subscription data if you buy Premium. Your iCloud backup file if you enable iCloud backup.	Independent controller under Apple's own terms
Google	On Android: purchase and subscription data if you buy Premium through Google Play. The diagnostic and usage information ML Kit sends, described in the What reaches the developer at all section	Independent controller under Google's own terms
RevenueCat	App Store or Google Play purchase details, a generated installation id, and purchase-service technical information described in the App Store and Google Play purchases section	Processor acting on our instructions
Vercel	Website access and security logs	Processor acting on our instructions
Apple iCloud Mail	Support messages and attachments you send	Email service provider under Apple's applicable service terms and privacy policy
Professional advisers and authorities	Only what is necessary, and only where we are legally required or need to establish or defend a legal claim	Controller or processor depending on the situation

Anywhere you send a file yourself, through your phone's share menu, is your own choice and outside our knowledge and control.

International transfers

Slip recognition and transaction storage happen on your device. If you enable iCloud backup or send a backup, export, or support attachment to another service, that file can leave your device and may be processed outside Thailand.

The limited personal data we do receive may be processed outside Thailand, because our hosting and support providers may operate servers in other countries, and because Apple, Google and RevenueCat operate globally. RevenueCat is based in the United States. Its end-user processing is described in its Privacy Policy and Data Processing Addendum. Where Sections 28 and 29 of the PDPA apply, a lawful transfer ground or an appropriate safeguard is required. Merely using the application or reading this notice is not consent to an international transfer. Contact our privacy address for information about the recipients and safeguards relevant to your data.

This notice explains the processing with reference to Thailand's PDPA. Any mandatory privacy rights under other applicable law continue to apply.

14. Retention periods

Data	Retention
Slip images	Local app copies remain until their transaction is deleted, the records are replaced, all app data is deleted, or the application is removed. Backup files omit them.
Raw recognized text	Never stored by the application
Your records, rules, settings, and hashes	On your device until you delete them, or until you delete the application
iCloud backup file (iPhone)	In your iCloud until you delete it. See the How iCloud backups are deleted section, because deleting inside the application does not remove it
Website access and security logs	According to the log type and Vercel's service and security retention rules. The one-hour Hobby runtime-log viewing period is not a limit on every kind of hosting record. See the website logs section
Support correspondence	12 months, after which we delete it
Purchase check at RevenueCat	Kept to check and restore purchases while the service is used, subject to RevenueCat's processing agreement and applicable retention duties. Contact us about access or deletion of purchase-service data; deleting the app or its local records does not send RevenueCat a deletion request
Purchase and subscription reporting	As long as required by Thai tax and accounting law, and by Apple's or Google's own retention rules for the data they hold
Temporary backup and export files	In the app cache until cleared by the operating system or removed with the app. Delete all data does not clear the file cache. Files you save or share elsewhere remain there until you delete them
ML Kit diagnostic information (Android)	Held by Google under Google's own retention rules. It never reaches us

15. Security measures and breach handling

Security measures

Inside the application:

the local database is encrypted with SQLCipher,
the encryption key is generated on your device; on iPhone it is stored in the iOS Keychain with a device-only accessibility class, so it is not synced to iCloud, and on Android it is protected by the Android Keystore and left out of Android's backups,
your passcode is stored only as a salted hash, never in readable form,
the application makes no network request to any server we operate, which removes an entire class of exposure,
raw recognized text, full transaction payloads, passcodes, and backup contents are never written to logs,
reminder notifications never contain an amount, a merchant, a category, or a total, so nothing financial appears on your lock screen.

For the limited data we receive, we use reputable providers, restrict access to those who need it, and use the security controls those providers offer.

No security measure is perfect, and no application or website can be guaranteed secure. What we can say is that the application is designed so that there is very little for anyone to take from us, because we hold very little.

Personal-data breach handling

If a personal data breach occurs in a system we control, we will assess the risk and, where the breach is likely to result in a risk to the rights and freedoms of individuals, notify the Office of the PDPC without undue delay and, where feasible, within 72 hours of becoming aware of it, in line with Section 37(4) of the PDPA.

Where the breach is likely to result in a high risk to your rights and freedoms, we will also notify you without delay, together with the remedial measures taken.

A breach of your device, your iCloud account, your Apple Account, or your Google Account is outside our systems and outside our knowledge. Section 6 explains how the data on your device is protected, Apple's own notice covers your iCloud and Apple Account, and Google's covers your Google Account.

16. Your rights, and how to complain

Your rights under the PDPA

Where the PDPA applies, you can exercise the rights below under the conditions set by the law. You can manage your local transaction records in the application. For personal data we or our processors hold, contact us at our privacy address.

Right of access and to obtain a copy, Section 30: You can view your transaction records and create a free JSON backup in the application's settings. The backup includes the data described in the Backups section. For personal data we or our processors hold, such as support correspondence or purchase-service records, contact us.
Right to data portability, Section 31: The free JSON backup provides a machine-readable copy of all saved transactions and the other data supported by the backup format. Slip images and secure keys are excluded, as explained in the Backups section.
Right to object, Section 32: You may object to processing based on legitimate interest, including the purposes described in the Legal bases section.
Right to erasure or de-identification, Section 33: Delete a record, delete everything, or delete the application. See the How local records are deleted section. For anything we hold, contact us.
Right to restrict processing, Section 34: You may ask us to restrict our use of data we hold about you.
Right to rectification, Sections 35 and 36: You can correct transaction details inside the application. For personal data we hold, ask us to correct it.
Right to withdraw consent, Section 19: Where we rely on your consent, you may withdraw it at any time. Withdrawing does not affect the lawfulness of processing before the withdrawal. In the application, every optional feature can be turned off in settings, and photo access can be changed or removed in your phone's settings at any time.

To exercise a right, contact us at privacy@sliptracker.app. We will respond within 30 days. There is no charge for a reasonable request. We may need to ask for information to confirm your identity, and if we cannot identify any data we hold about you we will tell you that plainly.

Complaints

You can contact us at privacy@sliptracker.app. You do not have to contact us before exercising your right to complain to the PDPC.

You also have the right to lodge a complaint with the Office of the Personal Data Protection Committee of Thailand, which under Section 73 of the PDPA is submitted for consideration by the Expert Committee. Contact details and the complaint procedure are published by the Office of the PDPC at www.pdpc.or.th.

17. Deleting your data

How local records are deleted

One record. Open it and delete it from its detail screen.
Everything. Settings, then Delete all data. This erases every transaction, merchant rule, category, setting, backup status entry, scan usage count, account, and saved scan marker from the encrypted database, and clears the application's preference store. It also attempts to remove the saved slip-image copies.
The whole application. Deleting Slip Tracker from your phone removes the app's ordinary local files, including its transaction database, saved slip-image copies, and file cache. Secure-key storage behaves differently, as explained below.

For completeness: Delete all data empties the database but does not itself remove the database file or its key (in the iOS Keychain on iPhone, in the Android Keystore on Android), or a passcode hash held in secure storage. It is not a guarantee of forensic erasure. On Android, uninstalling removes the secure storage used by the app. On iPhone, Keychain entries can remain after uninstalling and may be available if the app is reinstalled. These entries do not contain your transaction records. Delete all data also leaves temporary backup and export files in the app's cache, your original photos, files you exported elsewhere, and data held by purchase or support providers. Contact us to request deletion of personal data we or our processors hold.

How iCloud backups are deleted (iPhone)

Deleting data inside the application does not delete an iCloud backup. The backup file lives in your own iCloud account and we have no access to it, so you delete it yourself.

Open the Files application on your iPhone, or iCloud Drive on a Mac.
Go to iCloud Drive, then the Slip Tracker folder, then Backups.
Delete the backup file.
Empty Recently Deleted, so the file is not retained for a further 30 days.

You can also turn iCloud backup off in the application's settings, which stops any further backup from being written but does not remove files already there.

Backup files and exports you sent through your phone's share menu went wherever you sent them, and you delete those in the same way you would delete any other file.

18. Children and legal capacity

Slip Tracker is a personal finance tool intended for adults. It is not directed at children and we do not knowingly collect personal data from a child.

Under Section 20 of the PDPA, where consent is required from a minor: if the minor is ten years old or younger, consent must be given by the person holding parental power; for a minor older than ten but not yet of legal age, consent is given by the minor for acts the minor may lawfully perform alone under the Civil and Commercial Code, and otherwise by the minor together with the person holding parental power.

A purchase requires an Apple Account or a Google Account. Apple applies its own age requirements and Family Sharing controls, including Ask to Buy, and Google applies its own age requirements and parental controls for Google Play purchases.

If you believe a child has provided us with personal data, please contact us and we will delete it.

19. Changes, effective date, and language

Changes to this notice

We may update this notice when the application changes or when the law changes. When we do, we will change the "Last updated" date at the top of this page.

If a change materially reduces your privacy protection or materially expands what we collect, we will give notice before the change takes effect, in the application or on this page, and where the law requires consent we will ask for it. Changes apply going forward and are never applied retroactively.

Previous versions are available on request.

Effective date

This notice takes effect on 31 August 2026 and was last updated on 14 October 2026, to describe the Thai text recognition model on Android.

Language and interpretation

This notice is published in English and in Thai. The two versions are intended to have the same meaning.

In the event of a conflict between them, the Thai version prevails for users resident in Thailand and for any matter governed by Thai law. Elsewhere the English version prevails.

Section headings are for convenience only and do not affect interpretation. If any part of this notice is found to be invalid or unenforceable, the rest continues to apply.

Back to Slip Tracker