Privacy policy

Controller and contact

The data controller is Luca Gabriel Gil Cuello, an individual based in Argentina, trading as Feedmakers. For questions or to exercise your rights, write to hello@feedmakers.app.

What data we process

• Account: email address, name and password (encrypted; we never see it) and, if you give it to us, your WhatsApp number.
• Businesses: name, Instagram handle, logo, reference posts and brand guides you upload, creative agent rules and caption languages.
• Content: the briefs you write, your messages to the planner, the audio you dictate to it (we turn it into text and don't keep it), the files you upload (product photos and planners to import), and the images and texts generated for you.
• Connected Meta accounts: when you connect Facebook or Instagram we store your Meta ID and name, the list of Pages and Instagram professional accounts you can access, the permissions you granted, and the access tokens needed to act on your behalf. For what you publish from Feedmakers, we read the counts Meta reports for the 30 days after it goes out — likes (or reactions, on Facebook), comments, saves, shares and reposts — and, on Instagram, reach and views, and store them with the post.
• If you use those features, we also process: the comments on what you published from Feedmakers (we read them from Meta each time you open the Comments tab and don't store them); your Instagram account's statistics — followers, reach, views and accounts engaged — (we read them when you open Metrics and don't store them); the posts you choose to bring from your own account or from another public professional account, which we store as references for your brand; and the name, price, description and photo of the product from your Meta catalog that you pick to create a post.
• Free tools (feedmakers.app/tools): almost all of them run in your browser and send us nothing. The YouTube thumbnail one reads the public data of the video you paste and its channel — title, channel, its images and, when available, the video's and the channel's descriptions and the channel picture —, receives the text you type and the photo of the person you upload, if you upload one, and, to count the day's thumbnails, stores a code made from your IP address (not the address itself) or your account ID, which is deleted the next day. The thumbnails are not stored.
• Credits, payments and usage: credit balance, generations and their cost, publications and schedules, your plan, and the amounts and references of your payments. You enter your card or payment account details on Stripe or Mercado Pago, and they never reach us.
• Meetings: if you book a meeting with us, your name, your email, the note you leave and your time zone.
• Technical data: how you use the site and the app (pages you visit, what you click and session recordings, with what you type into fields hidden), where you first came from (the campaign, the referring site and the landing page), which we store with your account, and server error logs.

Why we use it

• To provide the service: generate artwork and copy, save your posts, publish or schedule to your accounts when you ask, show you how the posts you published from Feedmakers and your account are doing, and reply to or hide comments when you ask.
• To charge your plan and packs, and deduct the credits you use.
• Security, abuse prevention and support.
• To improve the product: understand which parts get used and where people get stuck.
• To measure our ads on Meta: know whether a visit from an ad ends in an account, a meeting or a payment.
• To contact you about your account.
• To email you to help you get started, for example if a few days have passed and you haven't created your first post yet. Every one of those emails includes a link to unsubscribe.
• To message you on WhatsApp, if you left us your number, to help you with your account. It is optional and you can delete it at any time from My account.

We do not sell your data or use it for third-party advertising.

Facebook and Instagram data

We use the data we receive from Meta solely for these features: showing you your Pages and accounts and letting you assign each one to a business; publishing the content you create and approve, at the time you choose; showing you how what you published from Feedmakers and your Instagram account performed; listing the comments on those posts so you can reply to or hide them; bringing in, as references, the posts you choose, your own or from another public professional account; and creating a post from a product in your catalog. We never publish, reply or hide anything without your action, we do not read your private messages, and we do not sell that data or use it for advertising.

To provide those features, some of that data goes through the providers in the next section: the text of a comment and your post's caption go to OpenAI when you ask it to suggest a reply; the images you bring from Instagram go to OpenAI to read their style and to Replicate when they serve as references for generating; and PostHog session recordings may show what appears on screen. We do not share Meta data with anyone else. We comply with Meta's Platform Policies.

You can disconnect Meta at any time from Connections: we immediately delete the tokens and the metrics of those accounts. The images you brought in as references stay in your brand until you delete them. You can also revoke access from your Facebook account settings (Apps and websites).

Who we share data with

We work with providers that process data on our behalf, only to deliver the service:

• Supabase: database, authentication and file storage (servers in São Paulo, Brazil).
• DigitalOcean: the server that hosts the site and the app, managed with Laravel Forge (New York, United States). Requests to the site go through it, and the server logs are kept there.
• PostHog: usage analytics and session recordings (United States). It receives your account ID, your plan and what you do on the site and the app, with a recording of what is on screen; what you type into fields stays hidden.
• OpenAI: writing the copy, the art prompt and the draft; the planner; reading your brand guides, your reference posts, your business's website and the planners you import; checking the text drawn in each piece; the reply it suggests for a comment; and the ideas for YouTube thumbnails. It receives your brief, your business details, your messages to the planner, the audio you dictate to it so it can be turned into text, the documents you ask it to read, your references (including the ones you bring from Instagram) and product photo (at low resolution), the generated pieces and, when you ask for a suggestion, the comment and that post's caption; for a thumbnail, the video's and the channel's data, the image you pick, the photo of the person you upload, the channel picture and your text.
• Replicate and the model providers that run through it (Google, ByteDance, OpenAI): generating, fixing and animating the artwork, and YouTube thumbnails. They receive the prompt, your product photo, your references and, to animate it, the piece; for a thumbnail, the video image you pick or the photo of the person you upload.
• Meta Platforms: publishing to Facebook and Instagram, the replies and hidden comments you ask for, and reading what is described under “Facebook and Instagram data”. In addition, the Meta pixel records the feedmakers.app pages you visit, and our server tells Meta (Conversions API) when someone creates an account, books a meeting or pays, to measure our ads. In those notices your email and your account ID are sent as SHA-256 hashes, never in plain text; a booking also carries the pixel cookies and the page you booked from, and a payment carries the amount and currency.
• Stripe: charging plans and packs. It receives your email and your account ID; you enter your card details on Stripe.
• Mercado Pago: charging plans and packs in Argentine pesos. It receives your email and a reference with your account ID; you pay on Mercado Pago.
• Resend: sending account emails, such as the confirmation and the get-started ones, and the messages you send us from the in-app help (United States). It receives your email address, your name and the message text.
• Google: our email (Google Workspace), where we receive what you write to us, and our calendar (Google Calendar and Meet): if you book a meeting, we create the event with your name, your email and your note, and Google sends you the invitation.
• Telegram: internal notices to the team. It receives your name and email when you create an account; your name, email and note when you book a meeting; and your name, email, plan and amounts when there is a charge.

Some of these providers are outside Argentina; by using Feedmakers you accept that international transfer, made with providers offering security and confidentiality guarantees.

Requests from authorities

If a public authority asks us for personal data, we check that the request is lawful and that the authority has jurisdiction; if it is not, we refuse or challenge it; we disclose only the minimum data needed to comply; and we keep a record of the request, our response, the legal reasoning and the people involved.

Retention

We keep your data while your account is active. Meta tokens and the metrics of those accounts are deleted when you disconnect. Images sent through Replicate to the models are kept on their servers for a limited time (up to 24 hours) to allow retries. When you delete your account from the app we erase your data immediately (by email, within 30 days), except what we must keep by law (for example, billing records).

Your rights

You can access, correct, update or delete your data and request its portability by writing to hello@feedmakers.app. We reply within 10 business days. How to request full deletion of your account is explained on the Data deletion page.

Argentina's Agencia de Acceso a la Información Pública (AAIP), the authority under Law 25.326, handles complaints about data-protection breaches. If you are in the European Union you also have the rights under the GDPR, including lodging a complaint with your supervisory authority.

Cookies

We use the strictly necessary cookies (the session cookie, to keep you signed in, and the language cookie), a PostHog analytics cookie that helps us understand how the product is used, and the Meta pixel cookies, which measure whether a visit from our ads ends in an account, a meeting or a payment. Businesses' public pages (feedmakers.app/@username) don't load the pixel.

Security

Data travels encrypted (TLS) and is stored with providers that enforce access controls; Meta tokens are only used from our servers and never reach the browser. No system is infallible: if we detect an incident affecting you, we will let you know.

Minors

Feedmakers is intended for people aged 18 or over who run businesses. We do not knowingly process data from minors.

Changes

We may update this policy; the new version will be published on this page with its date. If the change is material, we will email you.