Legal
Privacy Policy
Last updated October 9, 2026 · Terms of Service
This Privacy Policy explains how Računalniško programiranje, Alexandre Georges Michel Pierre Grisey s.p. ("CapWrapp", "we", "us") collects and uses personal data when you visit capwr.app, use the CapWrapp app, the free tools and commit previews (together, the "Service"). We're the controller of that data under the EU General Data Protection Regulation (GDPR).
In short
- We collect what we need to run CapWrapp: your sign-in profile, the repositories and store accounts you connect, and what you create in CapWrapp.
- Store credentials and secrets can't be read from a browser once saved. Only our servers use them, to ship your apps when you ask.
- We don't sell your personal data, and we don't use it for advertising.
- We rely on a short list of service providers, some of them in the United States.
- You can delete your account at any time from Account settings.
1. Who is responsible
- Controller: Računalniško programiranje, Alexandre Georges Michel Pierre Grisey s.p.
- Address: Trg borcev NOB 19, 1431 Dol pri Hrastniku, Slovenia
- VAT number: SI92114466
- Email: contact@capwr.app
For any question about your data, or to exercise your rights, write to contact@capwr.app.
2. What we collect
Account data
When you sign in with Google or GitHub, we receive your name, email address, profile photo, a unique user ID and, with GitHub, your GitHub username. We never receive your Google or GitHub password. We also keep when you created your account, your language, the plan you picked on the pricing page, when you accepted the Terms, and your access PIN, stored only as a salted hash.
GitHub data
When you install the CapWrapp GitHub App, we receive the installation, the account or organization it's installed on, and the repositories you grant. To provide the Service, we read branches, commits (including commit messages and author names), files, pull requests, workflow runs and build logs, and receive GitHub events for those repositories (pushes, workflow runs, pull requests, installation changes). We keep what we need to show your apps and their history, such as commit identifiers, messages and author names.
App and workspace data
The apps you connect and their settings, your organizations, their members, roles and invitations (including the email address of the people you invite), your release history (what was shipped, when, by whom and how it went), store listing text, screenshots and icons, environment values you save, integration settings, and the files of the commit previews you request.
Store credentials and secrets
Apple App Store Connect API keys (issuer ID, key ID and private key), Apple team ID, signing certificates and profiles, Google Play service account keys, Android upload keystores and their passwords, Capgo API keys and app environment values. These are stored in a part of our database that no browser can read. Only our servers use them, and they're handed to your GitHub workflow at build time through single-use tokens that expire.
Notification data
The email addresses that receive alerts, the Slack webhook URL you paste, and the Telegram chat you link.
Emails we send
A copy of each email we send: the recipients, subject, content, what it was about (an alert, a billing notice, a product email, an invitation), when it was sent and whether it was delivered to our email provider. We use it to answer your questions about an email and to check that our emails go out.
Billing data
Payments are handled by Link, a Stripe service and the merchant of record for CapWrapp subscriptions. Link collects your payment details, billing name and address, email, phone number and, for businesses, tax details, and processes them under its own privacy policy. We never receive your full card number. We receive and keep your Stripe customer and subscription IDs, your plan and billing period, the status of your subscription and trial, and which apps were recently shipped (to apply the active-app limit).
Support messages
Messages you send us through the live chat or by email. When you're signed in, the chat is linked to your user ID, name and email so we can help you faster.
Usage and analytics data
We use DataFast to understand how the website and the app are used: pages viewed, referrer and campaign, browser and device type, approximate location derived from your IP address, and events such as signing up, connecting a project or starting a build. When you're signed in, these are linked to your user ID, name, email and profile photo. DataFast sets a visitor and a session identifier (see section 8), which we also attach to Stripe Checkout to know which pages lead to subscriptions.
Technical and log data
Like any website, our servers and hosting providers log technical data such as IP addresses, browser user agents, requested pages and times. When something fails, we record an error report with the error, the page and, if you're signed in, your user ID and email, using LiteFeedback. We also report visits from known search engine and AI crawlers (their user agent and the page they visited) to DataFast; this concerns bots, not people.
Free tools
The free tools on the website run in your browser. What you paste or upload in them stays on your device, except in the GitHub repository checker, which asks GitHub's public API directly from your browser about the repository you enter.
Commit previews
When someone opens a preview link, our servers process their IP address and browser data to serve it, and set a session cookie on preview.capwr.app for that preview.
3. Why we use it, and on what legal basis
| Purpose | Data | Legal basis (GDPR) |
|---|---|---|
| Create your account and sign you in | Account data | Contract, Art. 6(1)(b) |
| Provide the Service: connect repositories, open pull requests, build, ship, preview, edit and push listings | GitHub, app, credential data | Contract, Art. 6(1)(b) |
| AI translation and build failure explanations | Listing text, build log error lines | Contract, Art. 6(1)(b) |
| Send the alerts you set up | Notification data | Contract, Art. 6(1)(b) |
| Run the trial, plans, limits and billing | Billing data, app activity | Contract, Art. 6(1)(b); legal obligation for accounting records, Art. 6(1)(c) |
| Answer support requests | Support messages, account data | Contract, Art. 6(1)(b); legitimate interest in helping you, Art. 6(1)(f) |
| Send service emails (trial ending, billing, invitations, security) | Email address | Contract, Art. 6(1)(b); legitimate interest, Art. 6(1)(f) |
| Keep a copy of the emails we send | Emails we send | Legitimate interest in answering questions about them and checking that they go out, Art. 6(1)(f) |
| Send product emails about your account: a welcome, setup tips, trial check-ins and the occasional feedback question | Email address, name, and whether you've added an app, shipped a build, or started, ended or canceled a plan | Legitimate interest in helping you get set up and improving CapWrapp, Art. 6(1)(f) |
| Keep the Service secure, prevent abuse, fix errors | Technical and log data, error reports | Legitimate interest in a secure, working Service, Art. 6(1)(f) |
| Understand how CapWrapp is used and improve it | Usage and analytics data | Legitimate interest in improving the Service, Art. 6(1)(f), and your consent where the law requires it for cookies, Art. 6(1)(a) |
| Comply with the law and defend legal claims | As needed | Legal obligation, Art. 6(1)(c); legitimate interest, Art. 6(1)(f) |
We don't send marketing newsletters without your consent. You can turn product emails off with the unsubscribe link in each of them, or in Settings; service emails about your trial, billing and security still arrive. We don't make decisions about you based solely on automated processing that have legal or similarly significant effects.
4. AI processing
For listing translation, we send the listing text to OpenAI. To explain a failed build, we send the error lines of the build log; GitHub hides secrets in logs before we read them. OpenAI processes this data as our service provider. Under OpenAI's API terms, data sent through its API isn't used to train its models by default.
5. Who we share it with
We share personal data only with the service providers below, who process it for us under contracts that protect it, and only as far as they need to provide their service.
| Provider | Purpose |
|---|---|
| Google Cloud and Firebase (Google) | Sign-in, database, file storage, servers, hosting of previews |
| Hostinger | Server hosting the capwr.app website |
| GitHub (Microsoft) | Repository access and builds, through the GitHub App you install |
| Stripe and Link | Payments; Link is the merchant of record |
| OpenAI | AI translation and build failure explanations |
| Twilio SendGrid | Service, alert and product emails |
| Heyo | Live chat |
| DataFast | Website and product analytics |
| LiteFeedback | Error tracking |
Other recipients:
- Services you connect. When you ask CapWrapp to ship, we send your app, builds, listing and related data to Apple, Google, Capgo or the integrations you choose, using your credentials. Alerts go to the Slack channel or Telegram chat you link. These services process the data under their own terms and privacy policies, as do Google and GitHub for your sign-in and your accounts with them, and Link for payments.
- Your teammates. Members of an organization see its apps and history, including your name, email, photo and the actions you take there.
- Authorities, when the law requires it, or to protect our rights, our users or the public.
- A successor, if our business is transferred, in which case we'll tell you first.
We don't sell or rent personal data, and we don't share it for advertising.
6. International transfers
Some providers, including Google, GitHub, Stripe, OpenAI and Twilio, process data in the United States or other countries outside the European Economic Area. When they do, we rely on the EU-US Data Privacy Framework where the provider is certified, or on the European Commission's Standard Contractual Clauses. You can ask us for a copy of the relevant safeguards.
7. How long we keep it
- Account and workspace data: as long as your account exists.
- Inactive accounts: if you haven't signed in for 24 months and have no active subscription, we may delete your account. We'll email you at least 30 days before.
- Read-only workspaces (trial ended or subscription cancelled): kept so you can pick up where you left off, subject to the rule above.
- Deleted apps: when you remove an app, its stored credentials, previews, history, listing screenshots and related records are deleted.
- Deleted accounts: when you delete your account, your profile, secrets and PIN, the apps in your personal workspace (as above), your history and our copies of the emails we sent you are deleted, and you're removed from your organizations. Apps in organizations stay with the organization.
- Commit previews expire after 7 days. Build tokens expire after 90 minutes.
- Billing records: as long as tax and accounting law requires.
- Support conversations: as long as your account exists, or up to 24 months after the conversation if you don't have one.
- Copies of the emails we send: 12 months, or until you delete your account.
- Analytics, logs and error reports: for a limited time, then deleted or kept only in aggregate.
Copies may remain for a short time in our providers' backups and logs before they're overwritten.
8. Cookies and similar technologies
| What | Purpose | Type |
|---|---|---|
| Firebase Authentication (browser storage) | Keeps you signed in | Essential |
| Session storage | Keeps the state of a sign-in or GitHub installation, and of some screens | Essential |
| Preview session cookie (preview.capwr.app) | Serves the preview you opened | Essential |
| Service worker cache | Loads the site faster and keeps a basic offline page | Essential |
| Local storage (capwrapp.locale and similar) | Remembers your language, checklist progress and the last changelog you read | Preferences |
| Heyo | Runs the live chat and keeps your conversation | Functional |
| datafast_visitor_id, datafast_session_id | Analytics (DataFast) | Analytics |
We don't use advertising cookies. You can block or delete cookies and site data in your browser settings. Without the essential ones, you can't sign in.
9. Security
- All traffic is encrypted with HTTPS, and our providers encrypt stored data.
- Database security rules limit each person to their own data and their organizations' data.
- Store credentials and secrets can't be read from any browser. Our servers hand signing keys to your GitHub workflow once per build, through tokens that expire.
- An access PIN, stored only as a salted hash, protects the settings pages that manage credentials.
- The GitHub App only reaches the repositories you grant it.
- We access your data only when needed to run the Service, to give you support you ask for, to investigate a problem or abuse, or when the law requires it.
No system is perfectly secure. If we learn of a personal data breach that affects you, we'll notify you and the authorities as the law requires. To report a vulnerability, write to contact@capwr.app.
10. Your rights
Under the GDPR, you have the right to:
- access your personal data and get a copy of it;
- correct inaccurate data;
- have your data deleted;
- restrict how we use it;
- receive the data you gave us in a machine-readable format and have it sent to another service (portability);
- object to processing based on our legitimate interests, including analytics;
- withdraw your consent at any time, where we rely on it, without affecting what was done before.
You can delete your account and remove connections and credentials yourself in CapWrapp. For anything else, write to contact@capwr.app. We answer within one month and may ask you to confirm your identity first.
You also have the right to lodge a complaint with a data protection authority, in particular in the country where you live or work. In Slovenia, that's the Information Commissioner of the Republic of Slovenia (Informacijski pooblaščenec), Dunajska cesta 22, 1000 Ljubljana, www.ip-rs.si. We'd appreciate the chance to address your concern first.
11. Your apps and your users
CapWrapp doesn't collect data from the people who use the apps you publish. Integrations you add through CapWrapp, such as RevenueCat, AdMob, OneSignal, Sentry or analytics tools, send data from your app directly to those providers, under your accounts. For your apps, you're the controller: you need your own privacy policy, and you're responsible for the privacy details you declare on the App Store and Google Play.
When Your Content includes personal data of other people, we process it on your behalf, as described in section 14 of our Terms of Service.
12. Children
CapWrapp is for people aged 18 and over. We don't knowingly collect data from children. If you think a child has given us personal data, contact us and we'll delete it.
13. Changes to this policy
We may update this policy. The date at the top shows the latest version. For important changes, we'll tell you by email or in CapWrapp before they take effect.
14. Contact
- Računalniško programiranje, Alexandre Georges Michel Pierre Grisey s.p.
- Trg borcev NOB 19, 1431 Dol pri Hrastniku, Slovenia
- Email: contact@capwr.app