01Who we are and what this covers
Render is operated by Render AI, Inc., a Delaware corporation ("Render," "we," "our," or "us"), 2261 Market St, Ste 19827, San Francisco, CA 94114, USA. This policy explains what personal information we collect, how we use and share it, how long we keep it and the choices you have. It covers our website, the Render app, our API and MCP server, and our emails.
It also covers people who don't use Render but whose information we handle for our customers: people a customer reaches with Email Outreach or Direct Mail, people who send a customer leads or messages, and people who comment on a customer's posts and ads. For that information our customer decides how it is used, and we process it on their behalf (see "People our customers reach").
02Information we collect
Information you give us
- Account details: your name, email address and password (stored hashed by our sign-in provider), or your Google profile if you sign in with Google, and your two-step sign-in settings.
- Business details: your Brand Kit, products, website, logo and the answers you give when you sign up.
- Content: files you upload (photos, videos, audio, logos), the projects, ads and posts you make, and your chats with Render's AI agent.
- Your likeness and voice, only if you choose to add them (see "Your voice and likeness").
- Payment details: your card goes straight to Stripe, our payment processor. We see the card brand, its last four digits and your billing details, never the full number.
- Messages you send us, such as support emails and forms.
- The email addresses of teammates you invite.
- Contact lists and mailing lists you upload, and the addresses you enter for postcards.
Information from accounts you connect
- Meta ad accounts, Pages and Instagram accounts, if you use Render Autopilot (see "Meta Advertising Data").
- Google Ads accounts, if you use Google Ads or YouTube Ads (see "Google Ads Data").
- Instagram, Facebook, TikTok and YouTube accounts, if you use social posting (see "Social accounts").
Information we collect automatically
- Usage data: the pages and features you use and when, and what happens when something goes wrong.
- Device data: IP address, browser and device type, operating system and an approximate location worked out from the IP address.
- Cookies, similar technologies and session replays (see "Cookies, analytics and advertising").
Information from other sources
- Business contact details from data providers and public business listings, for Email Outreach.
- Mailing lists from list providers, for Direct Mail.
- Public information on websites you ask Render to read, such as your own site.
- From Meta and Google, whether someone who signed up came from one of our ads.
03How we use it
We use personal information for these purposes. For people in the European Economic Area, the UK and Switzerland, the legal basis for each is in brackets.
- To provide Render: make the ads and content you ask for, run the services you turn on, post and send on your behalf, bill you and support you (to perform our contract with you).
- To keep Render safe and working: verify cards, prevent fraud and abuse, find and fix errors, and enforce our Terms (our legitimate interests).
- To improve Render: understand how features are used so we can make them better (our legitimate interests).
- To communicate with you: service emails about your account, billing, security and the services you use, and tips about getting started, which you can turn off at any time (contract and legitimate interests).
- To measure our own advertising on Meta and Google (our legitimate interests, or your consent where the law requires it).
- To meet legal obligations, such as tax and accounting rules and lawful requests (legal obligation).
Data we receive from Meta is used only as described in "Meta Advertising Data" below, data we receive from Google only as described in "Google Ads Data", and data from your social accounts only as described in "Social accounts".
04How Render uses AI
Render's features run on AI models from the providers listed under "Who we share it with". Each request sends a provider only what it needs to answer: your prompt, the files and brand details involved and, for features that use them, data from accounts you connected. The providers process it to answer Render's request under terms that don't let them train their models on it. We don't train AI models on your content or on data from your connected accounts.
Support: replies to support emails are written by Sam, Render's AI support assistant, and a person on our team steps in when needed. To help you, Sam reads your message and the details of your account that bear on it, using Google's Gemini models on Google Cloud.
07Meta advertising data (Render Autopilot)
Render Autopilot (in our systems, "Render Performance") is the part of Render that creates and manages Meta ads for you. You connect your Meta (Facebook and Instagram) business through Zernio, Render's service provider for connecting to Meta. Meta then shares the data below with Render, only for the business portfolio, ad accounts, Pages, Instagram accounts, pixels and catalogs you choose to share, and only within the permissions you grant.
What we receive from Meta
- An access token Meta issues for your login. Zernio holds it and uses it only to carry out Render's requests. It is never shown to you, to our AI models or to anyone else. A login made earlier through Render's own Meta app gave the token to Render, which stores it encrypted (see "Data Security").
- Who connected: the Facebook user and business portfolio that connected Render, as Meta reports them.
- Your ad accounts: their name, ID, currency, time zone, status, spending limit and amount spent, and settings such as the beneficiary and payer names Meta holds for ads shown in the EU.
- Your campaigns, ad sets and ads: their settings (such as budgets, audiences, placements and schedules), their creative (images, videos and text), their review status, the changes made to them, and their results (spend, impressions, reach, clicks, conversions and similar metrics). Results are aggregated: Render does not receive your customers' individual pixel or Conversions API events.
- Your Facebook Pages: their name, category and website and, for ads that open a WhatsApp chat or a phone call, the Page's WhatsApp number and phone number. We keep the Page's WhatsApp number while the ad account is connected; a business phone you enter yourself stays in your settings.
- Your Instagram account: its ID and username, if you share one.
- Your pixel or dataset: its ID and name, and diagnostics such as event volume and match quality.
- The posts behind the ads Render manages and, only if you turn on comment management, the comments people leave on them on Facebook and Instagram, so Render can sort them, hide spam and scams, and draft replies for you. We store a comment's text with a one-way code in place of the commenter's account; only you and the people you share the ad account with in Render see the text. A comment reaches our AI models without the commenter's name or account, and with any email addresses, phone numbers and @handles in it removed first.
- Leads, only if your ads use a lead form on Facebook or Instagram: what people send through it (usually their name, email address, phone number and answers to your questions). We store leads encrypted and show them only to you and the people you make editors of the ad account in Render (viewers see how many arrived, not who sent them). We email them to you unless you turn lead emails off. Leads are never passed to our AI models. The people who send you leads are your contacts: your form links to your own privacy policy, and you are responsible for how you use their details.
- Your product catalogs, only if you turn on catalog ads: the names, IDs and sizes of the catalogs and product sets you choose.
Forwarding leads to your CRM: if the ad account's owner adds a webhook address in Render (for example Zapier or a CRM), we send each new lead to it as it arrives, over an encrypted connection and signed so your system can check it came from Render. Only leads that arrive after the address is set are sent. Once delivered, that copy is held by the service you chose, under your agreement with it.
The brand guidelines, product details and files you give the agent (logos, product photos, reference ads, your own finished ads, attachments in chat) and, when you ask, public information and images from your website are your creative materials, not Meta data: they stay in your account until you delete them.
How we use it
We use Meta data only to provide Render Autopilot to you, the customer who connected it: reporting, recommendations, generating creative, and making the changes you authorize. We do not use it for any other customer, sell it, use it to advertise Render, or use it to train AI models. The general uses described elsewhere in this policy, such as improving our platform or communicating with you about offers, do not apply to Meta data. Authorized Render personnel access this data only for support, billing, security and troubleshooting.
Service providers that process it
To provide the service we share the minimum necessary with these providers, each of which processes it only on our instructions:
- Meta, to make the changes you authorize.
- Zernio, which holds your Meta login and passes Render's requests to Meta.
- AI models: Anthropic (directly or through Amazon Web Services); OpenAI (directly or through Microsoft Azure); Google Cloud Vertex AI; Microsoft Azure AI services (image generation, speech, translation, image analysis and content safety); ElevenLabs, for voiceovers; and Firecrawl, to read your website when you ask.
- Hosting and storage: Supabase (our database), Cloudflare (file storage), Fly.io (application hosting), Microsoft Azure (encryption keys and off-site backups), Amazon Web Services (video rendering with Remotion), Google Cloud Storage (copies of the images and videos Google's models read) and Upstash (short-lived rate-limit counters).
- Inngest, which runs our background jobs and stores their inputs and outputs, such as reports and sync results.
- Sentry, for error monitoring: an error report can include technical details of what failed, with access tokens and other secrets removed first.
- Stripe, our payment processor: for the management fee it receives your ad accounts' names and ad spend, which appear on your invoices.
- Resend, which sends our emails to you, including lead emails.
- PostHog, our product analytics. Render Autopilot pages are excluded from its click capture and session recording: it records only that those pages were visited, not what is on them.
How long we keep it, and deleting it
- While an ad account is connected, we keep its Meta data to manage it. Comments are deleted 90 days after they were written.
- Leads are kept while Render manages the ad account. To have a particular lead deleted sooner, contact support from inside the app.
- When you disconnect Meta, stop Render managing an ad account, or stop the management fee, Render disconnects the login at Zernio and deletes the rest of that Meta data, including leads, comments and files copied from your ads, within 30 days, except billing records we must keep by law. Copies in our database backups are deleted 35 days after the backup is made.
- Removing the connection in your Facebook settings (Business Integrations) cuts off Render's access at once, and the agent stops. To have Render also delete the Meta data it holds, disconnect in Render or ask us. For a login made through Render's own Meta app, removing it there tells us automatically and we delete your Meta data within 30 days, and when Meta sends us your data deletion request we delete it immediately and give you a confirmation code to check its status.
- When you delete your Render account, Render's access is revoked at once and your Meta data is deleted promptly, normally within a day.
See Meta data deletion for step-by-step instructions.
Render is not affiliated with, endorsed or sponsored by Meta Platforms, Inc. Facebook and Instagram are trademarks of Meta Platforms, Inc.
08Google Ads data (Google Ads and YouTube Ads)
If you connect a Google Ads account, you sign in with Google and give Render access to that account through Google's OAuth, with the Google Ads scope. Render uses this access only to provide the features you ask for: creating and managing your Google Search and YouTube campaigns, their budgets, keywords, ads and videos, and showing you how they perform. Render acts only on the Google Ads account you pick, and links it to Render's Google Ads manager account to manage it.
What we receive and store
- A refresh token Google issues to Render, stored encrypted (see "Data Security") and never shown to you, to our AI models or to anyone else; and the email address of the Google login that connected.
- Your Google Ads accounts' IDs, names, currency and time zone, and the names, status and budgets of the campaigns in the account you pick, so you can see and choose what happens to them.
- The campaigns, ad groups, keywords, ads, assets, videos and conversion actions Render makes or changes for you.
- Results: spend, impressions, clicks, calls, conversions and the search terms people used, to report your results, improve your campaigns and calculate Render's management fee.
- For YouTube Ads, the videos Render makes for you are uploaded to YouTube as unlisted videos on the channel Google makes for your Google Ads account.
How we use it
We use Google data only to provide Google Ads and YouTube Ads to you, the customer who connected it. To plan and improve your campaigns, Render sends the relevant parts of it (for example keyword ideas, search terms and results) to its AI provider, Anthropic (directly or through Amazon Web Services), which processes it only to answer Render's request. We do not sell Google user data, use it for advertising, share it with anyone except the providers that run our service (as listed for Meta data above), or use it to develop, improve or train AI models.
Render's use and transfer to any other app of information received from Google APIs will adhere to the Google API Services User Data Policy, including the Limited Use requirements.
Your control, and deleting it
- You can stop Render running Google Ads or YouTube Ads at any time in Render. Once neither runs on your account, Render removes its manager link and revokes its access to your Google login. You can also remove Render's access in your Google Account's security settings.
- When you delete your Render account, we delete your Google Ads data, except billing records we must keep by law.
Google Ads and YouTube are trademarks of Google LLC. Render is not affiliated with, endorsed or sponsored by Google.
10People our customers reach
This section is for people who don't use Render but hear from a business that does.
Email Outreach
Email Outreach finds businesses a Render customer wants as clients and emails people at them on the customer's behalf. We obtain the business's name, website, phone number and address, and the names, job titles and work email addresses of people there, from People Data Labs, Icypeas, Outscraper (which reads public business listings) and the business's own website, and MillionVerifier checks the email addresses. We show the customer whom it contacted and any replies. We do this in the customer's and our legitimate interest in business-to-business marketing, and only in the countries our Terms list.
Direct Mail
Direct Mail prints and mails postcards to addresses a customer gives us, or that Render obtains from LeadsPlease for that customer (for example homes near their business): names and postal addresses.
Your choices
- To stop emails, reply "stop" or use the opt-out line in any of them. Render then stops every Render customer from emailing you through Render.
- To stop postcards, use the address printed on the card, tryrender.ai/mail/stop.
- To ask what we hold about you, or to have it deleted, email support@tryrender.ai. We keep a record of your opt-out, so you aren't contacted again.
We keep these details while they are needed for the customer's outreach or mailing and to honor opt-outs, and delete them when you ask (apart from the opt-out record). Names on mailing lists Render buys are removed 12 months after purchase.
11Your voice and likeness
If you choose to appear in your ads, you upload photos and, if you like, voice recordings of yourself. Our AI writes a short description of your appearance (for example hair, age range and skin tone) so the scenes it makes look like you. If you clone a voice, the recording goes to ElevenLabs, which creates a voice model.
A voice model or data about a face can be biometric information under some laws, such as those of Illinois, Texas and Washington. We use it only to make the content you ask for, never to identify anyone, and we never sell it. We share it only with the AI providers that make that content (ElevenLabs, Google and the others listed above). You may add only your own voice and likeness, or those of someone who has given you written permission (see our Terms).
We delete your photos, recordings, appearance description and voice models, including the model at ElevenLabs, when you delete them in Render or delete your account, and in any case within three years of your last use of Render.
12Teams, the API and MCP
- Teams: when you invite someone, we email them the invitation. The people on your team can see and use your account's content, and their actions are recorded in your account's activity log.
- API and MCP: we log each request (time, endpoint, result and usage) to bill you and keep the service secure. Your API keys are stored hashed. When you connect an AI assistant through MCP, it can do what you approve on the consent screen until you revoke it. Data you send to a webhook address you set is held by that service.
13How long we keep it
- Your account and content: until you delete them or your account. When you delete your account we remove it from our live systems promptly, normally within a day.
- Data from connected accounts: as described in the Meta, Google and social sections above.
- Backups: full backups of our database are kept for 35 days and then deleted. Copies of files are also kept in off-site backups for disaster recovery; a file you delete can remain in those backups after it is gone from Render, and is used for nothing but restoring Render.
- Billing, tax and fraud-prevention records: as long as the law requires, usually seven years.
- Support emails: while your account exists, and afterwards as long as needed to resolve the request.
- Analytics and error data: for the retention periods set in PostHog, Google Analytics and Sentry.
- People our customers reach, and your voice and likeness: as described in those sections.
14Data security
We protect your information with measures that include:
- Encryption of data in transit and at rest
- Meta access tokens and leads encrypted with AES-256-GCM, using keys that are themselves protected by a hardware security module (Azure Key Vault)
- Two-step sign-in for your account
- Access limited to the staff who need it for their work
- Off-site backups locked against changes for 30 days
No system is perfectly secure. If a breach affects your personal information, we will tell you as the law requires.
15Your choices and rights
- See and download your data: Settings → General → Download your data.
- Correct it: in Settings, or ask us.
- Delete it: Settings → General → Delete account, or ask us. Accounts using Render Autopilot or Email Outreach, or with an unpaid invoice, are deleted through support.
- Stop tips and other marketing emails: use the unsubscribe link in any of them, or Settings → Emails. Service emails about billing, security and your account still arrive.
- Depending on where you live, you may also have the right to object to or restrict how we use your information, to withdraw consent, and to receive your data in a portable format. Ask us.
To make a request, email support@tryrender.ai or use the Support button in the app. We may ask you to confirm your identity, for example by replying from your account's email address. Someone you authorize can make a request for you. We respond within 30 days (45 days for California requests) and won't treat you differently for using your rights. If we decline a request, you can ask us to reconsider by replying. In the European Economic Area, the UK and Switzerland you can also complain to your data protection authority.
16California privacy notice
In the last 12 months we collected these categories of personal information, from the sources and for the purposes described above:
- Identifiers, such as name, email address, IP address and account IDs
- Customer records, such as billing details
- Commercial information, such as plans and purchases
- Internet activity, such as usage, cookies and session replays
- Approximate location, from IP addresses
- Audio and visual information, such as uploads, photos and voice recordings
- Biometric information (voice models and appearance data), only if you use those features
- Professional information, such as the job titles of people reached through Email Outreach
- Inferences, such as the appearance description above
We disclose each category to the service providers listed in "Who we share it with", for the business purposes described there. We do not sell personal information. We share identifiers and internet activity with Meta and Google for cross-context behavioral advertising, as described in "Cookies, analytics and advertising". Our sensitive personal information (account logins and biometric information) is used only to provide the features you ask for, not to infer anything about you. We keep each category as described in "How long we keep it".
California residents have the right to know what we collect, use and share, to delete and correct it, to opt out of its sale or sharing, and not to be treated differently for using these rights. See "Your choices and rights" for how to make a request.
17International data transfers
Render is based in the United States, and we and our service providers process information in the United States and other countries. When we transfer personal information from the European Economic Area, the UK or Switzerland, we rely on our providers' Standard Contractual Clauses or their certification under the Data Privacy Framework.
18Children’s privacy
Render is for people 18 and over. We don't knowingly collect personal information from anyone under 18. If you believe we have, contact us and we will delete it.
19Changes to this policy
We may update this policy as Render changes. If a change is material, we will tell you by email or in the app before it takes effect. The date at the top shows when it last changed.
20Contact us
Questions about this policy or your information? Contact us at:
Email: support@tryrender.ai
Mail: Render AI, Inc., 2261 Market St, Ste 19827, San Francisco, CA 94114, USA
09Social accounts (Instagram, Facebook, TikTok and YouTube)
When you connect a social account, you log in on the platform's own screen through Zernio, which holds the login for Render.
What we receive and store
How we use it
We use it only to provide social posting to you: to post and schedule what you ask (and, if you turn on Autopilot posting, what it plans), to show your results and to show your inbox. Render's AI reads comments and messages to sort them and suggest replies; a reply goes out only when you send it. The people who comment or message you are your contacts, and you are responsible for how you use their details. We don't sell this data or use it for any other customer.
YouTube
Render uses YouTube API Services. By connecting a YouTube channel you agree to the YouTube Terms of Service, and the Google Privacy Policy applies to your use of YouTube. Through YouTube API Services Render reads your channel's name, ID and picture; uploads the videos you post with their title, visibility, your "made for kids" answer and an AI label where it applies; and reads their results and comments. We use and share this data only as described in this section. You can revoke Render's access at any time by disconnecting the channel in Render, or on Google's security settings page.
How long we keep it
We keep this data while the account is connected. Disconnecting removes the login at Zernio and cancels posts that haven't gone out; the records of past posts and your inbox stay in your Render account until you delete them or your account.
Render is not affiliated with, endorsed or sponsored by TikTok or YouTube. TikTok is a trademark of ByteDance Ltd.; YouTube is a trademark of Google LLC.