TacTacGo – Privacy Policy

A note from the developer

Hi. I'm Evan, a parent who built TacTacGo for my own kids' morning routine. Like a lot of families, ours includes kids with very different attention styles and needs.

This policy exists because I care about where my kids' data goes — and I assume you do too.

Most privacy policies describe what an app already does: collect advertising IDs, send crash logs to a vendor, share data with "partners" for analytics. This one is different, because the app is built so that:

• No account. No sign-in. No email. No phone number.
• No advertising SDK. No analytics SDK. No cookies. No third-party tracker. Zero.
• No server of mine that your family's data ever touches. There isn't one.
• The only cloud copy is in your own Google Drive, end-to-end encrypted with your device screen lock — it is designed so that neither Google nor I can read it.
• Pairing your phone to the tablet happens directly between those two devices, over Bluetooth or local Wi-Fi. Nothing passes through a middleman.
• The only "We reserve the right to .." clause you'll find in this document is ... literally that one, that is the only clause like that you'll find anywhere in this whole policy.

Everything below this note is a plain, honest inventory of exactly what the app does — no hedging clauses, no "we may collect" escape hatches for later. If you find a line in the policy that contradicts a claim in this box, that's a bug and I want to hear about it (contact in Section 14).

If this feels like a breath of fresh air: please tell another parent. Privacy-respecting kids' software is rarer than it should be, and one parent telling another is how that changes.

Thanks for trusting TacTacGo to help make your family’s mornings a little easier.

— Evan

Effective date: April 20, 2026 Last updated: May 9, 2026

Publisher: twoecom (the "Developer", "we", "us", "our") App: TacTacGo ("TacTacGo", the "App") Package name: com.twoecom.tactacgo Contact: e@0x2ecom.com

1. Summary (plain English)

TacTacGo is a local, device-first app for scheduled morning routines, wake alarms, and optional parent/admin controls. It is designed to work on the device itself and, when the user chooses to pair devices, directly between nearby devices over Bluetooth LE and Google Nearby Connections.

In normal use, TacTacGo:

• Does not send your personal data to the Developer or to any server operated by the Developer.
• Does not contain advertising SDKs, analytics SDKs, cookies, tracking pixels, or any other third-party tracker.
• Does not require a user account, sign-in, email address, or phone number.
• Does not collect location coordinates, contacts, call logs, SMS, microphone audio, or browsing history.
• Stores routine, profile, history, and pairing data locally on your device.

Two narrow exceptions — both under your control and neither readable by the Developer — are described below:

1. Device-to-device sharing. Content you intentionally share with another device you control (for example, pairing a phone with a tablet, syncing a routine, approving an unlock, or transferring downloadable content packs). Those transfers happen directly, peer-to-peer, over Bluetooth LE and/or Wi-Fi Direct via Google's Nearby Connections API. See Section 5.
2. Android Auto Backup to your own Google Drive. If you have Android backup enabled on your device (the default on most Android devices), the operating system periodically copies TacTacGo's routines, profiles, task history, favorites, and pairing state to your own Google account. On Android 9 and newer, these backups are end-to-end encrypted using a key derived from your device screen lock (PIN / pattern / password), which means it is designed so that neither Google nor the Developer can decrypt or read them.

2. Information TacTacGo handles

2.1 Data you create in the App (stored locally on your device)

When you use TacTacGo, you may create or configure:

• User profiles (e.g., display name, avatar, per-profile settings) — names are chosen by you and may be a real name, nickname, or anything else.
• Routines, schedules, "crate" tasks and related configuration (go-times, wake times, task order, timing, etc.).
• Alarm settings (volume ramp, vibration, anti-movement alarm, etc.).
• Task history and daily logs (which tasks were completed, when, and related timing information).
• Parent/admin settings (approval preferences, trivia gate, pairing state with paired devices).
• "History images" — if you use the parent/admin features that save images, these are saved to your device's standard Pictures/TacTacGo folder via the Android MediaStore.
• Downloadable content ("DLC") packs that you choose to install, transfer, or receive from another device you have paired.

All of the above is stored only on the device (in the app's private storage and, for history images, in the device's Pictures folder). TacTacGo does not upload any of this data to the Developer.

