1. Who operates TAHT
NAIZA LLC owns, develops and operates TAHT. For questions about personal information, account data or this policy, contact tahtgame@gmail.com or +998501020572.
2. Information we process
- Phone number, name and account identifiers.
- Project name, logo, description and public links entered by the user.
- Product and service offers, community ratings linked to an account, and moderation records.
- Session cookies, a device identifier used for security and request identifiers.
- Purchase intent, transaction and refund records, and moderation audit records.
- First-party visit statistics and optional Datafast analytics, described below.
If you grant location permission, your coordinates are used in your browser to center the map. They are not sent to the TAHT database.
3. Use and retention
Information is used to protect accounts, display projects on the map, prevent fraud, handle support requests and keep records required by law.
Account information is retained until the user deletes it or while it is needed for the service. Transaction and security audit records are retained for the period required by legal obligations.
4. Hosting and service providers
The stated primary server location is Hetzner infrastructure in Finland. The existing service rules make overseas data storage conditional on formal confirmation of the cross-border protection requirements under Uzbekistan law.
Map sources include OpenStreetMap and Protomaps. Hosting providers and, when connected, SMS and payment providers may process only the information needed for their services.
The legal basis for overseas processing remains a launch prerequisite; this page does not claim that this prerequisite has been completed.
5. Your account and choices
Through the account cabinet, users can download a copy of their data, edit their project information, close sessions and delete their account where there is no legal restriction.
For correction requests, information about use of your data or withdrawal of consent, contact tahtgame@gmail.com. Include the relevant project or Request ID if available; do not send passwords or SMS codes.
6. Optional visit analytics
With your permission, TAHT uses Datafast to count visits to public pages. Datafast uses visitor and session cookies and browser storage; requests include a pseudonymous visitor ID, the public page path, device/browser information and, when it passes our checks, a referring site or public TAHT page. Like other network requests, these requests expose your IP address to the provider.
We do not connect account profiles, phone numbers, SMS codes, project details, payments or revenue to Datafast. Map coordinates, plot selections and query parameters are excluded from the tracked page path. Moving or zooming the map is not a new pageview. Visits with a potentially sensitive referrer are not tracked. Account/admin pages and local previews are excluded.
Analytics is optional. Declining does not limit the game. This browser remembers your choice for up to 180 days; you can change it below. Revoking permission stops further tracking and clears Datafast identifiers in this browser, but does not recall information already sent. Do Not Track and Global Privacy Control signals also prevent tracking. Essential account/security functions and TAHT's separate first-party operational statistics are unaffected.
Datafast is an external provider. See its privacy policy. Questions or requests about information already collected can be sent to TAHT using the contact details above.
7. Official statistics display
The map embeds an official Datafast widget from datafa.st and links to TAHT's public Datafast dashboard. The widget displays realtime provider statistics; TAHT does not generate its figures. This external content loads separately from TAHT's optional pageview tracker, so declining pageview tracking does not remove the statistics display.
Loading the widget contacts Datafast and exposes ordinary network information such as your IP address and browser information to that provider. The embed uses a fixed address and a no-referrer policy: TAHT does not append map coordinates, selected plots, account data or API credentials. Datafast controls its embedded content and processes requests under its own privacy policy.
The compact total-visits label is retrieved through TAHT's same-origin, aggregate-only endpoint. TAHT's server requests Datafast's all-time session total and sends the browser only the aggregate number, availability status and update time; the Datafast API credential is never sent to the browser. No account, phone, project, payment or selected-map data is included in that request.
The public statistics dashboard is viewable without a TAHT account. “All-time” begins when Datafast tracking for TAHT began and may exclude declined or blocked analytics. One visitor may create more than one session, and reporting periods and metric definitions may differ from the realtime widget.
8. Offers and community ratings
Public offer cards display information supplied by project owners and lead to their external websites or messengers. Those services have their own terms and privacy practices.
Ratings are account-linked user opinions, not verified purchases. TAHT shows only eligible aggregate counts and, after three votes, an average; public responses do not identify voters. Ratings do not buy or award game titles. You can withdraw your rating. The withdrawn record and moderation flags are retained to prevent repeat-voting abuse and are removed with account deletion; separate security audit records follow the retention policy above. Your data export includes your rating records. Contact support to dispute suspicious ratings or a moderation decision.
9. Optional offer interest statistics
The analytics choice also asks permission for TAHT's separate, first-party offer measurements. Earlier Datafast-only or owner-only analytics permission does not authorize public totals; TAHT asks for a new choice. Events collected under those earlier choices remain private, even if the project owner later enables public clicks. Declining has no effect on viewing offers, following their links or using the game.
With permission, a random browser identifier is stored locally and replaced on the next eligible interaction on a new Tashkent calendar date. TAHT receives the offer and project IDs, event type and this identifier. It stores a project-and-day-scoped hash, never the raw browser identifier, phone number, destination URL or precise location in the offer metrics table. Ordinary server security logs are separate. Revoking permission removes the local identifier and stops future measurement; it cannot recall an event already sent.
A view requires at least half of a card to be visible for one continuous second in a visible browser tab. A link click means activation of the offer's link, not successful delivery, a customer, payment or sale. Each event type counts once per offer and browser per Tashkent calendar day. Signed-in project owners, administrators and banned accounts are excluded; signed-out owners cannot be recognized. Browser changes, cleared storage, declined consent, blockers and automation affect accuracy. These are not unique-person counts or verified commercial results.
Only the project's owner can access the per-offer 7- or 30-day report. The public project passport also shows the sum of current offers' views over 30 days, using only events explicitly consented to public aggregation. Aggregate link clicks are hidden by default; the project owner can make that 30-day total public or hide it again in the cabinet. Public responses never contain per-offer click counts or visitor identifiers. Turning visibility off excludes clicks from subsequent public responses but cannot retract numbers someone already viewed. Public counts are not unique project visitors: viewing three different offers can contribute three views. These measurements do not feed Datafast, Nufuz, ratings, titles or financial records. Reporting is limited to the latest 30 calendar dates and begins when this feature is enabled; older visits are not backfilled. Expired measurement rows are deleted on the next accepted measurement or authorized statistics request; if the service is idle, older rows may remain until that next request. Removing an offer or deleting its project/account removes its measurements.