Your information, explained.

1. Information we process

Google sign-in provides your account identifier, name, email address and available profile photo. Your Tuki profile includes a username and may include photos, a biography, hometown, occupation, education and social links. Phone and WhatsApp contact numbers are optional; their Public, Friends or Private controls determine whether eligible users can see them.

We process messages, reactions, read/delivery status, temporary typing status, friendships, follow relationships, circles, sharing preferences, blocks and reports to provide the features you use. Optional shop pages can include a business name, description, category, address, contact details, location, photos, comments and likes. Information you publish on a profile or shop is visible to the audience allowed by that feature.

2. Location sharing

With your permission, Tuki processes location coordinates, accuracy, timestamps and available movement or direction information. Location is used for map positions, distances, Nearby, sharing and related features. Everyone makes your shared location available to public-map participants; Friends uses mutual-friend permissions. Circle sharing is a separate opt-in for each circle.

Tuki collects location updates in the background, including when the app is closed or not in use, when you enable background sharing and grant the necessary permissions. Android displays a foreground-service notification while supported background tracking runs. Updates depend on GPS, connectivity, permissions and device restrictions. An internet connection alone does not establish a fresh GPS fix.

Only Me stops general sharing; turn off enabled circle sharing as well to stop those audiences. Manage sharing opens Tuki’s sharing controls. Stopping sharing stops tracking locally and syncs removal of shared location records when connected. A previous location can remain visible remotely until the stop reaches the server. SOS sends a signal to eligible friends and opted-in circles; Tuki does not dispatch emergency services.

New people in your city

While you use Tuki with Everyone sharing, your phone’s geocoding provider may receive an available GPS point to identify its city. Tuki keeps the latest city, country, region, coarse area and update time in a private server record, separate from your profile’s Lives in field. A new account that enables Everyone within its first day may be announced by name to other eligible Everyone users recently located in the same city. Alerts link to the public profile and contain no exact coordinates. We recheck sharing choices and blocks, require a shared GPS fix within the last 24 hours near the geocoded area, and limit these alerts. City identification uses existing foreground location updates; fresh background GPS can keep recipients eligible without reopening the app. This does not change live GPS tracking. You can mute New people in your city in notification settings. We retain a one-time join marker and delivery records to prevent repeated announcements; account deletion removes city membership, join markers, device capability records and pending alerts.

Private My Timeline

My Timeline automatically stores location points from permitted updates Tuki receives, including available background updates, locally on this phone under your account. It shows routes and estimated distance for the last seven calendar days. Tuki does not upload this Timeline route history to its server or show it to friends. The map provider receives map-tile requests when you view a route. Your phone’s geocoding provider may also receive the route points visible on your screen to return place names. You can clear history in My Timeline; new permitted location updates can create new history afterwards. Uninstalling or clearing app storage removes local history. Revoking location permission prevents new location collection.

Nearby encounters may be saved locally for the last three calendar days. Older Timeline and Nearby entries are pruned when the relevant history is read or updated; this is not a remote backup service.

3. Messages, notifications & chat heads

Messages are stored on our service for conversation delivery and history. They are encrypted in transit, but are not end-to-end encrypted. Push tokens, installation identifiers and relevant device/app information are used for notifications. Notifications can show a sender, photo and message preview according to your app and Android settings.

Chat heads are optional and require Android’s “Display over other apps” permission. They display Tuki conversations and allow replies above other apps. This feature does not read the content of other apps. You can disable chat heads in Tuki or revoke the overlay permission.

Supported notifications offer Reply and Mark read. Replies use your signed-in account; a pending reply may be kept in private device storage for retry until sent or cleared. Drafts, queued messages and cached content are account-scoped on the device. Signing out clears native notification reply state. Notification actions do not create a different messaging audience.

4. Service providers & transfers

• Google/Firebase: authentication, database, hosting, push messaging and Crashlytics.
• Cloudinary: newly uploaded profile avatars and cover images. The database stores their HTTPS delivery URLs. Legacy inline images and shop images may remain in the database until changed or removed.
• Render: notification, photo-processing, moderation and account-cleanup services.
• Map and direction providers: requests needed for map tiles, place searches and directions. These requests can disclose the map area or locations involved and network/device information to the provider.

These services may process information on servers outside your country. We use them to operate Tuki. User-selected sharing also makes content available to the people or audience you choose. We do not use these features to sell your personal information or create advertising profiles. This website does not add advertising or analytics trackers; sign-in uses Firebase authentication storage. Hosting providers process standard connection information to serve pages.

5. Diagnostics & device storage

Firebase Crashlytics collects crash logs, stack traces, installation identifiers and relevant device/app diagnostic information in supported native builds. Our custom diagnostic events include bounded timing and feature events for app startup, resume, errors and chat/photo operations. They exclude message text, names, photos and GPS coordinates. Crash collection is enabled in the current native app without an in-app opt-out. To investigate interrupted location sharing, Tuki also sends account-linked operational reports to its private Firebase database when the app is active. Supported newer builds also report from the native location service and its recovery events while the app screen is closed. Android may run a scheduled, report-only diagnostic check even when the location service is not running; this check does not start location sharing or collect a new GPS point. Its timing depends on Android and network availability. These contain location and notification permission/settings states, service and recovery status, bounded event ages and app/update versions, not GPS coordinates or messages. Only the latest app observation, latest native background observation and last reported interruption are retained per account; they are removed during account deletion. An old report is not evidence that the phone is currently online.

Tuki uses bounded local caches, drafts and queues to reduce repeat downloads and recover interrupted work. Clear image cache removes cached web images/resources, not your account or messages. Android app backup is disabled for app-owned data; these features do not back up your content to the developer’s personal Google Drive.

6. Retention & account deletion

Request deletion in Tuki Settings or on our account deletion page, including if you have uninstalled the app. After a verified request is accepted, it is queued for cleanup. The cleanup worker disables the account, removes associated profile, contact, sharing, message and managed photo data, removes owned circles and cleans up membership/authored content in other circles, then deletes the sign-in account. Interrupted work resumes from a checkpoint.

Processing is automatic while the service is available; the time depends on the amount of data and service availability, so there is no guaranteed completion time. Acceptance is not confirmation that all data is already gone. Email support to check progress or if a request appears delayed. An email request requires ownership verification. A website request cannot erase cached or local-only data from an offline phone; clear that data in the app or Android storage settings. Copies or screenshots kept independently by recipients are outside our cleanup control.

7. Security & your choices

HTTPS/TLS protects communication in transit. Authentication and access rules restrict service access; no system can promise absolute security. You can change your profile, choose sharing audiences, stop background sharing, clear Timeline history, control notifications/chat heads, block or report users, and request account deletion. Revoke Android permissions in your device settings when you no longer want a feature to use them.

Do not use Tuki to track a person without their consent. Read our safety and child protection standards. If someone is in immediate danger, contact local emergency services.

8. Contact & policy updates

For privacy, access, correction, retention or deletion questions, contact designer.bidyut@gmail.com. Tuki / Bidyut Kumar (Xosho), Bangladesh. We update this page when our practices change and show the revision date above.