Draft pending legal review. This text has not yet been checked by a lawyer and may change before it takes effect.
In short
- This addendum applies when we handle personal data for a business customer, for example personal data that appears on websites you ask us to monitor.
- We only use that data to provide GEO Scanner to you, keep it secure, and help you meet your duties under data protection law.
- We tell you within 48 hours if we find a breach affecting your data.
- We list our sub-processors and give 30 days' notice of changes.
- It forms part of our Terms of Service. Ask privacy@rankit.cc if you need a signed copy.
1. Scope and how this addendum applies
1.1. This Data Processing Addendum ("DPA") is between [ENTITY_NAME missing] ("we", the "Processor") and the business customer that uses GEO Scanner under our Terms of Service (the "Customer").
1.2. It applies when we process Customer Personal Data (defined below) on the Customer's behalf. It forms part of the Terms when the Customer accepts the Terms for a business purpose. A Customer may also ask for a signed copy.
1.3. If this DPA and the Terms conflict on data protection, this DPA applies. If the Standard Contractual Clauses apply and conflict with this DPA, the Standard Contractual Clauses apply.
2. Definitions
2.1. Data Protection Law means all laws on personal data that apply to the processing, including the EU General Data Protection Regulation 2016/679 ("GDPR"), the UK GDPR and Data Protection Act 2018, the Swiss Federal Act on Data Protection, the Israeli Protection of Privacy Law 5741-1981 and its regulations, and US state privacy laws, each as amended.
2.2. Customer Personal Data means personal data that we process on the Customer's behalf in providing the Service, namely:
- personal data contained in web pages of websites the Customer adds for monitoring or for scans deeper than the free scan;
- personal data the Customer gives us about other people, for example names and email addresses of colleagues or clients for reports and alerts.
2.3. Not covered. Customer Personal Data does not include data we process as a controller, as described in our Privacy Policy. This includes account and sign-in data, billing data, security logs, free scans, marketing, and anonymous statistics.
2.4. Security Incident means a breach of security leading to the accidental or unlawful destruction, loss, alteration, unauthorised disclosure of, or access to, Customer Personal Data.
2.5. Standard Contractual Clauses or SCCs means the clauses approved by European Commission Implementing Decision (EU) 2021/914. UK Addendum means the International Data Transfer Addendum issued by the UK Information Commissioner.
2.6. Terms such as "controller", "processor", "data subject", "personal data" and "processing" have the meanings given in the GDPR.
3. Roles
3.1. The Customer is the controller (or a processor acting for its own client) of Customer Personal Data. We are the processor (or sub-processor).
3.2. The Customer is responsible for having a lawful basis for the processing it asks us to do, and for giving any notices that Data Protection Law requires.
3.3. The Customer must not ask us to process special category data (such as health data), data about criminal offences, or data about children, and must not add websites whose main purpose is to publish such data.
4. Instructions
4.1. We process Customer Personal Data only on the Customer's documented instructions. The Terms, this DPA, and the Customer's use and settings in the Service are the Customer's complete instructions.
4.2. If we are legally required to process Customer Personal Data otherwise, we will tell the Customer first, unless the law forbids it.
4.3. We will tell the Customer if we think an instruction breaks Data Protection Law.
5. Our duties
5.1. Confidentiality. Everyone we allow to process Customer Personal Data is bound by confidentiality.
5.2. Security. We use the technical and organisational measures in Annex II. We may update them, but not in a way that lowers overall protection.
5.3. Sub-processors.
- (a) The Customer gives us general authorisation to use sub-processors. The current list is on our sub-processors page (Annex III).
- (b) We give the Customer at least 30 days' notice by email before a new sub-processor processes Customer Personal Data.
- (c) The Customer may object on reasonable data protection grounds within that period. If we cannot reasonably address the objection, the Customer may end the affected service and get a pro-rata refund of prepaid fees for the unused time.
- (d) We put data protection terms in place with each sub-processor that protect Customer Personal Data at least as well as this DPA. We remain responsible for our sub-processors.
5.4. Help with requests from individuals. Taking into account the nature of the processing, we help the Customer answer requests from data subjects. If we receive a request directly about Customer Personal Data, we pass it to the Customer and do not answer it ourselves unless the Customer tells us to.
5.5. Help with compliance. We give the Customer reasonable help with security, breach notifications, data protection impact assessments and prior consultations, as far as they relate to our processing and using the information available to us.
5.6. Security Incidents. We notify the Customer without undue delay, and in any case within 48 hours, after becoming aware of a Security Incident affecting Customer Personal Data. We give the information the Customer reasonably needs to meet its own duties, as it becomes available, including the nature of the incident, the categories and rough numbers of people and records involved, likely consequences and the steps we are taking. Notice is not an admission of fault.
5.7. Deletion and return. When the Service ends, we delete Customer Personal Data within 30 days, unless the law requires us to keep it. Before that, the Customer can download its Reports. Page copies and screenshots are deleted within 7 days of capture in any case. We confirm deletion in writing on request.
5.8. Records and audits.
- (a) We make available to the Customer the information reasonably needed to show compliance with this DPA, including answers to a reasonable security questionnaire once a year.
- (b) If that information is not enough, or a supervisory authority requires it, the Customer may audit our compliance, through an independent auditor bound by confidentiality, with at least 30 days' notice, during business hours, not more than once a year, at the Customer's cost. Audits of our sub-processors are carried out by relying on their own reports and certifications.
6. International transfers
6.1. Transfers to us in Israel. We are established in Israel. The European Commission has recognised Israel as giving adequate protection (Decision 2011/61/EU). Transfers of Customer Personal Data from the EEA, the United Kingdom and Switzerland to us rely on adequacy findings.
6.2. Onward transfers. Where we transfer Customer Personal Data to a sub-processor in a country without adequate protection, we make sure an appropriate safeguard is in place, such as the sub-processor's certification under the EU-U.S. Data Privacy Framework (with the UK Extension and Swiss framework) or SCCs.
6.3. Fallback SCCs. If an adequacy finding for Israel no longer covers a transfer from the Customer to us, the SCCs are incorporated into this DPA as follows:
- Module Two (controller to processor) where the Customer is a controller, and Module Three (processor to processor) where the Customer is a processor;
- Clause 7 (docking clause) applies;
- Clause 9: option 2 (general written authorisation), with the notice period in section 5.3(b);
- Clause 11: the optional language does not apply;
- Clause 13: the supervisory authority is the one that has authority over the Customer, or, where the Customer is not established in the EEA, the authority of the member state where its representative is established;
- Clauses 17 and 18: the law and courts of Ireland;
- Annexes I and II of the SCCs are completed with Annexes I and II of this DPA.
6.4. UK and Switzerland. For transfers from the UK, the SCCs apply as amended by the UK Addendum, with Table 4 allowing either party to end it. For transfers from Switzerland, the SCCs apply with references to the GDPR read as references to the Swiss Federal Act on Data Protection, and the Swiss Federal Data Protection and Information Commissioner as the competent authority where relevant.
7. Israeli law
7.1. Where the Israeli Protection of Privacy Law applies, we also act as an outsourced service provider holding data for the Customer. We follow the Customer's instructions, use the data only for the Service, apply the security measures required of us, report security incidents to the Customer as in section 5.6, and return or delete the data at the end of the Service as in section 5.7.
8. United States
8.1. Where a US state privacy law applies, we act as a "service provider" or "processor". We will not sell or share Customer Personal Data, will not keep, use or disclose it outside our direct business relationship with the Customer or for any purpose other than providing the Service, and will not combine it with other personal data except as the law allows. We will tell the Customer if we can no longer meet these duties.
9. Liability and term
9.1. Each party's liability under this DPA is subject to the limits in the Terms, except where Data Protection Law or the SCCs do not allow such limits.
9.2. This DPA lasts as long as we process Customer Personal Data.
Annex I: Description of the processing
| Item | Details |
|---|---|
| Data exporter | The Customer (controller or processor), as identified in its account |
| Data importer | [ENTITY_NAME missing], [ENTITY_ADDRESS missing], [ENTITY_COUNTRY missing]. Contact: privacy@rankit.cc. Role: processor |
| Data subjects | People whose personal data appears on the Customer's monitored websites (for example staff, authors, reviewers, contacts); people whose details the Customer gives us for reports and alerts |
| Categories of personal data | Names, job titles, business contact details, photos or other content visible on web pages and screenshots, short text snippets; names and email addresses of report recipients |
| Special categories | None intended. The Customer must not ask us to process them |
| Frequency | Continuous, for as long as the Customer uses the Service; scans run on demand and on the schedule the Customer sets (weekly or daily) |
| Nature and purpose | Fetching, rendering, screenshotting and analysing web pages; scoring; generating findings, fix suggestions and reports; optional AI analysis of extracted page text; storing results; sending reports and alerts |
| Retention | Page copies and screenshots: 7 days. Scan results: while the account is open, then deleted within 30 days of a deletion request or the end of the Service. AI result cache: 90 days |
| Sub-processors | See Annex III |
Annex II: Technical and organisational security measures
- Encryption. HTTPS (TLS) for all traffic to and from the Service. Data at rest is encrypted by our cloud provider.
- Access control. Least-privilege service accounts for each part of the system. Staff access only when needed, with strong authentication. Admin tools limited to an allowlist of named people.
- Secrets. Keys and passwords kept in a secrets manager, never in code or in the repository.
- Authentication. Passwordless sign-in with single-use links that expire after 15 minutes and are stored only as hashes. Session cookies are HttpOnly, Secure, SameSite=Lax and signed.
- Scanner isolation. The scanner blocks private, loopback, link-local, multicast and reserved IP ranges, including the cloud metadata address, re-checks every redirect, allows only ports 80 and 443, caps response size at 3 MB and runs with no access to internal services.
- Application security. Strict input validation, output escaping, Content Security Policy and other security headers, rate limits on public endpoints, verification of payment webhook signatures.
- Data minimisation. Raw page copies and screenshots deleted after 7 days by automatic lifecycle rules. AI providers receive only extracted page text, capped at about 2,000 tokens per page.
- Logging and monitoring. Structured logs, error reporting and alerts on unusual failure rates. Logs kept for 30 days.
- Resilience. Managed cloud services with built-in redundancy. Scan jobs can be retried safely.
- Vendor management. Data processing terms with each sub-processor; review of their security documentation.
- People. Confidentiality duties for everyone with access. Security and privacy training at onboarding and yearly.
- Incident response. A written incident response plan with roles, a 48-hour customer notice target, and a review after each incident.
- Deletion. Documented deletion steps covering the database, file storage and sub-processors.
Annex III: Sub-processors
The current list is on our sub-processors page and forms part of this DPA.