Privacy policy
This policy describes what the Analytics prototype does as of the revision date.
1. Who processes the data
Individual Entrepreneur (YaTT) TASHPIKOV SVYATOSLAV OLEGOVICH, Uzbekistan (the “owner”). Contact for data questions: mouseakabug1@gmail.com.
2. What this policy covers
- The Analytics software and the Meta app Dashboard-bot, through which it receives Instagram and Facebook Messenger events.
- This website (section 10).
Analytics is in technical testing and is not offered to customers. Events are received from the owner's test accounts. Data is stored only for test participants who sent a one-time code themselves.
3. How data reaches the software
When someone messages a connected Instagram account or Facebook Page, Meta sends an event (webhook). The software verifies its signature and then decides whether to store it:
- The sender is not a test participant. The event is acknowledged to Meta and dropped. Its content stays only in memory during processing. What remains is a daily count: channel, reason, event class, and whether an ad referral was present. The person's ID, the message ID and the text are not stored. An ad ID is recorded only if that ad is already on the list being tested.
- The sender is a test participant. The data in section 4 is stored.
To join, a person sends a one-time code as a message. The text of that message is not stored; only a hash of the code is kept.
4. What is stored about participants
| Data | Contents | Purpose |
|---|---|---|
| Identifiers | The ID Meta issues for a person on a specific account (IGSID or PSID); account or Page ID; channel | Telling participants and conversations apart |
| Messages | Text, title of a tapped button, message ID and type, time. The text of outgoing echo messages is not stored | Testing event intake, identifying an inquiry |
| Ad referral | If Meta provided it: ad ID, source type, URL, click ID, ad headline and body, media type, the original referral object | Linking an inquiry to an ad |
| Derived data | Conversation counters, inquiry status, automated intent assessment, draft reply, dry-run conversion event | Testing the report |
| Entered by hand during testing | Sale: amount, currency, order reference | Testing the calculation of advertising results |
| Technical records | Event key, event structure without values, action log, participation expiry | Protection against duplicate processing, oversight |
The software does not request or store Instagram or Messenger profile names, usernames or photos. If someone writes personal details in a message, they become part of its text. The WhatsApp channel is not connected, and no data from it is processed.
When testing the report, advertising statistics (ad IDs, days, spend) may be uploaded by hand from a CSV file. They contain no data about individual people.
5. Automated processing
Intent is assessed with fixed rules. No third-party language models are used. The assessment has no legal effect on anyone. Draft replies stay in the local database: the software does not send messages to people.
6. Basis for processing
Participation in the test is voluntary: data is stored only after a person has sent a one-time code themselves. A participant can withdraw consent and request deletion of their data.
7. Who receives the data
- Meta is the source of the events. The Conversions API runs in dry-run mode, so nothing from the database is sent to Meta.
- Cloudflare. During tests on a local computer, events may pass through a Cloudflare tunnel.
Both companies are registered outside Uzbekistan, so data may be processed outside it. Data is not sold and is not used to show ads.
8. How long data is kept
The table shows software settings, not guaranteed completion times.
| Data | Setting |
|---|---|
| Message text and event structure | Data older than 30 days is cleared. This runs once a day, only while the event receiver is running |
| Permission to participate | 7 days, unless another period is set when adding the participant |
| Unused one-time code | 30 minutes, unless another period is set (4 hours at most) |
| Counts of dropped events | Records older than 30 days are cleared while the event receiver is running |
| Identifiers, ad referrals, inquiry statuses, sales, action log | No automatic clearing. Kept until deleted on request or when test data is cleared |
9. Data protection
- Only events with a valid Meta signature are accepted.
- The report dashboard is available only from the owner's computer or with an access token.
- The Meta token used to connect an account is not stored.
Data is kept in a SQLite database file on the owner's computer. There is no permanent server. Database encryption and backups are not implemented.
10. This website
The site is static. It has no forms, cookies, analytics counters or advertising trackers, and loads no external scripts or fonts. It is hosted on Cloudflare Pages: when a page is opened, Cloudflare technically processes request data, such as the IP address and browser details, under its own privacy policy. If you email us, your address and message are used to reply.
11. Your requests
You can ask what data about you is stored, ask for it to be corrected or deleted, and withdraw consent to take part in the test. This policy does not limit any rights you have under applicable personal data law. How to send a request is described on the Data deletion page.