Who we are
Rend (“Rend”, “we”, “us”) runs rend.ai: a studio for making video, music and images with AI agents, and Boost, which runs our customers’ videos as ads. This policy covers rend.ai, the Rend apps, the Rend tag (rend.js) and Boost. Questions or requests: support@rend.ai.
What we collect
- Account. Your name, email address, a hash of your password, two-factor settings and your sign-in sessions.
- Payments. Stripe processes card payments; we never see or store full card numbers. We keep your purchases, credit balance, invoices and the result of Stripe’s fraud checks.
- Your content. Files you upload, your projects, prompts and messages to Rend’s agents, and everything Rend makes for you.
- Connected accounts. When you link a YouTube channel, an X account, or your own Claude or ChatGPT account, we store the access tokens those services give us, encrypted, and basic profile details such as the channel name.
- Usage and device. IP address, browser and device type, pages and features used, errors, and timestamps, as server logs and usage records.
- Support. What you send us when you ask for help.
- Status alerts. If you sign up for email alerts at status.rend.ai, we keep your email address only to send outage emails, until you stop them (every email has a link).
Boost and the Rend tag
For advertisers. Boost runs your ads on Meta (Facebook and Instagram) from ad accounts that Rend manages. Through Meta’s Marketing API we read those campaigns’ performance data, such as spend, impressions and link clicks, and we create and manage the campaigns we run for you. We use this data only to run, report and bill your Boost. Each advertiser’s data is shown only to that advertiser and to Rend’s staff. It is never combined across advertisers, sold, or used for targeting or profiling.
On advertisers’ websites. An advertiser can put the Rend tag on their site to measure sales from their Boost. When someone visits that site, the tag records:
- a random visitor ID (cookie
rend_vid, 90 days); - the Boost code from the ad link (cookie
rend_click, 7 days); - Meta’s click and browser IDs (cookies
_fbcand_fbp, 90 days); - the page address and referring site, IP address and browser user agent;
- a one-way hash of the browser’s language, screen size and time zone;
- for a purchase or sign-up the advertiser reports, the order value and, if the advertiser provides them, the buyer’s email address or phone number, which we store only as SHA-256 hashes.
We send purchases and sign-ups from a Boost, with the hashed identifiers, IP address, user agent and Meta’s click and browser IDs, to Meta’s Conversions API for the ad account that ran the ad, so Meta can measure the ad. The tag collects nothing from browsers that send Global Privacy Control or Do Not Track, or when the site turns consent off. Advertisers who use the tag must tell their visitors and get any consent their law requires.
How we use it
- To provide Rend: run your projects, agents, renders, exports, publishing and Boosts.
- To take payments, keep credit balances, and prevent fraud and abuse.
- To keep accounts secure, answer support requests and fix problems.
- To send emails about your account, jobs, Boosts, billing and rewards.
- To understand how Rend is used so we can improve it.
- To meet legal, tax and accounting duties.
We do not sell personal information, and Rend does not train AI models on your content.
Who we share it with
- Service providers that run Rend for us, under contract: Cloudflare (hosting, database and storage), Stripe (payments and fraud checks), cloud computing providers (rendering and processing), AI model providers (writing, transcription, and generating video, images, music and voice from what you ask for), and email delivery.
- Meta, for Boost, as described above.
- Platforms you connect, such as YouTube and X, when you ask Rend to publish or read your stats there.
- Authorities or others when the law requires it, or to protect Rend, our users or the public.
- A buyer or successor if Rend is sold or merged, under this policy.
How long we keep it
We keep your account and content while your account is open. When you delete your account, your projects and media are deleted and your identity is erased from what remains. We keep payment and ledger records, without your identity, as long as tax and audit rules require. Boost performance data and tag events are kept with the Boost’s records for reporting and billing, and are deleted on request (see Data deletion). Logs and backups age out on their own.
Your choices and rights
- Delete your account any time in Studio: Settings, then Security, then Delete account.
- Ask for a copy of your data, a correction, or deletion by emailing support@rend.ai. We answer within 30 days.
- Revoke Rend’s access to a connected account in that service’s own settings (YouTube, X, Meta, Claude or ChatGPT).
- Stop the Rend tag in your browser with Global Privacy Control or Do Not Track.
Depending on where you live (for example California, the EU or the UK), you may have further rights, such as to object to or restrict processing, or to complain to your data protection authority. We will not treat you differently for using them.
Security
Data is encrypted in transit. Stored access tokens are encrypted with keys kept apart from the database. Accounts can use two-factor sign-in. No system is perfectly secure, so please use a strong, unique password.
Children
Rend is not for children under 13, and we do not knowingly collect their data. If you think a child has given us data, email us and we will delete it.
International transfers
Rend is run from the United States, and our providers process data in the US and other countries. Where the law requires it, we use safeguards such as standard contractual clauses.
Changes
If we change this policy, we will update the date above, and for significant changes we will tell you by email or in Rend before they take effect.