Maiks.ytAnalytics privacy
Only what the service needs.
Maiks.yt uses an explicit telemetry allowlist. It permits limited operational, security, and aggregate sponsor events instead of recording every visit or interaction by default.
- 01No general page-view tracking
Ordinary visits are not turned into a general browsing timeline.
- 02No cross-site profile
Activity here is not joined to an advertising identity elsewhere.
- 03No sale of personal data
Personal information is not treated as a product for data brokers or advertisers.
- 04Sensitive content stays out
Message text, medical details, and sensitive profile fields are excluded.
Explicit allowlist
Permitted telemetry
These are the event names the current design permits. Being listed means an event may be recorded when the relevant feature is active; it does not mean every event is constantly being collected.
| Event | Reason | Maximum retention |
|---|---|---|
auth.failure | Protect accounts and access | 30 days |
auth.suspicious-link | Protect accounts and access | 90 days |
security.rate-limit | Protect accounts and access | 30 days |
security.token-denied | Protect accounts and access | 30 days |
sponsor.impression | Count promised sponsor visibility | 365 days |
sponsor.click | Count promised sponsor visibility | 365 days |
system.health-failure | Detect service failures | 30 days |
Boundaries
Telemetry is not the same as feature data.
This allowlist excludes private content. Chat message text, private messages, medical information, and sensitive profile data do not belong in these telemetry events.
Account details, linked providers, posts, schedules, and other information deliberately saved to use a feature have their own purpose. They should not be quietly repurposed as general analytics.
Sponsor impressions and clicks are permitted only as aggregate reporting. If no sponsor reporting is active, the allowlist does not require those events to be collected.