2.2 Device and pairing identifiers (stored locally and shared only with paired devices)

To let paired devices recognize each other, TacTacGo generates and stores:

• A locally-generated device identifier (GUID) created the first time the app runs.
• Device role (e.g., tablet, admin phone, alarm-clock phone) and device model/name as reported by Android.
• Pairing state with other devices you have explicitly paired (e.g., scanned a QR code to link).
• Transient connection metadata used by Google Nearby Connections (e.g., endpoint IDs, service IDs) while devices are actively connected or advertising.

These identifiers are used exclusively for device-to-device communication between devices you have chosen to pair. They are not sent to us or to any third-party service.

2.3 Diagnostic logs (stored locally)

TacTacGo writes diagnostic logs to the app's external files directory (Android/data/com.twoecom.tactacgo/files/log/) to help with troubleshooting. Logs may include timestamps, component tags (e.g., [RDV], [ALARM], [APP_STATE]), connection states, error traces, and similar technical information. Logs remain on the device. The App does not automatically transmit logs to the Developer. If you choose to share logs with the Developer for support purposes, you do so manually (for example by sending a file).

2.4 Information we do not collect

TacTacGo does not collect, transmit, or share:

• Your name, email address, phone number, postal address, or date of birth.
• Precise or approximate geographic location (the location permission is requested for a different reason — see Section 4).
• Contacts, calendar entries, call logs, or SMS messages.
• Microphone audio, photos outside Pictures/TacTacGo, or videos.
• Web browsing history or information from other apps.
• Advertising identifiers.

2.5 Cookies and similar tracking technologies

TacTacGo is a native Android app. It does not use HTTP cookies, browser local storage, tracking pixels, web beacons, SDK advertising identifiers, device fingerprinting, or any similar technology commonly used on the web or in ad-supported apps to identify or follow users across sessions, apps, or sites. The App contains no embedded WebView and no embedded web content, and loads nothing that could set such tokens on your device. If this ever changes — for example, if a future feature were to show remote content in a WebView — this Privacy Policy would be updated before the feature shipped, and the new behaviour would be described here.

3. How information is used

Information handled by TacTacGo is used only to:

1. Run the routines, alarms, and task flows you configure.
2. Display your history and statistics to you on your device.
3. Allow paired devices you control to discover each other, exchange pairing information, approve unlock requests, and sync routine/content data.
4. Deliver notifications (alarms, approval requests, check-in prompts) on your device.
5. Write local diagnostic logs so you can troubleshoot issues on your own device.

We do not use your data for advertising, profiling (including behavioral tracking across apps or services), sale, or analytics.

4. Android permissions and why we ask

Android requires apps to declare permissions for certain capabilities. TacTacGo requests the following; each is used only for the purpose described.

If you deny a permission, the related feature may be unavailable, but the rest of the App will continue to work where possible.

5. Local device-to-device connectivity

TacTacGo uses Bluetooth Low Energy (BLE) and Google Nearby Connections (part of Google Play services) to let devices you control talk to each other directly — for example, to pair an admin phone with a tablet, approve an unlock, sync routine changes, or transfer downloadable content packs.

