Privacy notice

Slipmark Cloud is run by Reply Intelligence Group Ltd, a company registered in England and Wales with company number 17040048. Our registered office is 71-75 Shelton Street, Covent Garden, London WC2H 9JQ. We are registered with the Information Commissioner's Office under registration number ZC192287.

For any privacy question or request, email hello@replyintelligencegroup.co.uk.

When we act for our customers. For the repository and committer data in a customer's account, the customer is the controller and we are their processor. We handle that data only on the customer's instructions, under our Data Processing Agreement. If your data is in a customer's account, for example because you commit to their repositories, please contact that customer first. We will help them respond.

When we decide for ourselves. For account administration, billing contacts, visitors to our website and the running of our own business, we are the controller. The rest of this notice is mainly about this data.

Your GitHub identity when you sign in. We sign you in with GitHub. Your session holds your GitHub user id, login, display name, avatar address and a GitHub user access token, so we can check which repositories you can see.

The account that installed the app. The GitHub account id and login of the organisation or user that installed the Slipmark GitHub App.

Admin actions. The GitHub login of organisation admins who change rules or approve overrides. This is kept in the append-only account log as an audit record.

Committer identities. For each person whose work runs through Slipmark, we keep a pseudonymous id per account. Their GitHub login is held in a separate table and can be erased on request. After erasure, records show “erased” and cannot be linked back to the person.

Repository records. Repository names and ids, commit SHAs, workflow run ids, file paths, SHA-256 hashes, agent names, verdicts, attestation notes and pull request numbers. We read file contents from GitHub only to hash them in memory. We do not store file contents.

Billing. Card and payment details are collected and held by Stripe, not by us. From Stripe we receive a customer id, subscription status, seat quantity, and the billing name, address and tax id.

Alerts and webhooks. If you connect Slack or another destination, we keep the webhook address, integration key or email addresses you give us. If you add the Slipmark Slack app, we keep its access token (encrypted) and the channel it posts to. If you approve from Slack, we keep your Slack user id linked to your GitHub account so the approval is recorded as you. We keep a log of each event we send and how the destination answered for 30 days.

Messages. If you email us, we keep the message and your contact details so we can reply.

Attestation notes are free text written by a customer's agents. Customers must keep secrets and personal data out of them. Because the ledger is append-only, a note cannot be edited or removed once recorded.

Where we rely on legitimate interests, we have weighed them against your rights. You can ask us for details.

To sign you in we use:

a session cookie, encrypted and HttpOnly, which lasts 8 hours and holds the sign-in details in clause 3.1; and

a short-lived cookie used during sign-in to protect the GitHub sign-in flow.

These cookies are strictly necessary, so we do not ask for consent to set them.

We do not use advertising cookies. Our hosting provider, Vercel, keeps standard request logs (such as IP address, browser and the page requested) for a short period to run and secure the service.

To count visits and see which pages and links people arrive from, we use Vercel Web Analytics. It records the page viewed, the site you came from, your country, and your browser, operating system and device type. It sets no cookies and stores nothing on your device. It does not identify you: visits are grouped using a code worked out from the request that changes every day and is not kept. We rely on legitimate interests (improving the Service) for this.

If you accept analytics in the cookie banner, we also use Google Analytics, provided by Google Ireland Ltd. It sets cookies (named _ga and _ga_ followed by an ID) that last up to 2 years, and records the public pages you view, the buttons you click and the site you came from. It runs only on our public pages (the home page, docs, trust, status, anchors and legal pages), never on dashboards, proof records or auditor links, so it never sees repository data. Google signals and advertising features are switched off, Google does not store IP addresses in Google Analytics, and event data is deleted after 2 months. Google may process this data in the US under the EU-US Data Privacy Framework and its UK extension. We rely on your consent for this.

You can change your choice at any time with the Cookie settings link at the foot of every page. Declining removes the Google Analytics cookies.

We use a small number of service providers to run Slipmark Cloud. They are listed, with what they do and where, on our sub-processors page.

Each day we publish a signed digest of ledger heads to Sigstore's public Rekor transparency log. It contains only opaque identifiers and hashes, and no personal data.

We do not sell personal data.

We may disclose personal data where the law requires us to.

Our database is hosted in London. Some providers process data outside the UK, including in the US and the EU.

Where data leaves the UK, we rely on UK adequacy regulations where they apply, including the UK Extension to the EU-US Data Privacy Framework for certified US recipients. Otherwise we use the UK International Data Transfer Agreement or the UK Addendum to the EU Standard Contractual Clauses.

The ledger, run records, policy results, verification results and account log are append-only by design. We keep them indefinitely so that they remain verifiable. The personal data in them is limited to what is described in section 3.

Committer GitHub logins can be erased on request, as described in clause 3.4.

Account and billing records are kept while the account exists, and for 6 years afterwards where we need them for tax.

Session cookies expire after 8 hours.

You have the right to ask for a copy of your personal data, to have it corrected, to have it erased, to restrict or object to how we use it, and to receive it in a portable format. Some rights apply only in certain circumstances.

Because the ledger and account log are append-only, we cannot erase entries from them. We can erase a committer's GitHub login so that their records can no longer be linked back to them.

To use any of these rights, email hello@replyintelligencegroup.co.uk.

You also have the right to complain to the Information Commissioner's Office at ico.org.uk. We would be grateful for the chance to put things right first.

Data is encrypted in transit and at rest. The database cannot be reached from the browser, and only our server code can access it. Access is limited to our staff, currently our founder. The full list of measures is in Annex 2 of our Data Processing Agreement.

Slipmark Cloud is a business service and is not for anyone under 18.

We will update this notice when our practices change. The date at the top of the page shows when it last changed.