1. Controller
The controller responsible for this website and the RunBatch service is:
Octavio Herrera
RunBatch
Otto-Weidt-Platz 8
10557 Berlin
Germany
info@runbatch.ai
2. Data we process
- Account data: name, email address, password hash, verification and private-beta access status, and account timestamps.
- Security and session data: IP address, browser user agent, session identifiers, authentication events, and security logs.
- Billing data: top-up amount, currency, payment status, Stripe customer and transaction references, refunds, and balance ledger entries. RunBatch does not receive full card numbers from Stripe.
- Communications: messages you send and transactional email delivery details.
- Diagnostics: application errors, request route, device or runtime context, and technical breadcrumbs needed to investigate failures. Sentry is configured not to send default personal identifiers.
- Customer content: datasets, prompts, configuration, model selections, and generated outputs when paid batch execution is enabled and you choose to submit them.
3. Dataset upload and preview
When you submit a CSV or JSONL file in the batch builder, RunBatch uploads it to private server-side storage, inspects its columns and sample rows for the configuration screen, and scans the complete dataset to estimate tokens and prepare a conservative budget. The file is not sent to a model provider until you review the rates and maximum budget and explicitly confirm execution.
4. Purposes and legal bases
- To create accounts, authenticate users, provide the service, process top-ups, and respond to support requests under Article 6(1)(b) GDPR.
- To meet tax, accounting, fraud-prevention, and other legal duties under Article 6(1)(c) GDPR.
- To secure, monitor, debug, and improve RunBatch under Article 6(1)(f) GDPR. Our legitimate interests are reliable service operation, abuse prevention, and product improvement.
- Where we ask for optional consent, under Article 6(1)(a) GDPR. Consent may be withdrawn at any time for the future.
5. Service providers and recipients
We disclose data only where needed to operate RunBatch, complete a transaction, follow your instructions, or comply with law. Current categories of recipients include:
- Hetzner Online GmbH for hosting infrastructure.
- Stripe for Checkout, payment processing, fraud prevention, receipts, and refunds.
- Brevo (Sendinblue) for account, verification, password reset, and operational emails.
- Sentry for application error monitoring and diagnostics.
- Professional advisers and public authorities where required by law or necessary to establish, exercise, or defend legal claims.
Model providers for paid inference will be disclosed in the product configuration or supporting documentation before customer content is sent to them. RunBatch does not sell personal data.
6. International transfers
Some providers may process data outside the European Economic Area, including in the United States. Where required, transfers rely on an adequacy decision, the European Commission's Standard Contractual Clauses, or another lawful transfer mechanism, together with appropriate safeguards.
7. Retention
Account data is retained while the account is active and for a limited period afterward where needed for security, disputes, or legal obligations. Session and diagnostic data is kept for shorter operational periods. Billing, invoice, and transaction records are retained for the periods required by German tax and commercial law. Source files, prompts stored with execution artifacts, and output files are deleted 30 days after all batches using a dataset finish. Files that are uploaded but never run are deleted after 7 days. Accounting totals and provider references remain where needed for billing, fraud prevention, disputes, and legal obligations.
8. Customer datasets
If you submit personal data about other people in a dataset, you are responsible for having a lawful basis and providing any required notices. For such customer content, RunBatch acts as a processor where applicable and processes it on the customer's documented instructions. Contact us if your organization requires a data processing agreement.
RunBatch does not use customer datasets, prompts, or outputs to train general-purpose AI models unless the customer expressly opts in to a separate program with clear terms.
9. Security
We use access controls, encrypted transport, password hashing, signed requests, rate limiting, and monitoring appropriate to the service. No system can guarantee absolute security, so you should avoid submitting data that is unnecessary for the batch and protect your credentials.
10. Your rights
Subject to the GDPR's conditions, you may request access, rectification, erasure, restriction, portability, or object to processing based on legitimate interests. You may also withdraw consent without affecting earlier lawful processing. Send requests to info@runbatch.ai. We may need to verify your identity.
11. Complaints
You may lodge a complaint with a data protection authority, particularly in the EU country of your residence, workplace, or the alleged infringement. The supervisory authority for the controller is the Berlin Commissioner for Data Protection and Freedom of Information.
12. Automated decisions and children
RunBatch does not use personal data to make decisions that produce legal or similarly significant effects about account holders. The service is not directed to children, and users must be legally capable of entering the agreement.
13. Changes
We may update this policy when the service or legal requirements change. Material changes will be communicated through the service or by email where appropriate. The effective date above identifies the current version.