• These connections happen locally between your devices. Data sent this way does not pass through our servers (we don't operate any for this app).
• Google Nearby Connections is provided by Google Play services on your device. Its use is subject to Google's Privacy Policy and the Google Play services terms. Google does not receive your TacTacGo content through this API, but Google Play services on your device may process diagnostic and operational data as described in its own policies.
• Pairings are initiated by explicit user action (e.g., scanning a QR code).

5.1 Android Auto Backup (Google Drive)

So your kids never lose their progress — stars, streaks, finished crates, favorites, and the routines you've fine-tuned over months — TacTacGo participates in Android Auto Backup, the standard Android mechanism that copies app data to the signed-in user's own Google Drive. This is what lets you set up a new tablet, or reinstall the App after a factory reset, and pick up exactly where the family left off. Here is exactly what happens, and where the limits are.

What is backed up: profiles, routines, scheduled tasks / crates, settings, favorites, daily task-history logs, DLC category status, and device pairing state (SharedPreferences, including the locally-generated device GUID).

What is not backed up to the cloud: downloadable content (.ttp) packs, ttp caches, diagnostic logs, and system caches. These are excluded to keep cloud backup well under the 25 MB per-app quota that Android enforces.

DLC packs are carried over by device-to-device transfer (the "copy from old device" flow in Android's setup wizard, which has no strict size quota). After a cloud restore, TacTacGo automatically reconciles its state on first launch — categories whose content is no longer present are marked "needs re-transfer," and you can re-acquire them by pairing an admin device or re-installing from the in-app store. No routine or history data is lost in either path.

Where backups live: in your own Google account (Google Drive), counted against a separate per-app backup quota, not against your normal Drive storage. The Developer has no account relationship with Google that would allow access to your backups.

Encryption: on devices running Android 9 (Pie) or newer with a screen lock configured, Android encrypts Auto Backups end-to-end using a key derived from your device PIN / pattern / password. Google's servers store the backup but do not hold the key, so neither Google nor the Developer can read the contents of your backup. See Google's Android backup encryption description.

How to disable or delete it:

• Disable for TacTacGo only: Android Settings → Google → Backup → App data → uncheck TacTacGo (wording varies by device).
• Disable entirely: Android Settings → System → Backup → turn off Backup by Google One.
• Delete an existing backup: open the Google One app → Storage → Device backups → select your device → Manage backups → remove TacTacGo (or the whole backup).

If you disable backup, TacTacGo continues to work normally — you simply lose the ability to restore your data if the device is wiped or lost.

5.2 Future / dormant modules

The App also contains a stub module intended for future push-notification delivery (PushNotificationBackend). As of the effective date of this policy, this module is inactive and does not transmit any data. If we later enable push delivery, we will update this Privacy Policy before doing so and describe exactly what is transmitted and to whom.

6. Third-party components

TacTacGo is built with standard Android libraries and the following notable third-party components that run on your device:

• Google Play services – Nearby Connections (for local peer-to-peer discovery and transport). See Google's Privacy Policy.
• Android Auto Backup / Google Drive — provided by the Android operating system and your Google account, used to back up TacTacGo data end-to-end encrypted to your own Drive. See Section 5.1 and Google's Privacy Policy.
• AndroidX Jetpack libraries, Jetpack Compose, CameraX, Hilt, Coil, ZXing, Timber, Kotlinx Serialization, Drew Noakes metadata-extractor, AndroidX ExifInterface/Biometric. These are in-app libraries; they do not, in themselves, collect or transmit personal data.

TacTacGo does not integrate Firebase, Crashlytics, Google Analytics, AdMob, Facebook SDK, or any other advertising or analytics SDK. Some system-level services (such as Google Play services) may process limited technical data independently under their own policies. TacTacGo does not receive or have access to that data.

7. Children's privacy

TacTacGo is designed to be used as part of a family / parent-supervised morning routine, which means children may interact with the device on which it runs. Because the App:

• does not create user accounts,
• does not require any personal identifier (no email, phone, name required),
• does not transmit data to us, and
• does not contain ads or third-party trackers,

…it does not knowingly collect personal information from children within the meaning of COPPA, the UK Age Appropriate Design Code, or similar regimes. Any information entered into the App (such as a child's chosen profile name) is stored locally on the device controlled by the parent/guardian.

Parents and guardians are responsible for the content they enter into profiles, routines, and the parent/admin dashboard (including any "history images" saved to the device), and for managing those on the device.

If you believe a child has somehow provided personal data to us directly, please contact us at the email in Section 14 and we will delete it.

8. Data retention and deletion

• On-device data (profiles, routines, history, logs, pairing state, DLC packs, history images) remains on your device until you delete it.
• You can delete TacTacGo data at any time by:
• Using any in-app reset / clear options where provided, or
• Going to Android Settings → Apps → TacTacGo → Storage → Clear storage / Clear data, or
• Uninstalling the App, which removes app-private data. History images saved to Pictures/TacTacGo are not removed by uninstall; you can delete them from your gallery.
• Google Drive backup copy (if Auto Backup is enabled on your device): lives in your own Google account and is subject to your own Google settings. Delete via the Google One app → Storage → Device backups → Manage backups, or disable backup as described in Section 5.1. Uninstalling the App does not by itself remove an existing Drive backup.
• Paired devices each hold their own copy of shared data. To remove data from a paired device, repeat the above steps on that device.
• Because the Developer does not collect your data on its servers, there is no Developer-side copy for us to delete. The Drive backup is held by Google on your behalf and is inaccessible to the Developer.

9. Security

Data handled by TacTacGo stays on your device and on devices you pair with it. Android enforces app sandboxing so that other apps cannot read TacTacGo's private storage. Device-to-device messages use Google Nearby Connections' built-in transport security.

No method of electronic storage or transmission is 100% secure. You are responsible for securing the devices TacTacGo runs on (screen lock, OS updates, etc.).

10. Your rights

Because TacTacGo does not collect personal data on our servers, there is generally no account or server-side record for us to provide, correct, export, or delete under laws such as the GDPR, UK GDPR, or CCPA/CPRA. You retain full control of the data stored on your own device (see Section 8).

If you have questions or want to exercise any rights under applicable privacy law regarding data you believe we hold, contact us using the email in Section 14.

11. International use

TacTacGo is distributed in multiple languages and may be used worldwide. Because the App operates locally on your device and between devices you pair, no international data transfers to the Developer take place. Android Auto Backup data is stored by Google on your behalf and may be held in Google data centres outside your country; because the backup is end-to-end encrypted with a key only you hold, the content is not readable by Google, the Developer, or any third party in transit or at rest.

12. Changes to this policy

We may update this Privacy Policy from time to time — for example, if we add a new feature such as push notifications or optional cloud sync. When we do, we will update the "Last updated" date above and, for material changes, surface a notice in the App or in release notes. Continued use of the App after an update constitutes acceptance of the updated policy.

That acceptance applies to published policy text you can read — not to hidden behaviour. Section 13 below commits us to updating this document before shipping any feature that would change what the App does with your data, so you never discover new data practices only by diffing the policy after the fact.

13. Our commitments — the short version

Three things this policy does that most don't. Consider this the part you can quote.

1. No placeholder clauses. Every claim in this document reflects something the App either does or does not do today — not a menu of possibilities the Developer is quietly leaving open for later. Go ahead and search this whole policy for clauses of the open-ended, do-anything-later variety. You will find exactly one, up in the box at the top. That's it. Literally the only one.

2. Policy changes come before code changes, not after. If a future feature would alter any claim above — for example, enabling push notifications, adding optional cloud sync, or integrating crash reporting — this Privacy Policy will be updated before the feature ships in a release build, and the change will be called out in the App's release notes. You will never have to go read a policy to find out what an already-released version of the App has quietly started doing.

3. Policy-vs-App mismatches are bugs. If you ever find behaviour in the App that contradicts something in this policy, tell us (Section 14). We treat that as a bug on equal footing with a crash, and fix it the same way.

14. Contact

Questions, concerns, or requests about this Privacy Policy:

• Email: e@0x2ecom.com
• Publisher: twoecom
• App: TacTacGo (com.twoecom.tactacgo)

15. tacacgo.com website — optional launch email list

The marketing site at tactacgo.com is separate from the App. Nothing in this section changes how the App handles data on your device.

If you use the optional signup form to hear when TacTacGo launches:

• What you give us: the email address you type into the form (and anything else you submit in that same form, such as consent you confirm there).
• Why: to send you a small number of emails about launch and availability on Google Play or the App Store, and related practical updates, until you opt out.
• How it works technically: the form posts from your browser to a third-party form and email-list provider the Developer configures (for example Formspree, Buttondown, or a similar service). That provider receives the submission on its systems and may store or process it under its own terms and privacy policy. The Developer does not sell the list or use it for unrelated advertising.
• Opt-out and deletion: email e@0x2ecom.com from the address you signed up with and ask to be removed, or use an unsubscribe link if one is included in a message we send.
• Cookies and trackers on the static pages: the HTML and CSS pages themselves are not built to load analytics or advertising trackers. Submitting the form sends data to the provider’s endpoint; that domain may use cookies or logs in line with that provider’s documentation.