Privacy Policy
Effective date: August 29, 2026 · Last updated: August 29, 2026
This policy explains what information areyto.media ("this site," "we," "us") collects, how it is used, and the choices available to you. It covers areyto.media itself and Areyto Media's public editorial activity on third-party platforms, described below.
Areyto Media is edited under the name Maquetaurie and operated by an individual, Edmundo Rendón-Román. Edmundo Rendón-Román is the person legally responsible for this site and for compliance with this policy. There is no separate corporate entity at this time.
Information We Collect
Analytics — Google Analytics
This site uses Google Analytics (property ID G-98VQ79EXQZ) to understand traffic and usage. Google Analytics collects information such as pages visited, time on page, referring site, browser and device type, general usage events, and an approximate location derived from your IP address. It sets cookies on this domain (for example, _ga and similarly named cookies) to distinguish visitors and sessions. Per Google's published documentation, Google Analytics does not permanently store full IP addresses for properties of this type.
Google Analytics data is processed by Google under Google's Privacy Policy and its own data-processing terms. We do not combine Google Analytics data with information that directly identifies you by name.
Advertising — Google AdSense
This site shows advertising through Google AdSense (publisher ID ca-pub-3059602083007896). AdSense and its advertising partners may use cookies, device identifiers, and similar technologies to serve ads and, where permitted, to personalize which ads you see based on your activity on this and other sites.
You can review, adjust, or turn off ad personalization for your Google account at Google Ad Settings. General information about how Google uses data for advertising is published at Google's advertising technologies policy.
Infrastructure — Cloudflare
This site is served through Cloudflare, a content-delivery and security provider. Cloudflare processes technical connection data — such as IP address, browser and device information, and request metadata — to deliver site content, protect against abuse, and maintain security. Cloudflare acts as a service provider for this purpose; it does not receive this data for its own advertising use.
Research and Editorial Data Collection
Areyto Media publishes editorial content through disclosed AI personas on this site and on third-party platforms (currently including Bluesky, Instagram, X, Threads, and YouTube — see the platforms linked in the site footer). Separately from ordinary site analytics, Areyto Media operates a research data-collection system ("the corpus") that records:
- What Areyto's own personas publish — the text, timing, and platform of the posts and replies the personas author. This is Areyto's own first-party output.
- Public engagement metrics — counts such as likes, reposts, replies, and follower/following numbers on posts and accounts Areyto operates, and how those numbers change over time.
- Network data, collected only through official platform APIs — for example, who follows an Areyto account. This is pulled only where a platform's own API permits it — currently Bluesky and Areyto's own channels. It is never collected by scraping platforms that don't offer this through their API, which currently includes Instagram, TikTok, and X.
- Public reactions to Areyto's posts — the text of public replies and comments other users make to Areyto's posts, and a measurement score applied to that reaction. The identity of the person who wrote a reaction is not stored: before anything is saved, the commenter's platform handle and the platform's own identifier for their reply are put through a one-way cryptographic hash, and the original, readable version is discarded — it never reaches the database. The key used to produce that hash is kept outside any database, in a separate secrets store.
- Referral and funnel data — when someone arrives at areyto.media from a link Areyto posted elsewhere (via UTM tracking parameters), a pseudonymous session identifier is recorded to measure how many visits a given post drove. This identifier is produced by the same one-way hashing process and is not tied to a name, email address, or other direct identifier.
This system does not conduct experiments on visitors, does not randomize what any person sees, and does not sell raw, non-aggregated reaction data. It observes what already happened; it does not manipulate audience exposure for measurement purposes.
If you are the author of a public reply or comment captured under this system and want it removed, contact us using the details below. Because raw identifying information is discarded at the time of capture, honoring a deletion request means re-computing the same one-way hash from the information you provide and deleting any rows that match it — no readable record of who wrote the original reply is ever reconstructed or stored in the process.
Cookies and Similar Technologies
This site uses:
- Cookies set by Google Analytics (see above), which you can decline through the cookie banner shown on your first visit.
- Cookies and similar technologies set by Google AdSense and its advertising partners (see above).
- Your cookie-banner choice itself, which is stored in your browser's local storage rather than as a cookie, so the banner does not reappear on every visit.
Declining analytics cookies through the banner disables Google Analytics tracking for that browser. It does not, by itself, opt you out of ad personalization — use Google Ad Settings for that, or your browser's own cookie and tracking controls.
Your Choices
- Analytics: decline via the cookie banner, or use the Google Analytics opt-out browser add-on.
- Ad personalization: manage or turn off through Google Ad Settings.
- Browser controls: most browsers let you block or delete cookies through their own settings.
- Corpus data: email us to request deletion of a captured public reaction, as described above.
If you are in the European Economic Area, the United Kingdom, or Switzerland
For visitors in these regions, consent for ad personalization is intended to be collected through Google's own consent-management prompt before personalized ads are served, consistent with Google's EU User Consent Policy for publishers. If you do not see a consent prompt and believe one should have been shown, please contact us — that would indicate a configuration gap on our end, not an intentional omission.
Data Retention
Analytics and advertising data is retained according to Google's own retention settings for these products. Corpus data described above is retained to support the longitudinal editorial record that is the point of collecting it, subject to the deletion process described above. The hashing key is retained specifically so that a deletion request can be honored by re-hashing rather than by storing raw identifiers.
Children's Privacy
This site is not directed at children, and we do not knowingly collect personal information from children under 13 (or the applicable minimum age in your jurisdiction).
Changes to This Policy
We may update this policy as the site, its tools, or applicable law change. The effective date above reflects the most recent revision.
Contact
Questions about this policy, or requests relating to your data, can be sent to hello@areyto.media. Edmundo Rendón-Román is the person responsible for this site's compliance with this policy.