SimTap
SIMTAP · HELP CENTER

SimTap Privacy Policy

Last updated: September 28, 2026

SEEDFLOW LIMITED develops SimTap. This policy explains how the SimTap app handles information when you organize phone numbers, set reminders and record maintenance actions.

Information you save

SimTap stores the information you choose to enter, which may include:

This information is stored on your device. SimTap does not require an app account. Reminder preferences and notification display settings are also stored on the device.

iCloud

On configured physical devices, SimTap uses Apple's CloudKit service to synchronize app records through the private database belonging to the signed-in Apple Account. The app does not publish these records to a public database or share them with other SimTap users.

SEEDFLOW LIMITED does not receive a separate copy of these records on its own server. The app does not provide the developer with access to the contents of your private iCloud database. Apple's handling of iCloud data is governed by its own terms and privacy policy.

Synchronization depends on your account, device, network and available iCloud service. Notification preferences remain specific to each device.

Notifications

SimTap requests notification permission to schedule local reminders. A reminder can display information about the relevant number and task. You can use Hide numbers in notifications to control whether saved phone numbers are shown, and change notification permissions in the system settings.

SimTap uses Apple's remote notification capability for iCloud synchronization. It does not run a separate developer-operated service for sending promotional pushes.

Data collection, advertising and tracking

The SimTap app has no advertising, analytics SDK or tracking SDK. It does not read your contacts or existing messages, and it does not request location access.

SEEDFLOW LIMITED does not collect your saved app records through the app, sell those records or use them for advertising. This statement concerns the app's behavior; Apple and external services may process information under their own policies when you use their services.

Community templates

When you publish a template from Templates → Community, its name, carrier, country or region, number type, maintenance rules, plan details and pricing, message content, top-up link and instructions are sent over HTTPS to a Cloudflare Worker and stored in a Cloudflare D1 database, together with a template identifier and publication time. These templates are public: other users can browse them and copy their rules into a new number. Publishing does not attach your saved phone numbers, message recipients, personal dates or activity history. Do not include personal information in public template fields.

Community does not require an account. The app creates a random author credential and stores it in this device’s keychain. It sends the credential over HTTPS to identify your own templates and likes. The server stores only a hash, linked to templates you publish and likes you choose to add. The credential and its hash are not shown in public responses or written to application logs. This community identity is specific to this device and does not sync through iCloud; if it is lost, the app cannot restore your author permissions.

Templates published with an author identity can be edited or deleted from the same device. Each identity can like a template once, including its own, and can remove that like. Templates are ordered by like count, then by publication order. Removing a like deletes its vote record; deleting a template also deletes its likes. Removing a public template cannot remove copies other users have already saved.

Cloudflare processes requests and temporarily uses the source IP address for submission limits; the Worker does not store IP addresses or template text in application logs. Templates remain available until removed. To report a template or request removal, use in-app feedback or X: @samwangxp, including the template name and carrier so it can be located.

Optional feedback

When you choose Send feedback in Settings, the app sends the text you entered, the app version and your language over HTTPS to a Cloudflare Worker. The Worker forwards it through a Discord webhook to a channel configured by the developer for support and product improvements. Saved phone numbers, plans and activity history are not attached automatically.

The form does not request your name, email, account or device identifier. Any information you choose to include in the text will be part of the feedback message. Cloudflare processes the network request and temporarily uses the source IP address to limit repeated submissions. The Worker does not store feedback in a database or write feedback text or IP addresses to its application logs. Discord processes and stores submitted messages in the channel configured by the developer.

For questions about feedback or privacy, use the in-app feedback form or X: @samwangxp. Include enough context to identify a previous submission if you request its deletion.

Messages, calls and external services

If you choose a shortcut, SimTap may open the system message composer, a telephone action, Google Voice, the App Store or a saved carrier webpage.

A saved recipient and message template can be passed to the system message composer. You review and confirm sending. SimTap cannot read your message history or automatically select a sending SIM.

External services handle actions such as calls, message delivery and carrier payments under their own terms and privacy policies. SimTap does not receive your carrier payment details.

Backups you export or import

You can export your saved information as a JSON backup and choose where to store it using the system file interface. These files contain readable, unencrypted information, including phone numbers and history. Anyone you share a backup with may be able to read it.

Importing reads the file you select and adds supported new records to the app. SimTap does not upload an imported backup to a developer-operated server. Added records may synchronize through your private iCloud database when synchronization is available.

Keep backups private. Copies stored with a file provider or sent to another person are subject to that destination's handling of the file.

Your choices and deletion

You can edit the information you save, archive a number, or delete a number and its associated rules and history. Archiving keeps the information. Deletion through the app can synchronize to your other devices when iCloud synchronization is available.

You can turn reminders off and change system notification permissions. Manage your Apple Account and iCloud storage through Apple's system settings.

Exported backup files are separate copies. Deleting a number in SimTap does not delete those files or copies you have shared. Removing the app from a device should not be treated as deleting every iCloud or backup copy.

The developer does not hold a separate server copy of your saved app records to retrieve or delete for you.

Purchases

Apple processes the purchase of SimTap through the App Store. SimTap has no in-app purchase or subscription and does not receive payment-card information. Your carrier or another external provider processes any payments you choose to make through its service.

Changes to this policy

If the app's information practices change, we will update this policy and its last-updated date. Material changes to data collection will also be reflected in the App Store privacy information where required.

This support website

These pages are hosted by Cloudflare. Cloudflare processes technical request information, including your IP address, to deliver and protect the website. We do not add analytics, advertising, cookies or a website contact form. Links to other services are governed by those services' privacy policies.