Privacy

This page says what the hosted service keeps about you, item by item, where it is, how long it stays and why it is allowed to. It covers version.cam, app.version.cam, api.version.cam and clips.version.cam. The controller of the personal data it describes is:

Controller: RMTR studio, Peter Bulovec s.p.
Owner: Peter Bulovec, sole proprietor (samostojni podjetnik)
Registered office: Smokuč 15a, 4274 Žirovnica, Slovenia
Register: Poslovni register Slovenije (AJPES), the Slovenian Business Register; registration number (matična številka) 7021135000
Tax number: 42258723 (davčna številka)
VAT: SI42258723. Identified for VAT for cross-border services under Article 78(4) of the Slovenian VAT Act (ZDDV-1); no VAT is charged on supplies in Slovenia (Article 94 ZDDV-1).
Contact: hello@version.cam, for anything, requests about your personal data included

The versioncam package and the GitHub Action are a different matter: they run in your own CI and on your own machines, with your app and your secrets, and send nothing to us until versioncam publish runs. Then they send the recordings described below, and nothing else.

What we keep, and why

Each item names its legal basis in the words of the GDPR: contract is Article 6(1)(b), the service you asked for; legitimate interest is Article 6(1)(f), running and securing the service; legal obligation is Article 6(1)(c), tax law. "Kept" is how long, and what removes it.

Your GitHub identity: Your GitHub id, your login and, if GitHub shares one, your public e-mail address (usually none). The sign-in asks GitHub for no scope: it learns who you are and nothing you have written. To sign you in and to name your account.; Contract · while your account exists
What you may reach: Which GitHub accounts you belong to where the Versioncam App is installed and, for each of their repositories, whether you may read it or administer it, as GitHub lists them. Read at every sign-in and replaced whole, so what GitHub no longer grants goes with it. This decides who sees a project and who may change it.; Contract and security · replaced at each sign-in
Your session: A session record and the cookie that names it, __Host-vc_session, for seven days. While you sign in, a second cookie, __Host-vc_oauth, and the page to return to, for ten minutes. Signing out ends the session at once; "sign out everywhere" ends every session and every command-line token of yours.; Contract · seven days; the sign-in's state ten minutes
Command-line tokens: A token versioncam cloud login makes once you approve its code in the browser, kept as a hash: the service recognises the token and cannot reproduce it.; Contract · until you revoke it or sign out everywhere; an expired one is removed thirty days later
Your account: The account's login, its plan, a plan given by hand and when it ends, whether it is suspended and why, and once payment opens, the billing e-mail address and Stripe's id for the customer.; Contract · while the account exists; invoices ten years after the end of the year they belong to (ZDDV-1, Article 86)
Projects: A project's repository, its visibility (public, unlisted or private), how many days of versions it keeps, the address that gets its notifications, the Slack webhook you give it, and whether it opens GitHub issues. A notification address is held as pending until its owner clicks the link we send, and we keep when the link went out and when it was confirmed; mail goes only to a confirmed address. The Slack webhook is encrypted at rest.; Contract · while the project exists
Project tokens: For a CI outside GitHub Actions, which has no GitHub token to publish with: kept as a hash, like the command line's.; Contract · until revoked
Recordings: What versioncam publish sends from your CI: each clip's timeline and the pictures of your app's screens it was recorded from; the commit, branch, run id and recorder version; the check's result and, when a clip broke, one picture of the page where it did. If the screens show personal data, you are its controller and we process it for you under thedata processing terms.; Contract; for what the screens show, your instructions · as your plan and the project's retention say: the daily sweep removes versions past them, and a branch's versions thirty days after its last publish (the default branch keeps its). Deleting a project removes its records at once and its files within minutes; the project's name stays as a tombstone, so a CI job cannot quietly bring it back
Renders: The videos and posters made from a recording.; Contract · with their version
The record of the service: Each publish's own record, for two hours; per account and month, counts of publishes, render seconds and bytes; and an event log per account: what kind of thing happened, when, and a line about it (a project's name, the reason for a suspension). For the plan's limits, the dashboard, support, and noticing abuse.; Contract and legitimate interest · usage by month; events 400 days, removed by the daily sweep
Pull requests: The number and head commit of each pull request the App reports on, for its check and its comment.; Contract · with the project
Request logs: Cloudflare's log of each request to the service: method, address with its query string removed before it is written, status, timing and the country it came from. For operating and securing the service.; Legitimate interest · seven days (Cloudflare Workers Logs on the Workers Paid plan, checked 2026-11-01)
The services form: Your name, an address to reply to, a company if you give one, what it is about and your message become one e-mail to us through Resend, with your address as the reply-to; the service stores none of it. Your IP address is counted for an hour (five messages an hour from one address), and everyone's messages together for a day (fifty).; Steps before a contract · the e-mail in our mailbox and in Resend's log; the hourly count an hour; the daily count 31 days
Turnstile: On the services form, Cloudflare judges whether a person is sending it. We learn pass or fail; what Cloudflare looks at in your browser is in itsTurnstile privacy addendum.; Legitimate interest · the verdict is not kept
Notification counts: How many notification e-mails each project sent on each day, for the cap per project.; Legitimate interest · 31 days
Billing, once payment opens: Your name, billing address and VAT number, given to Stripe at checkout, and the invoices Stripe makes. Your card goes to Stripe only and never reaches us.; Contract and legal obligation · invoices ten years

