Legal
Privacy Policy
Effective
Rendobar provides a media processing API. This policy explains what data we collect, why, and what control you have over it.
Rendobar is the data controller for information collected through the Service. You can reach us at [email protected].
What we collect
Account data
Your name, email address, and profile information from the sign-in method you use: GitHub, Google, or a one-time code or link sent to your email. We don't store passwords.
Usage data
API request metadata: job type, timestamps, duration, cost, and which client sent the request (for example the SDK, CLI or n8n node, and its version). Used for billing, support and to keep the service running.
Media files
Files you submit for processing. Inputs are deleted after processing. Outputs are stored temporarily according to your plan's retention period.
Payment data
Handled entirely by our payment processor. We never see or store card numbers.
Attribution data
Which source you arrived from on your first visit (for example an AI assistant like ChatGPT, a search engine, or the website that referred you), the page you landed on, any campaign tags on the link, and the same for your most recent visit before signing up. We store these once per workspace to learn which channels bring developers to Rendobar. We never store a full link or its query string, only the page path. Links in our emails say which email they came from, so a visit from an email is not counted as direct. If that first visit came from an ad, we also keep the ad click identifier the ad platform added to the link, so we can report to that platform that the click led to a signup. That report carries no personal data, only the click identifier. No advertising profile, no cross-site tracking. Before you sign up, this source is kept in your browser for up to 30 days. It is not recorded if your workspace turns product analytics off.
Signup details
When a workspace is created we record where it was created (the dashboard, the CLI, an AI assistant connector, or an invitation), how you signed in (Google, GitHub or email), your country, your browser's time zone, and whether your email address is a free, business or education address. For a business address we keep the company domain. Country comes from the network, and we never store your IP address for this. After your first job we may ask two optional questions (how you heard about us, and what you are building). Your answers are stored only if you send them. We use all of this to understand who uses Rendobar and to improve it, never to advertise or sell.
When you leave
If you cancel Pro, we keep the reason and any comment you give in the billing portal, with your workspace, so we can see why people leave. If you delete a workspace and choose to tell us why, we keep your answer without your name, email or workspace, together with its plan, its age and how many jobs it ran. Both are optional.
Job origin
For each job, which API key or connection submitted it, the tool and runtime it came from (for example the SDK on Node.js), the name of the network it came from (such as a cloud provider or an internet provider), the country and the Cloudflare data center that received it. We never store your IP address for this. It helps us support you and understand how Rendobar is used. Kept with the job.
Request logs
Every request to our API, with what was sent and what we answered, so we can debug problems and answer support questions. API keys, passwords, tokens, signing secrets, cookies, custom callback headers and the signatures in signed links are removed before anything is stored, and so is the body of any upload. When an AI assistant uses Rendobar for you through our MCP server, we also record which tools it called, with what arguments, and what they returned. Never your conversation with the assistant. Each response carries an X-Request-Id you can quote to us. Only our staff can read these logs. They are kept for 30 days, and a count of requests by endpoint, status and speed for 90 days. This is operational data, so it is kept even when product analytics is off.
Activity
For each day, when each member last used Rendobar, through which tool (the dashboard, the SDK, the CLI, an AI assistant, and so on) and with which API key or connection. It powers "last active" on your team page and "last used" on your API keys, and tells us how the product is used. No IP address and no request content. Kept for 400 days.
Product analytics
We use PostHog, hosted in the EU and reached through our own domain, to count page views and record session replays with every form input masked, so we can see where the product is confusing. We use it only to understand and improve Rendobar, never to advertise. Visitors in the EEA, UK and Switzerland are asked first. Until they answer, we only count page views anonymously, with nothing stored in the browser and no session replay. After they choose No thanks, nothing is sent. Global Privacy Control and Do Not Track turn it off automatically. You can turn it off any time: for your whole workspace in Settings, Preferences, Product analytics, or for one browser with the switch next to it. Turning it off stops collection from that moment. When you are signed in, we also keep a record of your choice, the date and the wording you were shown, so we can show we respected it.
How we use it
- ✓ To run the service: process your media, track your balance and deliver results
- ✓ To send transactional emails (verification, billing)
- ✓ To prevent abuse and protect the platform
- ✓ To improve the service based on aggregate usage patterns (never individual content)
What we don't do
- ✕ We don't sell your data
- ✕ We don't train AI models on your content
- ✕ We don't analyze your media beyond processing your request
- ✕ We don't use advertising or tracking cookies
Sub-processors
We use the following third parties to operate the Service:
| Provider | Purpose | Location |
|---|---|---|
| Cloudflare | Hosting, CDN, database, object storage | Global |
| Trigger.dev | Job execution and processing | US / EU |
| Modal | GPU job execution | US |
| PostHog | Product analytics and session replay | EU |
| Polar | Payment processing | US |
| Resend | Transactional email | US |
Data retention
| Data | Kept for |
|---|---|
| Account info | Until you delete your account (removed within 30 days of deletion) |
| Job metadata | 12 months |
| Job outputs | Per your plan (30 days on Free) |
| Input files | Deleted after processing |
| Billing records | As required by law |
Automated processing
The Service uses automated systems to process your media (transcoding, captioning, moderation, etc.). We may also use automated tools for abuse detection and content moderation. No automated decision-making with legal or similarly significant effects is performed on your personal data.
Security
We protect your data with encryption in transit (TLS) and at rest. API keys are hashed before storage. Media files are stored in isolated object storage with time-limited access URLs. Access to production systems is restricted and logged.
If we discover a data breach that affects your personal data, we will notify you and any applicable regulatory authority within 72 hours as required by law.
Cookies
The dashboard uses a single session cookie for authentication. It is strictly necessary and cannot be disabled. Neither this website nor the dashboard uses tracking cookies or advertising pixels.
We use first-party browser storage (localStorage) for three things: your analytics choice, the product analytics described above, and how you arrived (the referring site, landing page and campaign tags of your first and most recent visit) so we can attribute your signup to a source. The arrival records are deleted after 30 days. None of it is a cookie or shared with third parties, and none of it is written if you decline analytics or your browser sends Global Privacy Control or Do Not Track.
International data transfers
Your data may be processed in the United States and other countries where our sub-processors operate. Where data is transferred outside the EEA, we rely on Cloudflare's and our sub-processors' standard contractual clauses and data processing agreements to ensure appropriate safeguards.
Legal basis for processing (GDPR)
If you're in the EEA or UK, we process your data under these legal bases:
- → Contract performance: Processing your media, managing your account, billing
- → Legitimate interest: Security, fraud prevention, service improvement, including server-side product analytics that you can switch off in Settings
- → Legal obligation: Billing records, compliance with law enforcement requests
- → Consent: Where specifically required, such as browser analytics for visitors in the EEA, UK and Switzerland, and optional marketing communications
Your rights
You can:
- → Access or export your data in a portable format
- → Correct inaccurate information
- → Delete your account and all associated data
- → Object to or restrict processing for specific purposes
- → Withdraw consent where processing is based on consent
- → Lodge a complaint with your local data protection authority
To exercise any of these rights, email [email protected]. We'll respond within 30 days.
California privacy rights
If you're a California resident, you have the right to know what personal information we collect, request its deletion, and opt out of its sale. We do not sell personal information. To exercise your rights, email [email protected].
Children's privacy
The Service is not intended for anyone under 18. We don't knowingly collect data from children. If you believe a child has provided us with personal data, contact us and we will delete it.
Changes
If we make material changes, we'll notify you by email or dashboard notification at least 30 days in advance.
Questions?
Reach us at [email protected].