Ranketto Data Processing Agreement
In short
This summary is for convenience. The binding text is the agreement below.
- This agreement applies when Ranketto processes personal data on your behalf, for example data in the material you give us, or the IP addresses of people reading your blog.
- You are the controller of that data and we are the processor. We process it only on your instructions and only to provide the service.
- We use Cloudflare, OpenAI and Resend as subprocessors. You will hear about a planned change 14 days in advance and can object to it.
- We will tell you about a personal data breach within 48 hours of finding it at the latest.
- When the service ends, we delete the data.
1. Parties and conclusion
- This Data Processing Agreement ("DPA") is concluded between the Customer as the controller ("Controller") and Arkadiusz Woźniak, who runs a sole proprietorship under the business name ASTROWARE Arkadiusz Woźniak, address: Rudka Kozłowiecka 102, 21-025 Niemce, Poland, tax ID (NIP): 7133133330, REGON: 529234783, as the processor ("Processor", "we").
- The DPA is concluded electronically when the Customer accepts the Ranketto Terms of Service and forms part of the Contract. It applies when, within Ranketto, we process personal data on the Customer's behalf.
- If the Customer itself processes data on behalf of another controller, for example as an agency working for its clients, the Customer confirms that it has that controller's authorisation to engage us and that its instructions are consistent with that controller's instructions. In that case we act as a sub-processor, and this DPA applies accordingly.
- Terms used in this DPA have the meaning given in Regulation (EU) 2016/679 of the European Parliament and of the Council (GDPR). Capitalised terms such as Contract, Content and Customer Materials also have the meaning given in the Terms of Service.
2. Subject matter, nature and purpose of processing
- The DPA covers personal data contained in Customer Materials, in Content and in Google Search Console data, where they contain any, and technical data of people who visit sites where we show Content. Annex 1 describes the categories of data subjects and data.
- Processing consists of storing the data, analysing it (also with AI models), creating and publishing Content, delivering Content to visitors, sending e-mails as part of the Service, and deleting the data.
- The only purpose of processing is to provide the Service under the Contract.
- Processing lasts for the term of the Contract and the Content storage period in clause 12.3 of the Terms of Service, until the data is deleted under clause 9.
3. Controller's instructions
- We process data only on documented instructions from the Controller, including with regard to transfers to a third country, unless Union or Member State law requires us to process it. In that case we tell the Controller about that legal requirement before processing, unless that law prohibits this on important grounds of public interest.
- Documented instructions are the Contract, including the Terms of Service and this DPA, the Controller's settings and actions in the Dashboard (such as choosing the Publishing Mode and approving Content), and other instructions sent by e-mail that are consistent with the Contract.
- We tell the Controller without delay if, in our opinion, an instruction infringes the GDPR or other data protection law.
4. Processor's obligations
- Only people we have authorised can access the data, and they have committed to confidentiality or are under a statutory obligation of confidentiality.
- We take the security measures required by Article 32 GDPR. Annex 2 describes them.
- As far as possible, we help the Controller respond to requests from data subjects exercising their rights under Chapter III GDPR. If a data subject contacts us directly, we pass the request to the Controller without undue delay and do not answer it ourselves without the Controller's instruction.
- Taking into account the nature of processing and the information available to us, we help the Controller meet its obligations under Articles 32 to 36 GDPR: security, breach notification, data protection impact assessments and prior consultation with the supervisory authority.
- Where the law requires it, we keep the record of categories of processing activities referred to in Article 30(2) GDPR.
5. Personal data breaches
- When we become aware of a breach of personal data we process on the Controller's behalf, we notify the Controller without undue delay, and no later than 48 hours, at the e-mail address linked to the Account.
- The notice contains the information we have at the time, in particular the nature of the breach, the categories and approximate number of data subjects and records concerned, its likely consequences, and the measures taken or proposed to address it. Information that cannot be given at once is provided in phases without undue further delay.
- Notifying the supervisory authority and informing data subjects is the Controller's responsibility. We help with both.
6. Subprocessors
- The Controller gives general authorisation for us to use subprocessors. Annex 3 lists the current ones.
- We tell the Controller by e-mail at least 14 days in advance about any intended addition or replacement of a subprocessor. During that time the Controller may raise a reasoned objection. If we cannot agree, the Controller may terminate the Contract with effect from the date of the change, and we refund the part of the fee for the unused period.
- We impose on each subprocessor, by contract, the same data protection obligations as in this DPA, in particular sufficient guarantees of appropriate technical and organisational measures. If a subprocessor fails to meet its obligations, we remain liable to the Controller for it.
7. Transfers outside the EEA
- Data may be transferred outside the European Economic Area only under the conditions of Chapter V GDPR: on the basis of a European Commission adequacy decision, including for recipients in the United States certified under the EU-U.S. Data Privacy Framework, or on the basis of the standard contractual clauses adopted by the European Commission (Article 46(2)(c) GDPR), with additional safeguards where needed.
- By accepting this DPA, the Controller instructs such transfers to the extent needed for the subprocessors in Annex 3 to provide the Service.
8. Information and audits
- We make available to the Controller the information needed to demonstrate that we meet our obligations under Article 28 GDPR. We do this first through written answers to questions, documentation, and our providers' reports and certificates where available.
- If that information is not enough, we allow the Controller, or an auditor it appoints who is bound by confidentiality, to carry out an audit, including an inspection. An audit is announced at least 30 days in advance. It takes place no more than once in 12 months, unless a supervisory authority requires it or it follows a personal data breach. It is carried out during business hours, without disrupting Ranketto and without breaching the confidentiality of other customers' data. The Controller bears the cost of the audit.
- For subprocessors, we give the Controller the reports, certificates or other compliance information we receive from them.
9. End of processing
- When the Service ends, meaning when the Contract ends or when the Content storage period in clause 12.3 of the Terms of Service runs out, we delete the personal data processed on the Controller's behalf and existing copies, unless Union or Member State law requires us to keep it. If the Controller deletes the Account, we delete the data at once. If the Controller deletes a single Customer Site, we delete its Content at once and the site's basic record (name, address, Profile and settings) 90 days later.
- If the Controller asks for the personal data to be returned before the Contract ends, we provide a copy in a commonly used electronic format. This covers the personal data processed on the Controller's behalf and does not mean an export of Content, which the Contract does not provide for (clause 11.4 of the Terms of Service).
- Data deleted from the system disappears from backups in the normal backup overwrite cycle, within 30 days at the latest.
10. Liability
- The parties' liability for breach of this DPA is governed by the Terms of Service, including the limits for Business Customers in clause 21 of the Terms of Service, to the extent the GDPR allows. This does not limit liability towards data subjects (Article 82 GDPR).
11. Final provisions
- This DPA applies for as long as we process personal data on the Controller's behalf.
- On data protection matters, this DPA takes precedence over the Terms of Service.
- This DPA is changed in the same way as the Terms of Service (clause 23 of the Terms of Service).
- This DPA is governed by Polish law.
- This DPA applies from 19 November 2026.
Annex 1. Description of processing
| Categories of data subjects | Categories of data |
|---|---|
| People whose data the Customer includes in Customer Materials or who appear on the Customer Site, such as the Customer's staff, authors and clients | name, job title, contact details and other data the Customer chooses to provide |
| People who visit sites where we show Content | IP address, browser type, address of the page visited, time of the request |
Processing does not cover special categories of personal data (Article 9 GDPR) or data relating to criminal convictions (Article 10 GDPR), and the Customer does not provide such data. Data is processed continuously for the term of the Contract.
Annex 2. Technical and organisational measures
- encrypted connections (TLS) between the browser, Ranketto and providers;
- encryption of Google access tokens (AES-GCM) with a key kept as an environment secret, outside the database;
- sign-in without passwords (with Google or a one-time link), and sessions in cookies with the HttpOnly, Secure and SameSite=Lax attributes, limited to the Dashboard's domain;
- separate domains: the Dashboard and API run only on app.ranketto.com, and Content and other text created by AI models is never served from that domain;
- HTML created by AI models is cleaned to an allowlist of elements;
- Content is served on a domain only after the Customer confirms control of it with a DNS TXT record or, for the WordPress plugin, with an API key that the Customer enters in its WordPress site;
- the tool that reads web pages is protected against requests to private and internal addresses and has limits on size, time and redirects;
- Stripe notification signatures are verified, and API requests are rate limited;
- access to production data only for authorised people;
- database backups with point-in-time restore;
- a procedure for handling incidents and notifying breaches (clause 5);
- choosing subprocessors that give sufficient guarantees, and signing data processing agreements with them.
Annex 3. Subprocessors
| Subprocessor | Scope | Location and safeguards |
|---|---|---|
| Cloudflare | hosting, page delivery, databases and files, protection against attacks | data centres worldwide, including in the United States; safeguards under clause 7.1 |
| OpenAI | writing and checking text based on Customer Materials, including the content of the Customer Site, and preparing title suggestions from a page's text and its Search Console figures | United States; safeguards under clause 7.1 |
| Resend | sending service e-mails that may contain data processed on the Controller's behalf, such as titles of Content | e-mails are sent from Resend's EU region (Ireland); Resend is a company in the United States; safeguards under clause 7.1 |
Stripe (payments) and Google (sign-in, Search Console API) are not subprocessors under this DPA. Stripe processes billing data for which we are the controller, and Google provides Google Search Console data under the Controller's own agreement with Google. The Privacy Policy describes both providers.