SevenOS Data Processing Agreement
Version 1.7 of 21 November 2026
This is an English translation of the SevenOS Data Processing Agreement, provided for the Controller's convenience only. The legally binding text is the Polish version; in the event of any discrepancy the Polish version prevails (§ 14(5)).
Template of the agreement on entrusting the processing of personal data concluded with Clients of the SevenOS service. The Agreement forms part of the Main Agreement for the provision of the SevenOS service (Terms, § 5(4)). The dotted fields are completed when the Agreement is concluded.
concluded on ………………… — or, if the Parties conclude it upon accepting the SevenOS Terms of Service, at the moment of that acceptance —
between:
………………………………………………… (business name, legal form, registered office address, NIP tax number, KRS number or CEIDG entry, and for an entity established outside Poland: the country of establishment, tax identification number and register), represented by ………………………………, hereinafter the “Controller”,
and
Adrian Hunia, a sole trader doing business under the registered business name “SEVENEDGE ADRIAN HUNIA”, entered in the Polish Central Register and Information on Business Activity (CEIDG), NIP (tax ID) 6842688170, REGON 544617676, address: ul. Spacerowa 31, 38-420 Kombornia, e-mail: contact@sevenedge.pl, phone +48 691 957 922, hereinafter the “Processor” or “SEVENEDGE”,
hereinafter jointly the “Parties”.
§ 1. Definitions
- GDPR — Regulation (EU) 2016/679 of the European Parliament and of the Council of 27 April 2016 on the protection of natural persons with regard to the processing of personal data and on the free movement of such data, and repealing Directive 95/46/EC.
- Main Agreement — the agreement for the provision of the SevenOS service concluded between the Parties, together with the SevenOS Terms of Service for services provided by electronic means (the “Terms”) and the Price List.
- Service — the SevenOS service described in the Main Agreement, including the Modules and Central Services within the meaning of the Terms.
- Data — personal data processed by the Processor on behalf of the Controller in connection with the performance of the Main Agreement, described in § 4 and Annex 1.
- Sub-processor — another processor engaged by the Processor to carry out specific processing activities on behalf of the Controller (Article 28(4) GDPR).
- Breach — a personal data breach within the meaning of Article 4(12) GDPR concerning the Data.
- Provider-hosted Installation, Client-server Installation, Central Services, External Services, Account, Panel, User, Business Day — have the meaning given to them in the Terms.
- Other terms (including “processing”, “controller”, “processor”, “third country”) have the meaning given to them in the GDPR.
§ 2. Subject matter and duration
- The Controller entrusts the Processor with the processing of Data on behalf of the Controller, to the extent and for the purpose specified in the Agreement, and the Processor undertakes to process it in accordance with the Agreement, the GDPR and other provisions on the protection of personal data.
- The Agreement is concluded for the term of the Main Agreement and the data retrieval period referred to in the Terms (§ 22), and its provisions on deletion or return of Data, confidentiality and liability remain in force until they are performed.
- The Processor is not entitled to separate remuneration for performing the Agreement beyond the remuneration under the Main Agreement, subject to § 9(4) and § 11(5).
§ 3. Nature and purpose of processing
- Purpose of processing: provision of the Service to the Controller, including in particular:
- maintaining the Account, authentication and authorisation of Users, ensuring security and accountability (audit log),
- obtaining from sources indicated by the Controller (Useme, Oferia, public Facebook groups, the Public Procurement Bulletin, Baza Konkurencyjności, platformazakupowa.pl) listings, posts, procurement notices and requests for quotation, rating them using AI models, saving them to the lead list, at a User's request analysing a procurement notice or request for quotation using an AI model and, on the Controller's instruction, sending notifications about them,
- maintaining the sales pipeline, tasks and calendar,
- handling the Controller's Facebook accounts: searching for posts and comments in groups and on pages indicated by the Controller, preparing AI drafts and publishing content approved by a User,
- running the AI Assistant (answers to a User's questions about Account data, summaries),
- running the SEO workshop (projects, measurements, audits, content) and the “Google Business Profile” Module (business profile data, reviews and replies, posts, statistics, AI drafts),
- making backups, updates, exports and deletion of Data and handling service requests,
- providing a page with information on processing and an objection form for data subjects, keeping a list of objections and preparing short match patterns without personal data from Users' ratings (§ 9(1)(3), Annex 1).
- Nature of processing: automated processing in an IT system, comprising the following operations: collection (including automated retrieval from publicly available websites on the Controller's instruction), recording, organisation, structuring, storage, adaptation, retrieval, consultation, use (including analysis and rating by AI models), disclosure by transmission (to AI model providers and to External Services on the Controller's instruction), alignment, restriction, erasure and destruction.
- The Processor does not take decisions concerning data subjects based solely on automated processing that produce legal effects or similarly significantly affect them (Article 22 GDPR). The AI rating of how well a listing matches serves only to organise the Controller's lead list; the decision to make contact is taken by the Controller.
§ 4. Types of Data and categories of data subjects
-
The following categories of data subjects and Data are entrusted (details in Annex 1):
Category of data subjects Types of Data Panel Users (employees and associates of the Controller) first name or display name, e-mail address, password hash (bcrypt), role, permissions, account status, history of actions in the audit log, content of conversations with the AI Assistant, data on use of the Service and costs assigned to the User Authors of listings and posts obtained from sources indicated by the Controller (natural persons, including entrepreneurs) name and surname or profile name, content of the listing or post, title, budget, publication date, name of the group or category, URL, contact details provided by the author in the content (e.g. phone, e-mail), the match rating and its justification generated by AI, ratings and pipeline stage assigned by Users, and if the author has objected, also a hash of their name Persons designated for contact in procurement notices and requests for quotation obtained from sources indicated by the Controller (employees and associates of contracting authorities) name and surname, position or organisational unit, business e-mail address and phone number, to the extent published by the contracting authority, together with the content of the notice, the name of the contracting authority, the URL, the match rating and its justification; in the AI analysis of a notice, e-mail addresses, phone numbers and the designated contact person are replaced with a placeholder before sending to the model and before saving Persons submitting an objection through the form on the Account's information page ( /dane)the profile name given in the form, stored only as a SHA-256 hash with the Account identifier, without the name itself; the date of submission; an audit log entry without the name; the IP address in server memory for the purpose of the submission limit and in the web server log, as with every visit to the page Authors of posts and comments in Facebook groups and pages in which the Controller's accounts operate name and surname or profile name, identifier and address of the post or comment, content, draft reply and AI hints Holders of the Controller's Facebook accounts account name, account role and guidelines, account session cookies (authentication data), user agent and any proxy server indicated by the Controller, the bot's browser profile Business partners, customers and contact persons of the Controller entered into the Panel data entered by Users in tasks, calendar appointments, pipeline notes and the knowledge base (free text) Authors of reviews in the Controller's Google Business Profile first name or display name of the author, content and rating of the review, date, content of the reply Persons whose data appears in the Controller's SEO projects in exceptional cases: proper names and contact details appearing in the content of analysed websites, keywords and reports -
The Controller does not intend to entrust special categories of data (Article 9 GDPR) or data relating to criminal convictions and offences (Article 10 GDPR). The Controller acknowledges that the content of listings and posts retrieved automatically from sources indicated by the Controller (e.g. topical groups) may contain such data if their authors have disclosed it themselves (e.g. posts asking for legal or medical help). The Controller selects sources and keywords so as to limit this risk, and the Parties apply to such Data the measures set out in Annex 2 and the retention rules in § 12(5). A post from a public Facebook group that the AI model has rated as containing health data, criminal matters or other special categories of data is not passed to the Controller as a lead, and the Service does not store its content, author or URL (Annex 2, Part I).
§ 5. Obligations of the Processor
- The Processor:
- processes Data only on documented instructions from the Controller (Article 28(3)(a) GDPR), including with regard to transfers of Data to a third country; the instructions are: the Agreement, the Main Agreement, the configuration of the Account and Modules made by the Controller or Users in the Panel (e.g. indicating groups, categories, keywords, accounts, a Telegram chat identifier, approving a publication) and instructions given in documentary form by persons authorised by the Controller; if Union law or Polish law requires the Processor to process Data, the Processor informs the Controller of that legal requirement before processing, unless the law prohibits such information,
- immediately informs the Controller if, in its opinion, an instruction infringes the GDPR or other data protection provisions (Article 28(3), second subparagraph, GDPR),
- ensures that persons authorised to process Data have committed themselves to confidentiality or are under an appropriate statutory obligation of confidentiality, also after the end of their cooperation (Article 28(3)(b) GDPR); access to Data is granted only to persons for whom it is necessary to provide the Service (persons responsible on the Processor's side for maintaining and supporting the Service),
- applies the technical and organisational measures referred to in Article 32 GDPR, described in Annex 2, and maintains them throughout the processing period; it may change them, provided that the change does not reduce the overall level of security,
- complies with the conditions for engaging Sub-processors set out in § 7,
- assists the Controller in fulfilling the rights of data subjects and the obligations under Articles 32 to 36 GDPR, in accordance with § 9 and § 10,
- after the end of the provision of services, deletes or returns the Data in accordance with § 12,
- makes available to the Controller all information necessary to demonstrate compliance with the obligations under Article 28 GDPR and allows for audits in accordance with § 11,
- maintains a record of categories of processing activities carried out on behalf of the Controller (Article 30(2) GDPR).
- The Processor does not use the Data for its own purposes, in particular to train AI models, to carry out its own sales or to make it available to other clients of the Service. The fact that the Processor, independently and as a separate controller, obtains data for its own needs from the same public sources (e.g. the same listings website) does not constitute a breach of the Agreement, provided that these data sets are logically separated and the Data is not used beyond the purpose set out in § 3.
- The Processor is not responsible for the lawfulness of the sources and purposes of processing determined by the Controller (in particular the choice of groups and websites from which listings are retrieved and the content published by the Controller), provided that it processes the Data in accordance with the instructions, subject to section 1(2).
§ 6. Obligations of the Controller
- The Controller declares that it processes the Data lawfully, has a legal basis for its processing and fulfils the information obligations under Articles 13 and 14 GDPR towards data subjects — in particular, it informs the authors of listings and posts with whom it makes contact, at the latest at the first contact. For this purpose, the Controller may use the tools referred to in § 9(1)(3), and it enters the details of its company needed for the information in the Account Settings and is responsible for their accuracy.
- The Controller is responsible for the choice of sources, keywords, accounts and content, for compliance with the terms of External Services and for determining the retention periods of Data within the functions provided in the Service.
- The Controller ensures that Users have been authorised to process the Data and have committed themselves to keeping it confidential.
- The Controller promptly informs the Processor of changes affecting the processing (e.g. revocation of a User's authorisation, requests of data subjects requiring action by the Processor).
§ 7. Sub-processing (Sub-processors)
- The Controller grants the Processor general written authorisation to engage Sub-processors (Article 28(2) GDPR). The list of Sub-processors as at the date of conclusion of the Agreement constitutes Annex 3.
- The Processor informs the Controller of any intended changes concerning the addition or replacement of a Sub-processor by e-mail to the address indicated by the Controller and by a message in the Panel at least 14 days before the change, indicating the name of the Sub-processor, the scope of activities, the location of processing and the basis for any transfer.
- The Controller may object to the change within 14 days of receiving the information, in documentary form, stating justified reasons related to data protection. In that case, the Parties seek a solution in good faith (e.g. disabling the function using the new Sub-processor for the Controller's Account). If no solution is agreed within 30 days, the Controller may terminate the Main Agreement with respect to the Module affected by the change, or in its entirety, without notice and without the obligation to pay fees for the period after termination. Failure to object means acceptance of the change.
- In an emergency, where a change of Sub-processor is necessary for the security or continuity of the Service (e.g. a supplier failure), the Processor may make the change immediately, informing the Controller no later than on the day of the change; the Controller then has the right to object on the terms of section 3.
- The Processor imposes on the Sub-processor, by way of a contract, the same data protection obligations as those arising from the Agreement, in particular the obligation to provide sufficient guarantees to implement appropriate technical and organisational measures (Article 28(4) GDPR). This requirement is deemed to be met if the Sub-processor processes data under a standard data processing agreement (DPA) offered by it to all business customers, ensuring a level of protection not lower than that required by Article 28 GDPR.
- Where a Sub-processor fails to fulfil its data protection obligations, the Processor remains fully liable to the Controller for the performance of that Sub-processor's obligations.
- Entities with which the Service integrates or from which it obtains data on the Controller's instruction, and which process data on their own terms as separate controllers or as service providers of the Controller, are not Sub-processors (in particular Meta — Facebook, Google — Search Console and Google Business Profile, the Useme and Oferia services, Telegram). The list of these External Services constitutes Part B of Annex 3. By configuring an integration with them, the Controller instructs that Data be transmitted to them to the extent necessary for the integration to work.
- In the Client-server Installation, the server provider chosen by the Controller is the Controller's processor under a separate agreement concluded by the Controller and is not a Sub-processor of the Processor.
- Operators of proxy servers through which the retrieval module connects to source websites are not Sub-processors, because the connection is encrypted from the retrieval module to the website and the operators have no access to the Data (Part C of Annex 3).
§ 8. Transfers of Data to third countries
- The Processor may transfer Data to a third country (outside the European Economic Area) only on the documented instruction of the Controller resulting from the Agreement and only where one of the grounds set out in Chapter V GDPR is ensured, in particular:
- an adequacy decision (Article 45 GDPR), including Commission Implementing Decision (EU) 2023/1795 of 10 July 2023 on the EU-US Data Privacy Framework — with respect to recipients in the USA certified under that framework,
- standard contractual clauses adopted by Commission Implementing Decision (EU) 2021/914 of 4 June 2021 (module 2 or 3), concluded with the recipient, together with a transfer impact assessment and, where necessary, supplementary measures.
- According to the state as at the last update of Annex 3, Data may be transferred outside the EEA in particular to AI model providers (Anthropic, within the Anthropic group to the USA; OpenAI, within the OpenAI group to the USA; Perplexity, USA), to the provider of e-mail sending from the Panel (Resend, USA), to infrastructure providers of Sub-processors and in connection with remote access from Ukraine at the SEO data provider (DataForSEO), in accordance with Annex 3.
- The Parties acknowledge that by judgment of 3 September 2025 in case T-553/23 Latombe v Commission, the General Court of the European Union dismissed the action against Decision (EU) 2023/1795, and that an appeal against the judgment has been brought before the Court of Justice of the EU. If that decision is annulled or suspended, the Processor will promptly ensure another basis for the transfer (in particular standard contractual clauses) or cease the transfer and inform the Controller accordingly.
- At the Controller's request, the Processor provides a copy (or an appropriate extract) of the transfer mechanism applied to a given Sub-processor.
- Controller established outside the EEA. If the Controller is established in a third country for which the European Commission has not adopted an adequacy decision (Article 45 GDPR), the making available of Data to the Controller by the Processor (in particular in the Panel, in exports, in notifications and in e-mail messages) takes place on the basis of the standard contractual clauses adopted by Commission Implementing Decision (EU) 2021/914 of 4 June 2021, in module four (transfer from processor to controller). The Parties incorporate these clauses into the Agreement by reference, without changes to their content, upon its conclusion. For the purposes of the clauses: the data exporter is the Processor, the data importer is the Controller, the description of the transfer (Annex I) consists of the parties indicated at the beginning of the Agreement, § 3, § 4 and Annex 1, clause 7 (docking clause) and the option in clause 11(a) do not apply, and the governing law and courts for the clauses (clauses 17 and 18) are Polish law and the Polish courts. In the event of a conflict, the clauses take precedence over the Agreement. This section does not apply to a Controller established in an EEA country or in a country covered by such a decision.
§ 9. Assistance to the Controller
- Data subject rights. Taking into account the nature of the processing, the Processor assists the Controller by appropriate technical and organisational measures in fulfilling the obligation to respond to requests from data subjects to exercise their rights (Chapter III GDPR), in particular it:
- forwards to the Controller promptly, not later than within 3 Business Days, any request addressed directly to the Processor by a data subject and does not respond to it on its own, unless the Controller authorises it to do so,
- provides functions in the Panel to find, export, correct and delete Data (e.g. a lead, a task, an appointment, a knowledge base entry, a task of the “Facebook Engagement” Module), and to the extent there is no such function, performs these activities on the Controller's instruction within 7 days of receiving it,
- provides tools in the Service that help the Controller fulfil the information obligation under Article 14 GDPR and handle objections under Article 21 GDPR, namely a public page with information on processing at the Panel address (
/dane) with an objection form, filled in with the Controller's details entered in the Settings, a text of the information to be given to the author at the first contact, and marking an objection in the lead card; an objection causes new posts and listings of that author (recognised by name) to be rejected before rating by the AI model and before being saved, and the Data already collected is subject to § 12(5) or deletion on the Controller's instruction in the manner described in point 2.
- Security, impact assessment, consultations. The Processor assists the Controller in fulfilling the obligations under Articles 32 to 36 GDPR, in particular by providing information on security measures, the operation of the Modules (including the source Modules and the “Facebook Engagement” Module) and on Sub-processors needed to carry out a data protection impact assessment and prior consultation with the supervisory authority.
- The Processor promptly informs the Controller of any proceedings, inspection or request of the supervisory authority or another authority concerning the Data, unless the law prohibits it.
- Assistance going beyond the standard functions of the Service and beyond what the Processor can perform within a reasonable time may be charged at rates agreed before it is provided, except for assistance related to a Breach on the Processor's side.
§ 10. Personal data breaches
- After becoming aware of a Breach, the Processor notifies the Controller without undue delay, and not later than within 24 hours of becoming aware of it, by e-mail to the address indicated by the Controller for such notifications (in the Main Agreement or in the Panel), and if the Controller has provided a phone number, also by phone.
- The notification contains, as far as the information is available:
- a description of the nature of the Breach, including, where possible, the categories and approximate number of data subjects concerned and the categories and approximate number of data records concerned,
- the name and contact details of the person from whom more information can be obtained,
- a description of the likely consequences of the Breach,
- a description of the measures taken or proposed to address the Breach, including measures to mitigate its possible adverse effects.
- Where it is not possible to provide all the information at the same time, the Processor provides it in phases without undue further delay. Lack of complete information does not delay the first notification.
- The Processor promptly takes action to limit the consequences of the Breach, secures evidence, documents the Breach in its register of breaches and cooperates with the Controller in assessing the risk, notifying the President of the Polish Personal Data Protection Office (UODO) (Article 33 GDPR) and communicating the Breach to data subjects (Article 34 GDPR). The Processor does not notify the supervisory authority or data subjects on behalf of the Controller without the Controller's instruction, unless such an obligation arises from the law.
- A Breach also includes, in particular: unauthorised disclosure of the Controller's Facebook account session cookies, API keys or Google tokens stored in the Service, and access by one Account to the data of another Account.
§ 11. Audits and inspections
- The Controller has the right to verify whether the Processor processes the Data in accordance with the Agreement, in particular by:
- requesting information and documents (in the first place in the form of a questionnaire), to which the Processor responds within 14 days,
- an audit carried out by the Controller or by an independent auditor bound by a confidentiality obligation and not being a competitor of the Processor.
- The audit referred to in section 1(2) requires notice at least 14 days in advance and is carried out on Business Days, during working hours, not more often than once a year, unless a Breach has occurred or the supervisory authority so requires. The audit is carried out remotely where possible, without access to the data of other clients of the Processor and without disrupting the provision of the Service.
- With respect to Sub-processors, the audit is performed by making available the certificates, reports and documentation of those entities.
- A report is drawn up from the audit; the Processor remedies the irregularities found within the period agreed by the Parties, not longer than 30 days, unless a longer period is needed due to their nature.
- The costs of the audit are borne by the Controller, unless the audit reveals a material breach of the Agreement by the Processor.
§ 12. End of processing — deletion or return of Data
-
After the end of the provision of the Service, the Processor, at the choice of the Controller, returns the Data (in the form of the export described in § 22(1) of the Terms) and deletes all existing copies of it, unless Union law or Polish law requires storage of the Data.
-
The Controller may request an export of the Data during the data retrieval period of 30 days from the end of the Main Agreement. After that period, the Processor deletes the Data from production systems, including from the Central Services (listings fetched for the Account, sessions and browser profiles of Facebook accounts, copies of business profile data, the Account's SEO projects and Google tokens, Account keys), and from backups in their rotation cycle.
-
In the Client-server Installation, the Data stored in the database on the Controller's server remains under the Controller's exclusive control; the Processor deletes the Data stored in the Central Services and in its own infrastructure, as well as its access data to the Controller's server.
-
At the Controller's request, the Processor confirms the deletion of the Data in documentary form.
-
Retention during the Agreement. The Controller instructs that the Service automatically delete once a day:
- the content, title, URL, author data and contact details of listings and posts that the AI model has rated as not being leads, 7 days after the rating,
- the same fields of leads rated by a User as bad, 7 days after the rating, unless the lead is in a pipeline stage marked as open or won,
- the same fields of other leads from sources, 12 months after they were saved,
- the content, author and address of third-party posts and comments in the “Facebook Engagement” Module, 7 days after the task is rejected or skipped, and in other cases 12 months after they were saved,
- the copy of listings and posts in the source engine (Central Services), used for deduplication and re-rating, 7 days after retrieval.
Deletion consists of clearing the fields containing personal data; an entry without them remains (in particular the identifier, date, source, group name and rating) so that the Service does not save the same listing again. Manually entered leads and Users' notes, tasks, appointments and ratings are not subject to automatic deletion; the Controller deletes this Data in the Panel or in the manner described in § 9(1)(2). Automatic deletion does not cover lead summaries sent on the Controller's instruction via Telegram, Discord and in the morning e-mail summary, or backups, from which the Data disappears in their rotation cycle. The Controller may instruct shorter periods or earlier deletion in documentary form. The Processor keeps other Data for the term of the Main Agreement.
§ 13. Liability
- The Parties are liable for damage caused to data subjects on the terms of Article 82 GDPR.
- The Processor is liable to the Controller for damage resulting from processing the Data contrary to the Agreement or to the obligations imposed by the GDPR directly on processors, on the terms and within the limits set out in the Main Agreement.
- The Controller is liable to the Processor for damage resulting from unlawful instructions, the lack of a legal basis for processing or the Controller's failure to fulfil its information obligations.
§ 14. Final provisions
- In matters of personal data protection, the Agreement takes precedence over the Main Agreement and the Terms.
- Amendments to the Agreement must be made in documentary form, otherwise they are null and void, except for updates of Annex 3 in the manner described in § 7 and of Annex 2 in the manner described in § 5(1)(4).
- The Agreement is governed by Polish law. Disputes are resolved by the court competent under the Main Agreement.
- The Agreement is concluded in electronic form or in documentary form, in particular upon acceptance of the SevenOS Terms of Service.
- The Agreement is drawn up in Polish. The Processor may make its English translation available solely for the Controller's convenience; in the event of any discrepancy, the Polish version is binding.
Annexes:
- Description of processing.
- Technical and organisational measures.
- List of Sub-processors and External Services.
| Controller | Processor |
|---|---|
| ……………………………… | ……………………………… |
Annex 1 — Description of processing
| Area of the Service | Data | Operations | Where processed |
|---|---|---|---|
| Account, Users, Roles, audit | User data (§ 4) | creating accounts, login, authorisation, audit log (security events, changes of permissions and roles, decisions in the “Facebook Engagement” Module, pipeline changes) | the Account database (Provider-hosted Installation — the Service Provider's server in Poland; Client-server Installation — the Controller's server) |
| User activity log | User identifier and name, type and time of the activity in the Panel (opening a lead, changing a stage, rating, note, assigning an owner, task, appointment, login), identification of the lead to which the activity relates | automatic recording upon the activity (opening a lead at most once per 30 minutes per User and lead), presentation to the Controller (counters and a person's timeline, statistics of reactions to leads) and to the Service Provider as part of support and Account handling | the Account database |
| Lead sources (Useme, Oferia) | content and metadata of jobs, author data, contact details from the content | automatic retrieval from the service's pages, rating by the AI model, saving in the source engine and passing to the Panel (listings that are not leads without content and author data), Telegram or Discord notification (optional) | the source engine on the Service Provider's server (a database with a tenant identifier, keeping the source text for deduplication and re-rating for 7 days, § 12(5)); AI model (Anthropic); the Account database |
| Lead source (Tenders) | content of the procurement notice or request for quotation, the contracting authority, persons designated for contact and their business contact details (if published by the contracting authority), deadlines, value, place of performance, URL; AI analysis of the notice | retrieval from the Public Procurement Bulletin and Baza Konkurencyjności (list of notices and details of notices matching the Controller's criteria) and from a copy of the public notice file of platformazakupowa.pl in the Service Provider's database; filtering by sources, CPV codes, words, voivodeships and value indicated by the Controller; rating by the AI model; saving in the Panel; at a User's request, analysis of the notice by the AI model after replacing e-mail addresses, phone numbers and the designated contact person with a placeholder, saving the analysis with the same replacement; Telegram or Discord notification (optional) | the source engine on the Service Provider's server, AI model (Anthropic), the Account database |
| Lead source (Facebook — groups) | content of posts, author, group, address | retrieval from public groups indicated by the Controller by the Service Provider's retrieval module, without logging in to the service, through proxy servers (encrypted connection, Part C of Annex 3); rejecting posts of authors who have objected, before rating; rating by the AI model, including recognition of special categories of data (§ 4(2)); saving as above | the retrieval module on the Service Provider's server, the source engine, AI model (Anthropic), the Account database |
| Facebook Engagement | the Controller's account sessions, third-party posts and comments, drafts, approved content | encrypted storage of sessions, operation of the browser bot on the account session (reading groups and comments, publishing approved content), AI drafts, screenshots and page HTML in case of errors | the bot on the Service Provider's server (browser profile per account, error screenshots), AI model (Anthropic), the Account database, Facebook (Meta) as an External Service |
| AI Assistant | Account data available to the User, questions and answers | reading data with read-only tools, sending to the model, saving the question and answer | the Account database, AI model (Anthropic) |
| Data information and objections | the Controller's company details for the information (name, address, NIP tax number, e-mail for data matters, optionally the address of its own information page), hashes of the names of authors who have objected, the IP address of the person objecting (in server memory for the purpose of the submission limit and in the web server log) | publishing the /dane page at the Panel address, the information text copied from the lead card, accepting an objection from the form or from the lead card, saving a SHA-256 hash of the name with the Account identifier (without the name), passing the hashes to the source engine, submission limits, audit log entry without the name | the Account database, the source engine |
| Patterns from ratings | the User's rating and its reason, the source, title and content of the rated lead (without the author name field; the content may contain data that the author provided in it) | preparation by the AI model of one sentence about what matches or does not match the Controller, a check in the code rejecting e-mail addresses, links, strings of at least 9 digits and the author's name, saving the pattern and passing it to the source engine as a hint when rating subsequent listings | the Account database, AI model (Anthropic), the source engine |
| SEO Research | domains, keywords, page content, data from the Controller's Search Console, content drafts | measurements, audits (page crawl), content generation, AI visibility research, reports | the SEO engine on the Service Provider's server (data per tenant), billing gateway, DataForSEO, AI model (Anthropic), OpenAI and Perplexity (only visibility research in ChatGPT and Perplexity), Google (External Service) |
| Google Business Profile | business profile data, reviews (author's first name, content), posts, statistics, Google tokens | synchronisation through the Google API, AI drafts (without authors' surnames; e-mail addresses and phone numbers removed from the draft), publication after a User's click, position grid | the SEO engine (copy of data per tenant, encrypted token), AI model (Anthropic), DataForSEO, Google (External Service) |
| Support and maintenance | any Data to the extent necessary to handle a request | service access, copies before an update, export, deletion | the Service Provider's servers / the Controller's server; the Service Provider's e-mail mailbox |
Duration of processing: the term of the Main Agreement and the data retrieval period (§ 12), subject to the retention periods in § 12(5).
Annex 2 — Technical and organisational measures (Article 32 GDPR)
The description corresponds to the state of the SevenOS software and the Central Services as at the date indicated in the document version.
A. Isolation of Account (tenant) data
- All tables with Account data contain a tenant identifier and are covered by the PostgreSQL Row Level Security mechanism in enforced mode (ENABLE + FORCE ROW LEVEL SECURITY) with tenant isolation policies; on start-up, the API performs an RLS self-test and does not start if isolation does not work.
- Composite foreign keys (record identifier + tenant identifier) prevent, at database level, a record from being linked to a record of another Account (e.g. a lead rating, a user role).
- Separate database roles: the application role (data operations only, no schema changes), the migration role (used only at start-up), the internal role of the operator panel (cross-tenant access only for administrative routes protected by a secret), the backup role (read-only). The right to connect to the Service database has been revoked from the PUBLIC role and granted by name to the Service roles.
- The SEO engine filters every query by tenant; the identifier of another tenant's resource is treated as non-existent. Modules are gated in three layers (menu, Panel route, API), which is covered by automated tests.
B. Authentication and access control
- Passwords are stored only as bcrypt hashes (cost 12).
- The session is kept in a cookie with the
__Host-prefix, with the HttpOnly, Secure and SameSite=Strict attributes, valid for 12 hours; sessions are invalidated after a change of permissions or deactivation of the account. - Login attempts are limited (5 attempts in 15 minutes per IP address and e-mail address, three independent counters).
- Protection against CSRF (verification of the origin of state-changing requests).
- Role model: Owner, Roles with “view”/“edit” levels, additional permissions for cost-incurring actions and publication; enforced on the server side; the Main Account is protected against being disabled.
- Integration keys (the key for data transfer from the Central Services, the SEO gateway key) are stored on the verifying side only as SHA-256 hashes.
C. Encryption
- Transmission: HTTPS with TLS 1.2/1.3, Let's Encrypt certificates, HSTS header (2 years, includeSubDomains),
X-Robots-Tag: noindexheader for Panels. - Account secrets (Facebook session cookies, the SEO gateway key, the Discord channel address) are encrypted with AES-GCM with additional authenticated data (AAD) binding the ciphertext to the tenant and, for Facebook sessions, to the account; key versioning with a rotation procedure; the master key is stored separately from database backups.
- Facebook sessions: only cookies of the facebook.com domain and the necessary attributes are saved; the Panel never returns the content of a session (only information that it exists and the date it was saved); sessions are released to the bot without caching and with a release limit (120 per 10 minutes per tenant).
- The Controller's Google tokens (Search Console, Business Profile) are stored in the SEO engine in encrypted form (Fernet); advertising account tokens are encrypted with a separate key.
D. Network and infrastructure
- The Service API listens only on the local interface (127.0.0.1); the only entry point is the web server (nginx) on ports 80/443.
- Routes receiving data from the Central Services on the Controller's server are restricted in nginx to the IP addresses of the Service Provider's infrastructure and additionally require the Account key.
- Updates are deployed atomically, under a lock excluding parallel runs, with the possibility of restoring the previous version of the code.
- The Service Provider's servers: VPS at the provider indicated in Annex 3.
E. Backups and continuity
- A copy of the database is made before each update that changes the database structure, using a separate database role with read-only privileges; the update is aborted if the copy cannot be made.
F. Artificial intelligence
- The AI Assistant uses only read-only tools, limited to the Modules available to the User (the gate is checked twice); the prohibition of writing tools is enforced by an automated test.
- System prompts treat content from the data as data and not as instructions (limiting prompt injection); answers are rendered without HTML, with links only to Panel paths.
- Review reply drafts: the review author's surname is not passed to the model; e-mail addresses and phone numbers are removed from the generated draft.
- No AI content is published without approval by a human with the relevant permission.
- The Data is not used by the Processor to train models; the terms of model providers for their APIs apply (no default training on API data).
G. Accountability
- An audit log of security events and changes (including changes of permissions, roles, Facebook sessions — without session content — and publication decisions); entries are kept regardless of the deletion of a User.
- A register of costs and calls of external services per tenant and User.
H. Organisational measures
- Access to servers and databases only for persons authorised by the Processor and bound by confidentiality.
- The principle of minimising service access to Data: access to Account data to handle a request only to the extent necessary, with a record made.
- The SEVENEDGE service account in the Controller's Panel serves only to help with handling the Account. It is visible on the list of Users, does not count towards the limit of persons, and every login to it is recorded and visible to the Controller in the Panel.
I. Data minimisation and retention
- Listings and posts that the AI model has rated as not being leads are passed by the source engine to the Panel without content, title, URL and author data.
- A post from a public Facebook group that the AI model marks as containing special categories of data is saved without content, author and URL, only with technical data (in particular a hash of the content, which prevents it from being rated again).
- An author's objection is stored only as a SHA-256 hash of the name (after normalisation) with the Account identifier; posts and listings of authors on the objection list are rejected before being sent to the AI model and before being saved. The name given in the objection form is not saved in the database or in logs.
- The objection form has submission limits per IP address (counters in server memory) and per Account, and protection against bots.
- Match patterns prepared from Users' ratings are created without the author name field and pass a check in the code that rejects e-mail addresses, links, strings of at least 9 digits and the author's name (also in inflected forms).
- The retention periods in § 12(5) of the Agreement are applied automatically once a day, and the result of each run is recorded.
Annex 3 — Sub-processors and External Services
Part A — Sub-processors
| # | Sub-processor | Scope of activities | Location / transfer | Transfer basis |
|---|---|---|---|---|
| 1 | OVH Sp. z o.o. (Poland), OVHcloud group | hosting of VPS servers: the Provider-hosted Installation (Panel and Account database) and the Central Services (source engine, Facebook bot, SEO engine, gateway) | Poland | not applicable (EEA) |
| 2 | OpenAI Ireland Ltd (Ireland), with onward transfer to OpenAI, L.L.C. and affiliates | only brand and keyword visibility research in ChatGPT answers in the “SEO Research” Module (queries containing keywords and brand names); other Modules and other functions of the “SEO Research” Module do not transmit data to OpenAI | EU / USA | standard contractual clauses in the OpenAI DPA; DPF, where applicable |
| 4 | DataForSEO OÜ (Tallinn, Estonia; office in Kharkiv, Ukraine) | position and search result measurements, backlink data, Google Maps position grid (keywords, domains, business profile location) | Estonia; possible access from Ukraine; sub-processors in the USA | standard contractual clauses / DataForSEO DPA |
| 5 | Perplexity AI, Inc. (USA) | brand and keyword visibility research in AI search engine answers in the “SEO Research” Module (queries containing keywords and brand names) | USA | in accordance with § 8(1) |
| 6 | Hostinger (Hostinger group) | the Service Provider's mailbox used to handle the Controller's requests and demands (correspondence may contain Data); DNS zone of the sevenedge.pl domain (records of Panel addresses — no personal data) | EU | not applicable (EEA) |
| 8 | Anthropic Ireland, Limited (Ireland), with onward transfer to Anthropic, PBC (USA) and affiliates | rating the match of listings, analysis of procurement notices and requests for quotation in the “Tenders” Module at a User's request (without recognised contact details), patterns from Users' ratings, drafts and classification in the “Facebook Engagement” Module, the AI Assistant, briefs, content and strategy in the “SEO Research” Module, and drafts of review replies and posts in the “Google Business Profile” Module | EU / USA | standard contractual clauses in the Anthropic DPA; DPF, where applicable |
| 9 | Plus Five Five, Inc. (Resend, USA) | sending e-mail messages from the Panel (password setup links, notifications, the morning summary with lead titles, source, match rating, budget, deadline and a link to the Panel), containing the recipient's e-mail address and first name | USA | standard contractual clauses in the Resend DPA |
Update of 23 October 2026 (version 1.1): added Sub-processors no. 8 (Anthropic) and no. 9 (Resend), changed the scope of no. 3 (Apify) and the description of no. 7 (proxy servers), in the manner described in § 7(2).
Update of 24 October 2026 (version 1.2): the area “User activity log” added in Annex 1. The Controller, as the employer or principal of the Users, informs them of this processing.
Update of 26 October 2026 (version 1.3): the scope of Sub-processor no. 2 (OpenAI) narrowed to visibility research in the “SEO Research” Module, because listing rating, drafts, the AI Assistant and SEO and Business Profile content run on Anthropic models (Sub-processor no. 8); in Part B, the row about the Controller's own OpenAI key removed (the Service does not accept the Controller's keys, so it also disappears from the list of encrypted secrets in Annex 2) and a row added about speech recognition in the User's browser.
Update of 30 October 2026 (version 1.4): the full scope of Sub-processor no. 2 (OpenAI) restored, because the SEO engine uses only OpenAI models (content and visibility research in the “SEO Research” Module, drafts in the “Google Business Profile” Module), and listing rating, drafts in the “Facebook Engagement” Module and the AI Assistant run on Anthropic or OpenAI models depending on the configuration of the Service; the scope of Sub-processor no. 8 (Anthropic) narrowed to these three uses; in Part A, speech transcription by OpenAI removed (speech is recognised by the User's browser, Part B); in Part B, Discord added as an optional notification channel; in Annex 2, the Discord channel address added to the encrypted secrets; in the manner described in § 7(2) and § 5(1)(4).
Update of 30 October 2026 (version 1.5): all functions generating and rating content (listing rating, drafts in the “Facebook Engagement” Module, the AI Assistant, content in the “SEO Research” Module and drafts in the “Google Business Profile” Module) run on Anthropic models (Sub-processor no. 8); the scope of Sub-processor no. 2 (OpenAI) narrowed to visibility research in ChatGPT in the “SEO Research” Module; in the manner described in § 7(2).
Update of 1 November 2026 (version 1.6): Sub-processor no. 3 (Apify) removed, because the Service no longer uses this service; proxy servers (previously no. 7) described in Part C and in § 7(9), because with an encrypted connection they have no access to the Data; numbers 3 and 7 are no longer used; the scope of no. 8 (Anthropic) supplemented with patterns from ratings, and of no. 9 (Resend) with the morning summary. The body of the Agreement now describes the retention periods (§ 12(5)), the tools for information and objections (§ 9(1)(3)), the data of persons submitting an objection (§ 4(1)), the handling of special categories of data (§ 4(2)) and new purposes (§ 3(1)(8)); new areas “Data information and objections” and “Patterns from ratings” in Annex 1; new Part I in Annex 2. Changes to the body of the Agreement and Annex 1 bind a Controller who concluded the Agreement before this date from their acceptance in documentary form (a reply by e-mail to the notification is sufficient).
Update of 21 November 2026 (version 1.7): the scope of no. 8 (Anthropic) supplemented with the analysis of notices in the “Tenders” Module; in Part B, sources of procurement notices added (the Public Procurement Bulletin, Baza Konkurencyjności, platformazakupowa.pl), in the manner described in § 7(2). The body of the Agreement now describes the retrieval and analysis of procurement notices (§ 3(1)(2)), the data of persons designated for contact in notices (§ 4(1)), making Data available to a Controller established outside the EEA on the basis of standard contractual clauses (§ 8(5)) and the language of the Agreement (§ 14(5)); new area “Lead source (Tenders)” in Annex 1. Changes to the body of the Agreement and Annex 1 bind a Controller who concluded the Agreement before this date from their acceptance in documentary form (including in the Panel), and at the latest after 30 days from the notification, in accordance with the Terms (§ 23(2) and § 26(10)).
Part B — External Services (not Sub-processors; integration on the Controller's instruction)
| Service | Role and scope | Notes |
|---|---|---|
| Meta Platforms Ireland Limited (Facebook) | the service in which the Controller's accounts operate; the bot reads groups and publishes approved content on the Controller's account session | processes data on its own terms; compliance with Meta's terms is the Controller's responsibility (Terms § 12) |
| Google Ireland Limited / Google LLC (Search Console, Google Business Profile) | access to the Controller's data through the API on the basis of OAuth authorisation granted by the Controller | processes data on the terms of the Controller's agreement with Google |
| Useme, Oferia | listings services from which jobs indicated by the Controller are retrieved | data sources; obligations under Article 14 GDPR are on the Controller's side |
| Public Procurement Bulletin (Biuletyn Zamówień Publicznych, President of the Polish Public Procurement Office), Baza Konkurencyjności (the Polish minister responsible for regional development), platformazakupowa.pl (Open Nexus Sp. z o.o., public notice file) | public services of procurement notices and requests for quotation from which notices matching the Controller's criteria are retrieved (the Controller chooses the sources in the settings of the “Tenders” Module) | data sources, no Data is transmitted to these services; obligations under Article 14 GDPR towards persons designated for contact are on the Controller's side; a bid on platformazakupowa.pl is submitted in that service |
| Telegram (Telegram Messenger Inc. / Telegram FZ-LLC) | delivering lead notifications to the chat indicated by the Controller (optional function) | entity outside the EEA, without a data processing agreement; transmission only on the Controller's express instruction (entering the chat identifier) |
| Discord (Discord Inc., USA) | delivering lead notifications to the channel indicated by the Controller (optional function) | entity outside the EEA, without a data processing agreement; transmission only on the Controller's express instruction (connecting the channel in the Panel) |
| Provider of the User's browser (e.g. Google in the Chrome browser) | speech recognition when a User dictates a message to the AI Assistant using a microphone | processes the recording on the terms of the browser provider; the Service does not send recordings to the Service Provider's servers; the User may type instead of dictating |
Part C. Connection intermediaries that are not Sub-processors
| Intermediary | Role | Notes |
|---|---|---|
| Operators of proxy servers used by the Service Provider's retrieval module | relaying the connection of the retrieval module with the Facebook service when retrieving posts from public groups | the connection is encrypted (HTTPS) from the retrieval module to the service, so the operator has no access to the retrieved content or Data and is not a Sub-processor; operators may also operate outside the EEA |


