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.

Unlike this one, 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 TacTacGo is built different so that:

• No TacTacGo account. No sign-in. No email. No phone number.
• No advertising SDK. No analytics SDK. No cookies. No third-party tracker. Zero.
• Your child's profile, routines, progress, and history are never sent through a TacTacGo server or tracked or collected by us — ever.
• The only cloud copy of that family content is the Android backup in your own Google account, if device backup is enabled. Android and Google manage it; I cannot browse, download, or read it.
• Your devices pair by QR code and talk directly over your local Wi-Fi using authenticated TCP. No Google Nearby Connections, Bluetooth scanning, location permission, or middleman for family messages.
• We use the minimum carefully selected online services to handle technical signals — not your child's content — to wake paired devices, confirm Full Unlock or DLC access, and deliver image packs you choose. Every field they need is described below.

The only “We reserve the right to…” clause you'll find in this document is… literally this sentence. That's the only one.

Everything below this note is a plain, honest inventory of exactly what the App does today — not a shopping list of data I might want someday. 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: June 30, 2026

Publisher: twoecom (the “Developer”, “we”, “us”, “our”)
App: TacTacGo (“TacTacGo”, the “App”)
Package name: com.twoecom.tactacgo
Contact: go@tactacgo.com

1. Summary

TacTacGo is a local, device-first app for family routines, wake alarms, and parent controls.

• Profiles, routines, task history, settings, and family progress are stored on your devices.
• Paired devices communicate primarily over an authenticated TCP socket on the same local network. TacTacGo no longer uses Google Nearby Connections and does not request Bluetooth or location permissions for this connection.
• When enabled and available, Firebase Cloud Messaging provides a small wake-up and rendezvous channel so a sleeping paired device can reconnect. Ordinary routine, profile, and history data is not sent through this channel.
• TacTacGo contacts our pack catalog and download service when browsing or installing reward-image packs. Full Unlock includes the Core image packs; additional DLC image packs may be acquired separately.
• Android may back up eligible App data to your Google account if device backup is enabled.
• The App contains no ads, behavioral analytics, or third-party tracking SDKs. We do not sell or rent personal data.

TacTacGo does not require you to provide a name, email address, or phone number. Firebase may create a pseudonymous installation identifier and anonymous authentication identifier for push delivery and service protection; these are not a TacTacGo profile or a sign-in you manage.

2. Information TacTacGo handles

2.1 Family data stored on your device

Depending on the features you use, the App stores:

• profile names or nicknames, avatars, and per-profile settings;
• routines, schedules, tasks, wake times, and alarm settings;
• completion history, stars, streaks, favorites, and daily logs;
• parent/admin preferences, approvals, check-ins, and paired-device state;
• history images that you explicitly save to Pictures/TacTacGo;
• installed reward-image packs and pack metadata; and
• entitlement state, such as whether Full Unlock is active and which optional DLC packs are owned or enabled.

This family content remains in App-controlled storage or, for saved history images, the device's Pictures collection. It may be copied to another device you pair or included in Android backup as described below.

2.2 Device, pairing, and local-network data

TacTacGo creates or handles:

• a random device GUID and household identifier;
• device role, model/name, App version, and paired-device records;
• pairing invitations, authentication material, connection nonces, and authorization state;
• local IP addresses, TCP port and connection state; and
• mDNS/DNS-SD service records used to find TacTacGo devices on the same Wi-Fi network.

These details let your devices find and authenticate each other. Other devices on the same local network may be able to observe that a TacTacGo service is advertised, as is inherent to mDNS.

2.3 Push wake-up data

When the push wake-up channel is configured and enabled, TacTacGo and Google's Firebase services handle:

• a Firebase Cloud Messaging registration token;
• a Firebase installation/anonymous authentication identifier and short-lived authentication token;
• an App Check attestation token, which helps confirm that requests come from a genuine App installation;
• the sending and destination device GUIDs, message identifiers, reason/urgency, timestamps, and delivery status; and
• an encrypted “doorbell” payload containing short-lived local TCP connection candidates.

The Developer-operated relay and Firebase use this information only to wake or reconnect a paired device. Normal family profiles, routines, tasks, progress, and history do not travel through this relay. A narrow synthetic diagnostic probe may use the same path during troubleshooting.

2.4 Reward-pack catalog and downloads

The public catalog contains pack IDs, titles, preview artwork, versions, product IDs, and download broker endpoints. When the App refreshes the catalog, normal web request information such as IP address, request time, and user agent may be processed by our hosting provider.