Where

Recordings, renders and the database are stored in Cloudflare's European Union jurisdiction. The pages and the API are served by Cloudflare's network, which answers from the location nearest you. A render holds a version's screens for the seconds it takes, where its container runs. E-mail is sent from Resend's EU region. GitHub is in the United States. Each company, what it does for us, and the basis on which personal data may leave the EU are on the subprocessors page.

Who else sees what

GitHub receives the App's check runs, comments and issues on your repositories, on your project's instruction. Slack receives what your project's webhook says, if you gave it one. Nobody else: nothing is sold, shared or used for advertising, and there is no profiling.

On this website

No analytics, no tracking, and no third-party script, except Cloudflare's Turnstile on the services page. Fonts, clips and the badge on the front page come from version.cam's own hosts, so no request of yours leaves the site for anyone else.

Cookies

Two, both set by app.version.cam and readable by it alone: __Host-vc_session keeps you signed in for seven days, and __Host-vc_oauth lasts the ten minutes of signing in with GitHub. Both are strictly necessary (they are the sign-in), so no consent is asked and no banner is shown; the ePrivacy rules, as ZEKom-2 carries them in Slovenia, exempt storage a service cannot work without. version.cam sets no other cookie. The Turnstile widget on the services page is Cloudflare's, and its addendum says what it does in your browser.

Your rights

You may ask for a copy of your data, its correction, its deletion, a limit on its use, or its transfer to you in a usable form, and you may object to what we do on the basis of legitimate interest (GDPR, Articles 15 to 21). Write to hello@version.cam from the e-mail address GitHub has for you, or from a confirmed notification address, so we know it is you. We answer within thirty days.

Your own page on app.version.cam, reached from your login in the bar, has the two buttons: "Download my data" gives you everything above as one JSON file, and "Delete my account" removes your sessions, your command-line tokens, your memberships and access records, and your user record at once. An account that holds no projects, no subscription and no customer record goes with it; one that does stays as the customer's, and you are removed from it. A project you administer you delete yourself, in its settings, and you may download any version as a zip first. Either is also a request to the address above.

You may complain to the Information Commissioner of the Republic of Slovenia (Informacijski pooblaščenec, Dunajska cesta 22, 1000 Ljubljana, ip-rs.si), or to the authority where you live.

Changes

This page was last changed on 2026-11-01. A change that narrows what you may expect from us is sent to the e-mail address we have for your account thirty days before it applies. The version in force is always this page.