This Data Processing Addendum ("DPA") forms part of the Terms of Service for customers who use LocalCan on behalf of a business ("Customer"). It applies where LocalCan processes personal data on the Customer's behalf and the GDPR or similar data protection law applies. It takes effect automatically; if your procurement process requires a countersigned copy, contact support@localcan.com.
For the data covered by this DPA ("Covered Data"), the Customer is the controller and LocalCan is the processor. Covered Data means:
For account, billing, and product data, LocalCan is an independent controller as described in the Privacy Policy; that data is not Covered Data.
We process Covered Data only on the Customer's documented instructions. The Terms, this DPA, the Customer's configuration in the dashboard (including its LocalCan Access apps, sign-in methods, rules, blocks and sign-outs), and the instructions sent by the Customer's identity provider (for example SCIM provisioning and deprovisioning requests) together constitute those instructions. We will inform the Customer if we believe an instruction infringes applicable data protection law. We transfer Covered Data outside the European Economic Area only as section 11 describes. If European Union or Member State law requires us to process Covered Data in another way, we will tell the Customer first, unless that law forbids it.
The Customer gives the people who sign in to its apps through LocalCan Access the information data protection law requires, including those who sign in through the Customer's own identity provider and may never see a LocalCan page.
Persons we authorize to process Covered Data are bound by confidentiality obligations.
We protect Covered Data with technical and organizational measures appropriate to the risk, including encryption in transit (TLS), encryption of the database and its backups at rest, access controls, and the measures described in the Privacy Policy, with further detail on our Security page. Operational logs can contain email addresses, for example of the recipient of an email we send, and IP addresses, including a viewer's IP address and browser user agent on our LocalCan Access sign-in service. The log provider listed in section 9 of the Privacy Policy keeps them for 30 days, in Germany.
The Customer gives general authorization for the subprocessors listed in section 9 of the Privacy Policy. A team's own identity provider, connected for single sign-on or for LocalCan Access, is chosen and contracted by the Customer and is not our subprocessor. The data it sends us is stored with our existing hosting provider in the European Union. Sign-in with Google, Microsoft or GitHub in LocalCan Access runs through our own sign-in service and is described in section 9 of the Privacy Policy. We bind each subprocessor by written contract to data protection obligations that protect Covered Data as well as this DPA does. We will give reasonable notice of subprocessor changes, for example by updating the Privacy Policy and notifying customers, and the Customer may object on reasonable data protection grounds. We remain responsible for our subprocessors' performance.
Taking into account the nature of the processing, we will assist the Customer with requests from data subjects to exercise their rights. If a team member or a viewer contacts us directly about Covered Data, we will refer them to the Customer or involve the Customer in the response.
We will notify the Customer without undue delay after becoming aware of a personal data breach affecting Covered Data, with the information reasonably needed to meet the Customer's own notification obligations.
We will provide reasonable assistance with data protection impact assessments and prior consultations with supervisory authorities, to the extent they concern Covered Data.
Deprovisioning a team member removes their membership, invalidates their license key, and ends their sessions. Their underlying account record is deleted on the Customer's request. Thirty days after the Customer's paid plan is cancelled, we delete its public URLs, custom domains and Snapshot archives, and, unless the Customer still has LocalCan Access, its LocalCan Access apps and the identities and block list of its viewers. A Customer on the Free plan that ends LocalCan Access keeps these until it asks us to delete them. Team membership, license keys and the team record are kept so the Customer can resume, and we delete them, and any other Covered Data, on the Customer's request, unless applicable law requires us to keep it. Copies in our encrypted database backups are deleted as those backups expire, after about 13 months. Tunnel traffic is never stored, so there is nothing to return or delete for the conduit role. Snapshot archives are deleted when the Customer deletes the Snapshot or its public URL.
Before deleting, we return a copy of the Customer's Covered Data on request.
For LocalCan Access, viewer sign-in sessions are deleted 7 days after they expire and access log entries after 90 days. When the Customer asks us to erase a viewer, we find them by email address and delete their identities, sessions, agreements and access log entries at once. We can find a viewer by the address the Customer's sign-in rules match for as long as we keep their identity. Other addresses their sign-in provider sent, such as a secondary GitHub address, are kept only in their sign-in sessions, so they find the viewer only until those sessions are deleted. Audit log entries that name a blocked or unblocked email address, or the admin who acted, are not deleted.
We will make available the information reasonably necessary to demonstrate compliance with this DPA, including answering reasonable written security questionnaires, and we allow for and contribute to audits, including inspections, by the Customer or an auditor it appoints. Audits are limited to once per year unless a supervisory authority requires otherwise, must be agreed in advance, and must not disrupt the service.
Covered Data is stored in the European Union. Our edge servers, including those outside the European Union, relay tunnel traffic and LocalCan Access requests, including a viewer's IP address and identity token, and keep cached copies of published Snapshots. Where a subprocessor processes data outside the European Economic Area, the transfer is covered by appropriate safeguards such as the European Commission's Standard Contractual Clauses, as described in section 10 of the Privacy Policy.
This DPA applies for as long as we process Covered Data for the Customer. Liability under this DPA follows the limitations in the Terms of Service.
LocalCan is operated by:
Questions about this DPA: support@localcan.com.
Last updated: November 15, 2026