When you request a Core or DLC pack, the App sends the download broker:

• pack ID, type, and version;
• App version;
• device GUID and household ID;
• Full Unlock status and owned DLC product IDs;
• a timestamp, one-time nonce, and request signature; and
• normal network request data such as IP address.

If authorized, the broker issues a short-lived HTTPS download URL. The pack is downloaded from Google Cloud Storage or its delivery network, checked for size, SHA-256 hash, and database integrity, then installed locally. The service records limited operational logs such as the pack, result, timestamp, network request metadata, and a shortened device identifier for security, abuse prevention, and troubleshooting.

2.5 Purchases and entitlements

TacTacGo's commercial model may include:

• Full Unlock, a one-time entitlement to the complete TacTacGo feature set and Core image packs; and
• optional DLC reward-image packs, acquired individually and not automatically included with Full Unlock.

The App stores and synchronizes entitlement state between your paired devices. Where a purchase is offered through Google Play, Google processes the transaction under its own terms and privacy policy. TacTacGo receives the product identifier and purchase/entitlement status needed to unlock content; we do not receive your full payment-card details. Development or pre-release builds may use a local test entitlement instead of a real transaction.

2.6 Diagnostic logs

TacTacGo writes technical logs locally to its App files directory. Logs may contain timestamps, component tags, connection state, shortened identifiers, errors, and stack traces. They are never uploaded or collected automatically. If you manually choose to send logs to us for support, we use them to investigate the issue and delete them when they are no longer needed for that purpose.

2.7 Information TacTacGo does not collect

The App does not collect contacts, call logs, SMS, microphone recordings, precise or approximate location, browsing history, or advertising identifiers. It does not use Firebase Analytics, Crashlytics, Google Analytics, AdMob, the Facebook SDK, or another advertising/behavioral analytics SDK.

3. How information is used

TacTacGo uses information only to:

1. run the routines, alarms, rewards, and parent controls you configure;
2. connect and synchronize devices you choose to pair;
3. wake sleeping paired devices and establish a local connection;
4. show the pack catalog, check entitlement, and securely deliver requested content;
5. restore eligible data through Android backup or device transfer;
6. provide App updates and purchase functionality through Google Play; and
7. secure, operate, and troubleshoot these features.

We do not use this information for targeted advertising, cross-app tracking, sale, or behavioral profiling.

4. Android permissions and special access

The current production manifest declares the following permissions. Some are automatically granted or are special system access rather than runtime prompts.

TacTacGo does not declare location, Bluetooth, Nearby Wi-Fi Devices, or camera permission. QR pairing uses the permissionless Google Code Scanner supplied by Google Play services; scanning is performed on the device and TacTacGo receives the decoded code, not a saved camera image.

5. Connectivity and cloud services

5.1 Local TCP and mDNS

The tablet acts as a local hub and paired phones connect to it using a TCP socket on the same LAN. mDNS/DNS-SD helps a paired device rediscover the tablet after an IP address changes. QR codes and pairing invitations bootstrap authorization; later connections use an authenticated handshake, nonces, and paired-device authorization checks.

The TCP data plane is local and does not route family messages through our server. Because it uses your LAN, use TacTacGo on a network you trust and keep devices and routers updated.

5.2 Firebase wake-up relay

Firebase Cloud Messaging is a small signaling channel, not the normal data plane. It can wake a sleeping device and deliver an encrypted, short-lived rendezvous “doorbell”; the devices then move family data over local TCP. Relay requests use HTTPS, Firebase anonymous authentication, and Firebase App Check. The feature can fall back to local/scheduled reconnection when unavailable.

Google and our Google Cloud project necessarily process delivery and operational metadata for this service. Cloud service logs are retained only as needed for operation, security, abuse prevention, and troubleshooting, subject to our configured Google Cloud retention and Google's terms.

5.3 Android backup and device transfer

If Android backup is enabled, Android Auto Backup may copy profiles, routines, history, settings, favorites, entitlement/pack status, pairing state, and related user data to the Google account configured on the device. Android and Google control backup scheduling, storage location, encryption, and retention; the Developer cannot browse or download your Android backup.

Cloud backup excludes downloaded .ttp image packs, pack caches, and diagnostic logs. Android's direct device-transfer flow may copy downloaded packs as well as user data. Missing packs can be downloaded again after entitlement is restored.

You can control or delete backups through Android/Google One backup settings; wording varies by device and Android version.

6. Third parties

The notable external services are:

• Google Firebase Authentication, Cloud Messaging, App Check, and Cloud Functions for the limited wake-up/rendezvous channel;
• Google Cloud hosting, API Gateway, Cloud Storage, and content delivery for the public pack catalog, protected pack downloads, security logs, and this website;
• Google Play for App distribution, updates, optional purchases, and the permissionless Google Code Scanner; and
• Android Auto Backup / Google One for backup selected by the device owner.

These services process data under Google's Privacy Policy and applicable service terms. In-app libraries such as AndroidX, Jetpack Compose, Hilt, Coil, Kotlinx Serialization, Timber, and metadata readers do not by themselves send personal data to their authors.

7. Children's privacy

TacTacGo is intended for parent- or guardian-supervised family use. A child can use a profile without supplying an email address, phone number, date of birth, or account. Profile names and routine content remain on family devices and are not included in the push or pack-delivery data described above.

The limited online data is device/service metadata used to connect paired devices, protect the service, deliver requested packs, or process purchases. We do not knowingly use children's data for advertising, tracking, or profiling. Parents control the names and content entered in the App and can delete them as described below.

If you believe personal information from a child was sent to us unexpectedly, contact us at the address in Section 14.

8. Retention and deletion

• On-device data remains until you remove it with in-App controls, clear TacTacGo's storage in Android Settings, or uninstall the App. Images saved in Pictures/TacTacGo may need to be deleted separately from your gallery.
• Paired devices keep their own copies. Delete data separately on each device when needed.
• Android backups are controlled through your Android or Google One backup settings.
• Firebase identifiers and cloud operational logs are retained as needed to provide and secure the wake-up service and under the configured retention of the relevant Google service.
• Pack-delivery request logs are retained as needed for download delivery, fraud/abuse prevention, security, and troubleshooting. Download URLs expire after a short period, although infrastructure access logs may remain for their configured retention period.
• Google Play purchase records are retained by Google under its policies. Local entitlement records remain until App data is cleared, subject to restoration or synchronization from the purchase service or a paired device.
• Support material you send directly is kept only as long as reasonably necessary to answer the request and maintain an appropriate support record.

For a privacy request concerning data we control, email go@tactacgo.com. We may need information such as a shortened device identifier or approximate request time to locate pseudonymous service records; in some cases we cannot link those records back to a person.

9. Security

App-private data is protected by Android's application sandbox. Cloud traffic uses HTTPS. Push rendezvous details are encrypted with household session material. Local TCP connections use an authenticated handshake, replay protection, and paired-device authorization. Pack downloads use short-lived URLs and are verified for identity, length, hash, and database integrity before installation.

No storage or transmission method is completely secure. Protect devices with a screen lock, keep Android and the App updated, and use a trusted local network.

10. Your rights

Depending on where you live, you may have rights to access, correct, delete, restrict, or object to processing of personal data and to lodge a complaint with a data-protection authority. Most family content is under your direct control on your devices. For the limited service data we control, contact us using Section 14.

We do not discriminate against anyone for exercising a privacy right and do not sell or share personal data for cross-context behavioral advertising.

11. International processing

Local family data normally stays on the devices you pair. Google/Firebase, Google Cloud, Google Play, and Android backup may process service data in countries outside your own under their terms and transfer safeguards. Contact us if you need more information about a specific processing flow.

12. Changes to this policy

We may update this policy when the App, its permissions, business model, or service providers change. We will change the “Last updated” date and, for a material change, may also give notice in the App or release notes.

13. Our commitments

1. No advertising SDK or behavioral analytics SDK.
2. No sale or rental of personal data.
3. Family routines, profiles, and history stay on your devices and are not the payload of our push or pack-delivery services.
4. A mismatch between this policy and the App is a bug; please report it.

14. Contact

• Email: go@tactacgo.com
• Publisher: twoecom
• App: TacTacGo (com.twoecom.tactacgo)

15. TacTacGo websites

TacTacGo's public websites and pack-store pages are separate from the App. Static pages do not use advertising or behavioral analytics trackers. Standard hosting and security logs may include IP address, request time, requested URL, browser/user-agent details, and response status.

The pack-store catalog and preview images are public. Opening or browsing them produces ordinary website requests; protected full image-pack files are delivered only through the App's short-lived download flow.

If you use an optional email signup form:

• we process the email address and consent information you submit to send the requested product or launch updates;
• a form/email-list provider may process the submission under its own privacy policy; and
• you can unsubscribe using the link in an email or request deletion at go@tactacgo.com.