AI Flow Finder
Your information

Privacy policy

Last updated October 15, 2026.

Who is responsible for your information

Legal operator: MEYER BELZITI GIANLUCA
Spanish tax identification number (NIF): 05459553C
Business and postal address: Calle Federico García Lorca 2, Portal 10, 2B, 28770 Colmenar Viejo, Madrid, España
Email: info@aiflowfinder.com

The operator above is the controller of personal information processed for AI Flow Finder. Use info@aiflowfinder.com for privacy questions or requests.

Reading and saving workflows

You can read the directory without an account. Saved workflow identifiers stay in your browser’s local storage and are not sent to us. Clear your browser’s site data to remove them. Search and filter choices appear in directory page URLs. Guide sharing buttons use only the public guide title and canonical link, without campaign or test labels. Copying writes that link to your clipboard; choosing an external sharing service opens that service. We do not read your clipboard or contacts.

The directory currently adds no advertising pixels, third-party analytics scripts, remote fonts, or email tracking pixels. Cloudflare processes technical request information, such as IP addresses and browser metadata, to deliver pages and protect the service. Form abuse controls use limited security records; they are not used to build advertising profiles.

Limited campaign measurement

For links carrying our approved X campaign labels, our own script makes one best-effort request when a visible page is first opened from another site or with no referring page. Reloads, browser back/forward navigation, and navigation between our own pages are excluded when the browser exposes that information. We store a UTC day, one approved campaign label, a test flag, and an aggregate entry count in this project’s Cloudflare D1 database. Known bots are excluded, but blocked requests, repeat entries, and undetected bots can affect counts. These are observed entries, not unique visitors, people, or all page views.

For a new newsletter request from an approved campaign, we also keep a separate measurement record linked to the subscription record: request time, first confirmation time when confirmed, campaign label, and test flag. This lets us compare new request cohorts with observed campaign entries. Existing subscribers and repeat confirmations do not become new conversions. Test activity is reported separately. Campaign labels come from links and do not prove that X caused a subscription.

This measurement adds no cookies, local or session storage, visitor IDs, fingerprints, advertising pixels, third-party analytics SDKs, or analytics records containing IP addresses or browser metadata. The newsletter form works independently of the measurement request.

Newsletter consent and confirmation

Links in our X launch campaign may include fixed campaign labels in the URL. We carry only approved labels between pages on this site. If you request the newsletter, we keep those labels with the consent record to associate the request with that campaign. They are campaign names, not visitor identifiers. Other query parameters are not saved as campaign attribution. The labels do not create visitor identifiers or a browsing profile, add cookies or browser storage, or send campaign data to a third-party analytics service. The limited first-party measurement described above is kept separately.

When you request the newsletter, we process your email address, consent wording/version, consent time and source, confirmation status, and unsubscribe status. For delivery, we also process issue and provider message identifiers, send attempts and timestamps, and delivery, bounce, or complaint outcomes. We use this information to confirm your request and send the AI Flow Finder newsletter, including any clearly labeled sponsor placements, on the basis of your consent.

Newsletter consent is optional: you can use the directory without subscribing. The checkbox is unchecked by default and must be selected to request a subscription. You join the active mailing list only after confirming your address using the confirmation email. Opening a confirmation page alone does not subscribe you. Confirmation links expire after 24 hours. A pending request is not permission to send the newsletter.

We send one edition with three workflows on Tuesdays at 10:00 a.m. New York time (America/New_York, including daylight saving time). This describes the intended schedule, not a guarantee that every issue will arrive at that exact time. We do not add addresses from other businesses’ lists, sell subscriber addresses, or share a subscriber list with sponsors.

You can withdraw consent at any time through the unsubscribe link in an issue or by emailing us. Withdrawal does not affect processing that was lawful before you withdrew. Unsubscribing does not require an account or a payment.

We check consent and delivery suppression before sending. Authenticated delivery notifications help us record delivery outcomes and stop further messages to addresses associated with a bounce or complaint. To retry an interrupted send without changing its content, we may keep an encrypted copy of the outgoing request, including the recipient address, email content, and personal unsubscribe link. Subscription and delivery metadata are stored separately from that encrypted copy.

Workflow suggestions and contact messages

If you use the suggestion form, we process the workflow details, source link, your agreement to review, and any optional contact email to assess the suggestion and answer related questions. The form’s availability is shown on the page. Suggestions are reviewed before publication; submitting one does not join the newsletter. We do not publish a contributor’s contact email as part of a guide.

We process ordinary contact and correction messages for our legitimate interests in responding to requests and maintaining the directory. Sponsorship inquiries are handled by the operator to respond to your request and, where relevant, discuss a possible agreement. Do not send secrets, private customer data, or material you are not entitled to share.

Sponsorship payments

Sponsorship payments are processed on Stripe’s hosted checkout. Stripe receives the contact, billing and payment details entered there. We receive payment and transaction records and the contact or billing details needed to reconcile the purchase and provide the placement. After payment, you send your logo, short message, destination link and scheduling preferences to our contact mailbox for review and coordination. We do not receive or store full card numbers on this website. We use these records to perform the sponsorship agreement and meet applicable recordkeeping obligations. Buying a sponsorship does not subscribe you to the newsletter.

Service providers

These providers may process information outside the European Economic Area, including in the United States. Their published terms describe their processing and applicable international-transfer safeguards: Cloudflare’s data processing terms, Resend’s privacy policy, and Microsoft’s privacy statement. Contact us for further information about safeguards applicable to your data.

Clicking an external tool or source link takes you to a separate provider with its own terms and privacy practices. This directory does not automatically send your workflow inputs to an AI tool.

Retention and security

We retain subscription, consent, and suppression records as needed to manage your choices, demonstrate consent or withdrawal, and prevent further unwanted mail. These records and delivery metadata currently have no fixed automatic expiry; you can contact us to request a review or deletion where applicable. Suggestions and correspondence are kept as needed to handle the request, resolve issues, and meet applicable recordkeeping obligations.

Campaign entry counts and the separate campaign measurement records become eligible for bounded cleanup after 90 days when analytics processing runs. This does not erase the separate newsletter consent, withdrawal, suppression, or delivery records. Cleanup eligibility does not guarantee deletion at an exact time.

Expired, never-confirmed requests without a withdrawal history become eligible for cleanup after 30 days of inactivity when signup processing runs. Expiry of the 24-hour confirmation link does not itself erase a request.

Encrypted retry copies become eligible for removal after a send is finished or stopped and its record has remained unchanged for 30 days. Records used to enforce sending limits become eligible after 62 days, and operational run logs after 14 days. Cleanup works in limited batches when processing runs, so these are eligibility periods rather than guaranteed deletion on an exact day. Delivery metadata and suppression records are retained separately; removing an encrypted retry copy does not erase those records.

Access to project records is restricted to the operator and the service providers needed to run the site. Do not include sensitive information in a submission or email. No service can guarantee absolute security.

Your rights

Where applicable, you may request access, correction, deletion, restriction, portability, or object to processing based on legitimate interests. You can withdraw newsletter consent at any time. Email info@aiflowfinder.com or write to the postal address above. We may ask for proportionate information to verify that the request concerns your own data.

You can lodge a complaint with the Spanish Data Protection Agency (AEPD) or another competent supervisory authority. We do not use subscriber or suggestion data for decisions with legal or similarly significant effects made solely by automated processing.

Changes

We update this policy when the services or data practices change. The date above identifies the current version.