Privacy Policy

Digidan (Pty) Ltd (registration number 2017/184017/07), trading as DeploySeal, of 28 George Street, Mayfair, Johannesburg, 2092, South Africa, operates the DeploySeal service at deployseal.com (“we”, “us”). We are a private company incorporated in the Republic of South Africa.

Under the Protection of Personal Information Act 4 of 2013 (“POPIA”) we are the responsible party for information about our customers’ team members and about visitors to this website, and the operator for information our customers collect through DeploySeal, including everything testers submit. Where the GDPR or the UK GDPR applies, read “controller” for responsible party and “processor” for operator.

Our Information Officer is Danyal Motan, founder and director of Digidan (Pty) Ltd, registered with the Information Regulator under registration number 2026-068913, reachable at desk@deployseal.com.

• Customers and their team members: people who create or join a DeploySeal organisation to run reviews and sign off releases.
• Testers: people a customer invites to review a website. Testers do not need an account; they open a personal link.
• Signers: people a customer asks to approve a release, who may sign through a link without an account.
• Visitors to deployseal.com, including anyone who requests access or contacts us.
• Visitors to a customer’s website where the DeploySeal widget is installed. Section 5 explains the little the widget does for people who are not testers.

We do not take payment card details. When paid plans open, payments will be taken by a payment partner acting as merchant of record; it, not we, will hold your card details. The refund policy explains how that works.

The DeploySeal widget is a small script a customer installs on the website being reviewed. When a tester opens their personal review link, the widget starts a session. Testers see a notice on screen that session recording is active. Here is exactly what it records.

Before the sensitive parts leave the browser, the widget removes the fragment from page addresses and replaces the values of query parameters named like token, code, password, email or session with “[redacted]”. A tester can remove the replay, console, network or performance parts of a report before submitting it.

The widget does not use the browser’s location, camera or microphone. It stores no cookies on the customer’s site. It keeps a short-lived session token in the browser’s session storage and the tester’s name and dock position in local storage so they are remembered on the next page.

On a page where the widget is installed, every page load sends a short heartbeat to us: the site’s key, the page address and title, and the widget’s version and build. We use the heartbeat only to confirm that the installation is working. We store the time, version, build and install method, and nothing about the page or the visitor. No recording, screenshot or device detail is collected from anyone who has not opened a tester link.

• When you request access or send a message through the contact form, we keep your name, email address, organisation and what you wrote, so we can reply. Requests to join the pilot are kept until we have answered them and for twelve months after.
• Our web servers keep standard request logs (address, time, page, browser) for security.
• We run no analytics or advertising scripts. Our hosting provider does not set tracking cookies on our behalf.
• Fonts are served from our own site, not from a third party.

Under POPIA (section 11) and, where it applies, the GDPR (article 6), we rely on:

• Performing a contract with you or your organisation: running accounts, reviews, issues and sealed records.
• Our legitimate interests, where they are not outweighed by yours: keeping the service secure, preventing abuse, keeping an audit trail that makes sealed records trustworthy, and improving the product from aggregate usage.
• Legal obligations: tax and company records, responding to lawful requests.
• Consent, which you can withdraw at any time, for anything optional, such as product news.

For information collected through the widget, the customer who installed it decides why it is collected and must have a lawful basis for it. We process it only on their instructions, under the data processing agreement.

We do not sell personal information and we do not share it with advertisers. It is handled by these providers, each bound by contract to protect it:

Integrations you connect. If your organisation connects Linear, Jira, GitHub, Azure DevOps, Asana, Slack, Microsoft Teams, Zapier or a webhook, we send issue details (title, severity, page address, description, steps, the reporting tester’s name and a link back) to that service on your instruction. Those services then hold the data under their own terms, chosen by you. Your access tokens for them are stored encrypted with AES-256-GCM.

Sign-in providers. If you sign in with Google or Microsoft, they tell us your name and email address. We do not receive your password, and they receive nothing about your use of DeploySeal beyond the sign-in itself.

We will also disclose information where the law requires it, to establish or defend legal claims, or to a successor if the business is sold, with the same protections carried over.

Our application, database and evidence files are hosted on Microsoft Azure in the Johannesburg region, with file storage replicated to Azure’s paired South African region for resilience. Transactional email is sent from Azure’s Africa data location. The website, the web application and the widget are delivered by Vercel, whose network is global; requests you make to the application pass through Vercel’s servers, including in the United States, before reaching our API in South Africa. Error reports, with personal information stripped, go to Sentry in the United States.

Where information leaves South Africa we rely on section 72 of POPIA: the recipient is bound by contract to a standard of protection substantially similar to POPIA. For customers in the EU or UK we will enter into the Standard Contractual Clauses on request as part of the data processing agreement.

You may ask us, free of charge, to tell you what personal information we hold about you, to correct it, to delete it, to stop processing it, to object to processing based on our legitimate interests, or to send it to you in a usable form. Email desk@deployseal.com. We will confirm your identity, answer within 30 days, and explain any reason we cannot comply in full, for example where a sealed record must keep your signature.

• Team members can delete their own account from account settings. Deletion is refused while you are the only owner of an organisation that has other members, or while any of your organisations holds a sealed record, because a sealed record must keep the names of its signers. Transfer ownership or ask the organisation owner to resolve this first.
• Testers should first ask the organisation that invited them, since it decides what happens to the evidence. If that does not work, write to us and we will help.
• Marketing: every non-essential email we send has an unsubscribe link.

If you are unhappy with how we have handled your information you can complain to the Information Regulator of South Africa (inforegulator.org.za). If you are in the EU or UK you may also complain to your local data protection authority.

We set only the cookies that make the service work. None is used for tracking or advertising, so we do not show a cookie banner.

All of these are first-party, set only by deployseal.com, and marked so other sites cannot read them.

• Everything travels over TLS. Data at rest in our database and file storage is encrypted by Azure.
• Integration tokens, two-factor secrets and webhook signing secrets are encrypted with AES-256-GCM before they reach the database. Passwords, refresh tokens and invitation links are stored as hashes.
• Sealed records are signed with a key held in Azure Key Vault that never leaves it, so a record cannot be altered without detection.
• Every organisation’s data is isolated at the database query layer. Links to evidence files expire after 15 minutes.
• Access to our operations tools requires two-factor authentication. Dependencies and container images are scanned on every change.
• If a breach affects your information we will tell the affected customers without undue delay, and the Information Regulator as POPIA section 22 requires.

Report a security concern to security@deployseal.com.

DeploySeal is a tool for businesses. It is not directed at anyone under 18, and we do not knowingly collect information from children. A customer must not invite a child as a tester.

Under the Promotion of Access to Information Act you may also request records we hold that are not your own personal information. Our PAIA manual explains what records exist, which are already published, and how to make and pay for a request. For your own personal information, section 11 above is the quicker route and carries no fee.

We will update this policy when the service changes. Material changes are announced by email to organisation owners and by a notice in the application at least 14 days before they take effect. The dates at the top show the current version.

Digidan (Pty) Ltd, trading as DeploySeal
28 George Street, Mayfair, Johannesburg, 2092, South Africa
desk@deployseal.com

Customers who need a signed data processing agreement will find it at deployseal.com/dpa.