1. What this policy covers
This policy covers retivai.com, its public submission form, and the private editorial review tools used to operate the directory. External products and repositories linked from RetivAI apply their own privacy policies.
2. Information you provide
When you submit a product or correction, we receive the product name and URLs, description, category, interaction method, claimed technology, evidence, optional notes, and your email address. New-product submissions also include public URLs for a logo and primary screenshot, optional additional screenshots, demo video or media kit, and your media-permission confirmation. No public account is created. Your email and internal review notes are not published.
If you use the feedback page (/feedback), we receive the message you write (up to 1,000 characters), an optional type, an optional email address that you choose to leave for a reply, and the page you came from (its path only). To limit abuse, your IP address is immediately turned into a salted one-way hash and only the hash is stored. The message, type and page, but never your email address, are forwarded to the site owner’s private operations notification channel so that a person can read it; the email address is visible only in the protected admin.
3. Information collected automatically
Our infrastructure may process request metadata such as IP address, user agent, timestamps, requested pages, response status, and security signals. For submission rate limiting, an IP address is immediately transformed into a salted one-way hash; RetivAI stores the hash rather than the raw address in the submission record.
Your analytics choice is stored in your browser under retivai_analytics_consent_v1. This first-party preference is not an advertising identifier and is used only to remember whether analytics (Google Analytics and RetivAI’s own event log, described in section 5) may run.
The submission preflight requests the public product, evidence, source-code, logo, and screenshot URLs you provide and records response status, redirects, selected public metadata, matching technical terms, and—where relevant—public GitHub repository metadata. It does not sign in to those destinations or bypass access controls. Optional demo-video and media-kit URLs are stored for human review but are not automatically opened by the preflight.
4. Turnstile and infrastructure
RetivAI uses Cloudflare to deliver and protect the site and plans to use Cloudflare Turnstile on the production submission form. Cloudflare processes technical data to provide those services under its own policies. The launch architecture does not use advertising cookies, behavioral profiles, or cross-site remarketing.
5. Analytics and your choice
RetivAI uses Google Analytics 4 only after you select “Accept analytics.” Before that choice, the Google tag is not loaded and no analytics request is sent to Google. After consent, Google Analytics may process the page URL and title, referring page, approximate location, browser and device information, and visit or session measurements. It uses first-party cookies such as _ga and _ga_* to distinguish users and sessions.
RetivAI keeps Google advertising storage, advertising user data, ad personalization, Google Signals, and remarketing disabled in the site configuration. You can decline initially or reopen “Analytics choices” in the footer at any time. Withdrawing consent disables further collection and removes RetivAI’s Google Analytics cookies from your browser. Google processes analytics data under its privacy policy.
Separately, RetivAI keeps a cookie-free daily visitor count and a cookie-free page-view count. When a page loads, and again each time you move to another page on the site, a small request carrying only the page path is sent to RetivAI; the site counts it by day and page path and against the same daily key described next. On your first page of the day it also records that page path, the referring website or utm_source tag, and a traffic channel worked out from them (for example search, social, or direct), together with the country code Cloudflare derives from your connection, a device class (mobile, desktop, or tablet), and a key derived from your IP address and user agent with a secret that changes every day. The key cannot be reversed and cannot link your visits across days; no IP address, user agent, cookie, or browser storage is kept for it. Only daily totals by source, channel, landing page, country, and device class, and page-view counts, are reported to RetivAI’s internal operations dashboard, and rows are deleted after 120 days. This count does not depend on your analytics choice.
If you select “Accept analytics,” RetivAI also keeps its own first-party event log, separate from Google Analytics. It sets a random visitor identifier in a first-party cookie (retivai_vid, 180 days) and a session record in your browser’s session storage, and records three kinds of events: a visit (the start of a browsing session), a page view (page path only, without query strings), and a click on a link that leaves RetivAI (only the destination’s domain name, never the full address). Each event also stores the referring website, any utm_ campaign tags on your landing address, country code, device class, operating system and browser family, and a timestamp. No IP address, user agent string, email address, or full URL is stored. Declining or withdrawing consent stops these events and deletes the cookie and session record from your browser. Once you have accepted analytics, that same random visitor identifier is also saved on the day’s cookie-free visitor record, and with your submission record if you submit a product, only so that aggregate funnel counts can tell how many people who visited went on to submit; if you have not accepted analytics, no identifier is saved on either record and the visitor key stays unlinkable across days. Event rows are deleted after 120 days. The events are used only for aggregate counts in RetivAI’s internal operations dashboard.
If we later add advertising, affiliate tracking, or technology that materially changes collection, this policy and any required consent controls will be updated before activation.
6. How information is used
- Review, verify, classify, publish, correct, or decline a submitted listing.
- Contact the submitter about missing evidence or material changes.
- Detect abuse, enforce rate limits, investigate security events, and keep the service reliable.
- Create aggregate operational statistics that do not identify submitters.
RetivAI does not sell personal information.
7. Retention
Feedback messages, with any email address left in them, are deleted after 365 days. Submission and review records may be kept while a listing is active and for a reasonable period afterward to preserve editorial history, prevent repeat abuse, and handle corrections. Rejected or abandoned submissions are reviewed periodically and may be deleted when they no longer serve those purposes. Security and infrastructure logs follow the relevant service provider’s configured retention.
8. Sharing and international processing
Information is shared only with infrastructure, security, and consented analytics providers needed to operate and understand RetivAI, when required by law, or to protect users and the service. Cloudflare and, when you accept analytics, Google may process data in countries other than yours. Public listing facts and source URLs may be published, but submitter contact information is not.
9. Your choices
You can request access to, correction of, or deletion of personal information associated with your submission, subject to legal, security, and legitimate editorial-record needs. Use the correction form or email hello@retivai.com. Include the submission reference when available.
10. Children and changes
RetivAI is not directed to children under 13, and we do not knowingly request their personal information. Material policy changes will be posted here with a revised date.