Terms of Service
These terms are the contract between THRIVE NEXUS S.R.L. and the organisation that uses Content Engine, the app at https://content.thrivenexus-team.com that teams use to review, organise and publish content material kept in their Google Drive™. The service is intended for professionals only. Together with the Privacy Policy, the Cookie Policy and Annex A (processing data on the customer’s behalf), they form the entire contract. The Romanian version is the one with legal effect; this English translation is provided for information.
1. Who we are (identification)
The Content Engine service is provided by:
- Name: THRIVE NEXUS S.R.L.
- Legal form: societate cu răspundere limitată (S.R.L.)
- Registered office: Sat Lăpuș, nr. 53-A, județul Maramureș, cod poștal 437175, România
- Trade Register number: J2023001443249
- Unique registration code (CUI): 48861692
- European unique identifier (EUID): ROONRC.J2023001443249
- Email: contact@thrivenexus.ro
- Service address: https://content.thrivenexus-team.com
You can write to us at any time at contact@thrivenexus.ro. The same address is also the single point of contact required by Regulation (EU) 2022/2065 on digital services (section 8).
2. Definitions and acceptance
In these terms:
- The service — the Content Engine app, available at https://content.thrivenexus-team.com, with all its features, including those that run automatically in the background (section 6).
- We — THRIVE NEXUS S.R.L., the provider of the service.
- The customer (“you”) — the professional for whom a team is created: a legal person, an authorised self-employed person or a liberal professional. When a person creates an account on behalf of an organisation, “you” also means that organisation.
- User — anyone with an account in the service: the owner, the admins and the members of a team.
- Team — a customer’s workspace, with its connected resources (Google Drive, integrations) and its members. In agency mode, a team may have several clients or brands, each with its own resources.
- Owner, Admin, Member — the roles within a team, described in section 5.
- Content — the material you process through the service: the files and folders in Google Drive, texts, images, videos, articles, posts and schedules, with their metadata, and anything you enter in the app.
- Integrations — the third-party services you connect: Google Drive, Zernio (publishing to social networks), WordPress and Webflow (blog) and the notification webhook.
- Google data — information received through Google APIs (Google Drive) after you authorise access.
Acceptance. You accept these terms when you create your account, by ticking the two mandatory boxes in the registration form, which are not ticked in advance. The first confirms that you use the service for professional purposes, that you are at least 18 years old, that you accept the terms and that you have read the Privacy Policy. The second confirms that you expressly accept the clauses in sections 9 (Limitation of liability), 10 (Suspension and termination) and 13 (Governing law and jurisdiction), under art. 1203 of the Romanian Civil Code. Without both ticks the account cannot be created. The accepted version (identified by its date) and the time of acceptance are stored in your account.
Order of documents. If you have signed a separate written contract with us, it prevails where it provides otherwise. For personal data processed on your behalf, Annex A prevails over the rest of the terms.
3. Who may use the service (B2B, 18+)
The service is intended exclusively for professionals — legal persons, authorised self-employed persons, sole traders or family businesses and liberal professions — who use it for the purposes of their professional activity. It is not intended for consumers.
- You must be at least 18 years old and have full legal capacity.
- If you create an account on behalf of an organisation, you confirm that you are entitled to represent it and to accept these terms for it. Invited members accept the terms themselves when they create their accounts.
- Because the service is not aimed at consumers, consumer protection rules do not apply (for example Government Emergency Ordinance no. 34/2014 on consumer rights, Law no. 193/2000 on unfair terms and Government Ordinance no. 38/2015 on alternative dispute resolution).
- Between professionals, art. 8(3) of Law no. 365/2002 on electronic commerce allows the parties to agree otherwise than provided in paragraphs (1) and (2). We expressly agree to derogate from art. 8(1)–(2), except for the information we provide anyway in section 4, which remains valid. Making the terms available in a form you can store and reproduce (art. 8(4)) is not covered by the derogation.
If you do not meet these conditions, do not use the service. If we find that an account is used by a consumer or by a person under 18, we may close it after notifying you.
4. How the contract is concluded (Law 365/2002, art. 8)
Technical steps.
- You open the registration form (https://content.thrivenexus-team.com/login?mode=register) and fill in your display name, email address and a password. If you received an invitation link, the form links you to that team.
- You read these terms and the Privacy Policy (the links are in the form itself) and tick the two mandatory boxes described in section 2.
- You press “Creează contul” (Create account). The contract is concluded when the account is created, and the app takes you straight into your account.
- Access to the features starts once the team is approved: we review and activate a new team, and a new member joins once the team’s owner or an admin has invited them or approved their request. Until then you see a waiting screen. If the team is not approved, you can ask us to delete the account at contact@thrivenexus.ro.
Correcting errors. Before you press “Creează contul” you can check and correct every field; the form flags missing or invalid fields, and the account is not created until you fix them. After creation, you change your name and photo in Setări → Cont (Settings → Account), reset your password from the sign-in page, and write to us for any other correction.
Language. The contract is concluded in Romanian. The English translation is for information; if the versions differ, the Romanian one prevails.
Storage of and access to the contract. We store in your account the version of the terms you accepted (its date is shown at the top of this page) and the time of acceptance. The version in force is permanently published, without sign-in, at https://content.thrivenexus-team.com/terms, together with the Privacy Policy and the Cookie Policy. You can save or print it at any time from your browser (for example Ctrl/Cmd + P → “Save as PDF”). We send you earlier versions free of charge on request.
Codes of conduct. We have not subscribed to any code of conduct.
Price. The service is currently not paid for through the app. If you have agreed separate commercial terms with us in writing (for example for agency mode), they apply together with these terms. If the service or part of it becomes paid, the prices, including VAT treatment, are communicated to you in advance and apply only with your agreement.
5. Your account and team
- Account data. You use real, up-to-date data. An account belongs to a single person and is not shared with others.
- Password. You keep your password confidential and tell us immediately at contact@thrivenexus.ro if you suspect someone else has used your account. You are responsible for what is done from your account until you tell us, unless the unauthorised access is our fault.
- Roles. The owner creates the team and is responsible for it. The owner and the admins connect Google Drive and the integrations, choose the working folders and invite, approve or remove members. Members work with the team’s resources — they review, edit, approve and schedule material — within the limits of their role.
- Invitations. A member joins a team either by accepting an email invitation from the owner or an admin, or by asking to join through the team link, a request the owner or an admin approves.
- Responsibility for the team. The customer is responsible for the members it approves: what they do in the service is deemed done on the customer’s behalf. The owner makes sure members are entitled to work with the team’s content and removes those who should no longer have access.
- Shared Drive access. Approved members work with the owner’s Google Drive access, and the address of the connected Google account is visible to them (section 6).
- Deleting your account. You can delete your account yourself at any time from Setări → Legal și date → „Șterge contul” (Settings → Legal and data → Delete account), confirming with your password and typing STERGE. Deletion is immediate and automatic. If you own a team that still has other members, you first remove them in Setări → Echipă (Settings → Team) or write to us to transfer the team. The files in Drive and the posts already sent to Zernio, the networks, WordPress or Webflow stay with you and are managed there. What is deleted and when is explained in the Privacy Policy.
6. What the service does (including in the background)
Content Engine is a review centre and a “second brain” built on top of your Google Drive folders, with publishing to social networks and to your blog. The service lets you:
- browse the material in the chosen folders, edit it, approve or reject it and move it between working folders;
- organise approved material in a library (Brain) in Drive;
- schedule and publish posts to social networks through Zernio, and articles to WordPress or Webflow;
- receive a webhook notification when a post is published, if you set one up;
- optionally, Game Mode: a leaderboard of published posts, only if you turn it on.
Google Drive access. The owner or an admin connects Google Drive through Google’s consent screen. To let you choose folders we show you the names of the folders in your Drive; we read file content only from the chosen folders (including the files and folders, with all their contents, that shortcuts placed there point to). In Drive, the app creates the “Content Engine” folder with its working subfolders (De revizuit, Aprobate, Programate, Postate, Respinse — To review, Approved, Scheduled, Posted, Rejected) and the category folders, writes the content.md and _review-meta.json files (status, schedule), uploads images, renames, moves and copies material into Brain, and permanently deletes, bypassing the trash, the older copy with the same name in Brain when you send an item to Brain again or remove it from Brain. Details are in the Privacy Policy.
Automatic operations in the background. While Drive is connected, the service does the following on its own, without you pressing a button:
- re-reads the chosen folders every few minutes (at most 10), so the review list stays up to date — for teams that used the app in the last 7 days, including when nobody is signed in;
- moves material to Programate (Scheduled) or Postate (Posted) based on the scheduling status in Zernio;
- re-uploads to Zernio, about every 5 days, the images and videos of scheduled posts (Zernio keeps temporary files for only 7 days); the files are downloaded from Drive into memory only, never written to disk;
- publishes scheduled Webflow articles while the app is open (on resync or when the calendar is opened);
- sends the webhook notification, if you set one up.
These operations follow from the configuration you choose and stop when you disconnect Drive or the relevant integration, or when you delete your account.
Members use the owner’s access. The Google Drive connection belongs to the team: approved members work with the owner’s Drive access, that is, the Google account connected for the team. Copies of the access tokens are kept, encrypted, in their server-side sessions. By connecting, the owner agrees that approved members work with the material in the chosen folders and that the address of the connected Google account is visible to them.
Third-party services. The service depends on Google Drive, Zernio, WordPress and Webflow, and on the social networks Zernio publishes to. You use them with your own accounts and keys, and their terms and policies apply separately. We do not control their availability, API changes or decisions (for example a network rejecting a post). You can withdraw the app’s access to Google Drive at any time from Setări → Conexiuni (Settings → Connections) or from your Google account permissions.
Availability. We make reasonable efforts to keep the service available and secure, but we do not offer a guaranteed service level (SLA). We may carry out maintenance and improve or change features; if a change removes an essential feature you use, we notify you under section 12.
7. Your content, the licence and Google data
Your content stays yours. We acquire no ownership rights over your content. The material stays in your Google Drive, under your control.
The licence you give us. You grant us a non-exclusive, royalty-free, non-transferable licence (except to the sub-processors in Annex A), for the term of the contract and only to the extent needed for the operations you request or configure, including the automatic ones in section 6: to read content from the chosen folders, to keep a temporary working copy in server memory only, for at most 7 days (as the owner of the content, you expressly permit this retention), to display it to you and your team members, to modify, move or copy it in Drive on your instruction and to transmit it to the integrations you configured. The licence ends with the contract.
What we never do with content and Google data:
- We do not use them for advertising, including personalised or retargeted advertising.
- We do not sell them or give them to data brokers or other third parties, other than the integrations you configure and the sub-processors in Annex A.
- Content Engine does not use data obtained through Google Workspace APIs (including Google Drive) to develop, improve, or train generalized or non-personalized AI and/or ML models, or any other AI/ML model. The app has no AI features.
- People on our team do not read content, except where you have given explicit consent for specific material (for example in a support request), where it is necessary for security (for example investigating abuse), where the law requires it, or where the data has been aggregated and anonymised for internal operations.
- We transfer Google data only for the features you see and use in the app, with your consent, for security, to comply with the law or — only with your explicit prior consent — as part of a merger, acquisition or sale of assets.
Our statement on Google data, in the form Google requires:
Content Engine's use of information received from Google APIs will adhere to the Google API Services User Data Policy, including the Limited Use requirements.
The use of information received from Google Workspace scopes will adhere to the Google User Data Policy, including the Limited Use requirements.
The policy referred to is the Google API Services User Data Policy. How we use Google data is explained in the Privacy Policy.
Your responsibility. You warrant that you hold the rights needed for the content you process and publish through the service — copyright, image rights, the consent of the people who appear in the material — and that publishing complies with the law and with the platforms’ rules. You also warrant that you are entitled to connect the Drive folders, especially when they belong to an organisation or to one of your clients. For personal data in the content, you are the controller and we process it on your behalf under Annex A.
Our rights. The app, code, design and the Content Engine brand remain ours. For the term of the contract you have a non-exclusive, non-transferable right to use the service in line with these terms.
Trademarks. Google Drive is a trademark of Google LLC. Zernio, WordPress and Webflow are trademarks of their respective owners. Content Engine is not affiliated with or endorsed by these companies.
8. Acceptable use, illegal content and point of contact (DSA)
What is not allowed. You do not use the service, and do not let team members use it, for:
- illegal content — for example content that infringes copyright or other rights, is defamatory, incites hatred or violence, exploits minors, or constitutes fraud or deception;
- spam or mass automated publishing that breaks the social networks’ rules;
- accessing other teams’ data or circumventing authentication, roles or technical limits;
- malware, vulnerability testing or overloading the infrastructure without our written consent;
- automated data extraction (scraping), or copying or decompiling the app, except where the law permits;
- breaching the policies of Google, Zernio, WordPress, Webflow or the networks you publish to.
How to report illegal content (DSA art. 16). Anyone can report content they consider illegal that is stored or transmitted through the service by writing to contact@thrivenexus.ro with the subject “Illegal content notice”. The notice must include:
- an explanation of why you consider the content illegal;
- its exact location: the address (URL) of the post or article, or other information that helps us identify the content (team, material, date);
- your name and email address (not required if you are reporting offences concerning child sexual abuse);
- a statement that you believe in good faith that the information in the notice is accurate and complete.
We acknowledge receipt, assess the notice diligently, objectively and without undue delay, through people on our team (not through automated systems), and then inform you of our decision and of the ways to challenge it. Content published on social networks, WordPress or Webflow sits with those providers, so you can also report it to them directly. If we become aware of information indicating a criminal offence that threatens someone’s life or safety, we inform the competent authorities (DSA art. 18).
Single point of contact (DSA arts. 11 and 12). Member State authorities, the European Commission, the European Board for Digital Services and users of the service can contact us directly, by electronic means, at contact@thrivenexus.ro. Languages we communicate in: Romanian and English. Messages are read and answered by people, not only by automated tools.
How we moderate (DSA art. 14). We do not generally monitor content and we do not use automated moderation tools. We manually review notices, requests from authorities and signs of technical abuse. If a breach is confirmed, we take a proportionate measure, case by case: a warning; disabling access to the content in the service; restricting certain features (for example publishing or integrations); suspending access for a user or for the team; in serious cases, terminating the contract (section 10). We email you a statement of reasons (DSA art. 17) — what we restricted, the facts and the grounds, and whether the decision followed a notice — no later than when we apply it, unless the law or an authority prohibits this. You can challenge any decision by replying to that email or writing to contact@thrivenexus.ro; a person on our team reviews the case again and replies within one month. You can always go to court.
9. Limitation of liability
Clause expressly accepted at registration (art. 1203 of the Romanian Civil Code)
We provide the service with professional diligence. To the extent permitted by law:
- Cap. Our total liability for all claims related to the service within any 12-month period is limited to the greater of: the total you paid for the service in the 12 months before the event that caused the damage, or 1,000 lei.
- Indirect damage. We are not liable for loss of profit, loss of clients, opportunities or reputation, or other indirect damage.
- Third parties. We are not liable for the operation, outages, API changes or decisions of Google, Zernio, WordPress, Webflow or the social networks, nor for content once it has reached them.
- Your actions. We are not liable for content that you or your team members publish, for changes and deletions you make or request in Drive or in the integrations, including through automatic operations you configured, nor for unauthorised access that occurs because a password or access keys were not protected.
- Force majeure. We are not liable for non-performance caused by force majeure or a fortuitous event.
What we do not limit. Nothing in this section excludes or limits our liability for damage caused intentionally (wilful misconduct) or through gross negligence (art. 1355(1) of the Romanian Civil Code), for harm to a person’s life, bodily integrity or health (art. 1355(3)), or in any other case where the law does not allow a limitation. The limitation does not affect data subjects’ rights under Art. 82 GDPR.
Your files stay in Google Drive, which also keeps version history; we still recommend keeping your own backups of important material.
10. Suspension and termination
Clause expressly accepted at registration (art. 1203 of the Romanian Civil Code)
Termination by you. You may terminate the contract at any time, without notice and at no cost, by deleting your account (section 5) or by writing to us at contact@thrivenexus.ro. For a team with several members, the owner first removes the others or asks us to transfer the team.
Termination by us. We may terminate the contract, including by discontinuing the service, with 30 days’ notice sent by email.
Immediate suspension or termination. We may suspend access — the whole account, the team or only certain features — or terminate the contract without notice only for serious reasons: a serious or repeated breach of section 8; a risk to the security of the service, of data or of other users (for example a compromised account); a legal obligation or an order from an authority. If Google or another essential provider withdraws the access a feature depends on, we may suspend only the affected feature. We choose the mildest measure that solves the problem, tell you the reason (section 8), restore access as soon as the cause is gone, and you can challenge the decision at contact@thrivenexus.ro.
What happens to data on termination.
- access to the service and the automatic operations (sync, moving material, re-uploading media to Zernio) stop, and the team’s Google access is revoked;
- the files in Google Drive and the posts or articles already sent to Zernio, the networks, WordPress or Webflow stay with you, untouched;
- unless termination results from you deleting your account, you can request an export of the account data within 30 days of termination (section 11); after that period we delete it permanently;
- if you delete your account yourself, deletion is immediate, so request the export beforehand;
- copies in server memory disappear within at most 7 days or on restart, the password reset log keeps entries for up to 30 days, and any backups held by the infrastructure provider are overwritten in their normal cycle; we keep only what the law requires us to keep (for example accounting records).
11. Portability and switching providers (Data Act)
Regulation (EU) 2023/2854 on data (the Data Act) gives you the right to switch easily to another provider or to your own systems. With us, switching is simple because of how the service is built:
- Your content stays in your Drive. Material, statuses and schedules are kept in files in your Google Drive, in open formats: Markdown (
content.md), JSON (_review-meta.json) and the original media files. You can use them right away in another tool, without asking us for anything. - Published posts stay in your Zernio, WordPress and Webflow accounts.
- Export of account data. On request sent to contact@thrivenexus.ro, we give you the account and team data in a structured, commonly used and machine-readable format (JSON), without undue delay and no later than 30 days after the request. You can request the export at any time during the contract and within 30 days after termination.
- What the export contains (full list): the profile (email, name, photo, role, account creation date, version and date of acceptance of the terms); the team (name, owner, status, members and invitations with their roles, the clients or brands in agency mode); the configuration (chosen Drive folders, connected integrations, webhook address); usage statistics; the Game Mode entry, if any; the number of published articles.
- What it does not contain: passwords (managed by Firebase Authentication, which does not show them to us), Google tokens and integration keys (secrets you already hold with those providers and can revoke there), sessions and internal technical security and anomaly logs.
- No notice and no fees. You can start switching at any time, without notice. We charge no switching or export fees, including data transfer costs.
- During the transition the service remains functional for as long as the contract is in force, and we give you the information needed to move to the new provider. Once switching is complete, or 30 days after termination, we fully delete the exportable data and the account data (section 10).
Where the infrastructure runs (Data Act art. 28).
- application server: Hostinger International Ltd., data centre in Germany (European Union);
- database and authentication: Google Firebase (Cloud Firestore and Firebase Authentication), region europe-west3 (Frankfurt, Germany);
- the full list of sub-processors is in Annex A.
Protection against unlawful governmental access. Tokens and integration keys are encrypted at application level before storage, Drive content is never written to disk, and our staff’s access is limited to what is strictly necessary. We comply with a request from an authority of a country outside the European Union to access or transfer your data only under the conditions of art. 32 of the Data Act and Art. 48 GDPR (for example on the basis of an international agreement) and, where the law allows, we inform you beforehand.
12. Changes to these terms
We may change these terms, for example when we add features or when the law changes. For any change that affects your rights or obligations:
- we notify you at least 30 days before it takes effect, by email or through a visible notice in the app, with a summary of the changes;
- until that date you can terminate the contract at no cost and request a data export (section 11);
- if you keep using the service after that date, the new version applies; a new form of the clauses in sections 9, 10 and 13 applies only once you expressly accept it;
- changes to Annex A and changes of sub-processors are notified to you by email, as set out in Annex A.
Exception: changes required by law, by an authority or by an urgent security risk may take effect sooner; even then we notify you as soon as possible and you have the same termination rights. Purely editorial corrections, with no effect on your rights, are published directly.
The date of the last update and the version are shown at the top. We send you earlier versions free of charge on request.
13. Governing law and jurisdiction
Clause expressly accepted at registration (art. 1203 of the Romanian Civil Code)
These terms and any contract concluded under them are governed by Romanian law.
We first try to settle any disagreement amicably: write to us at contact@thrivenexus.ro and we reply within one month. If we do not reach a solution within 30 days of the notice, the dispute is settled by the competent courts at the registered office of THRIVE NEXUS S.R.L. (Sat Lăpuș, nr. 53-A, județul Maramureș, cod poștal 437175, România). For customers in other Member States of the European Union, the choice of court is made under Art. 25 of Regulation (EU) No 1215/2012.
The attempt at amicable settlement does not prevent either party from asking a court for urgent measures. The mandatory rules of the applicable law remain unaffected.
14. Confidentiality and security
Confidentiality. Each party keeps confidential the non-public information received from the other in connection with the service (for example technical or commercial information) and uses it only to perform the contract, for its term and for 2 years after termination. Your content and personal data remain confidential without time limit. Public information, and information the law or an authority requires us to disclose, is not confidential; in that case we inform the other party where the law allows.
Security measures (detailed in the Privacy Policy):
- HTTPS-only connections, security headers and a strict content security policy (CSP);
- the session cookie holds only a random, signed identifier (HttpOnly, Secure), and the session data stays on the server, encrypted with AES-256-GCM;
- Google tokens and integration keys are encrypted at application level before they are written;
- Drive content is never written to disk or to the database: it stays only in server memory, for at most 7 days;
- sign-in attempt limits, server-side role checks and access rules in the database;
- our staff access data only when necessary, under a confidentiality obligation.
Your obligations. You use a strong, unique password, do not share it, remove from the team people who should no longer have access, and protect your integration keys (Zernio, WordPress, Webflow).
Security incidents. If we become aware of an incident affecting your team’s data, we notify you without undue delay — our target is 48 hours from when we become aware — with the information available on the nature of the incident, the data affected, the likely consequences and the measures taken, and we follow up as we learn more (details in Annex A).
15. Contact
- Email: contact@thrivenexus.ro — also the DSA single point of contact, in Romanian and English
- Registered office: Sat Lăpuș, nr. 53-A, județul Maramureș, cod poștal 437175, România
We reply within one month. For requests about personal data (access, rectification, erasure, portability and the others) see your rights in the Privacy Policy.
Annex A — Processing data on the customer’s behalf (Art. 28 GDPR)
This annex is the data processing agreement required by Art. 28(3) of Regulation (EU) 2016/679 (GDPR) between the customer, as controller, and THRIVE NEXUS S.R.L., as processor. It forms part of the terms, is accepted together with them and prevails over the rest of the terms for personal data processed on the customer’s behalf. For account data, security, logs and support we are the controller, and that processing is described in the Privacy Policy.
A.1 Subject matter and duration
Subject matter: processing the personal data contained in the team’s content in order to provide the service. Duration: the term of the contract, plus the period until deletion after termination (sections 10 and 11).
A.2 Nature and purpose of processing
Reading from the chosen folders, temporary storage in memory, consultation, display, organisation, modification, copying and moving in Drive, transmission to the integrations chosen by the customer, and deletion — manually or through the automatic operations configured by the customer (section 6). The sole purpose is providing the service to the customer.
A.3 Types of data and categories of data subjects
- Types of data: names, images and voices of people who appear in the material; contact details and other information in texts; file names and their metadata; the name and email of the user who schedules a post (sent to Zernio); social network page data (id, username, display name) in webhook notifications; names and emails of team members.
- Data subjects: the customer’s team members; people who appear or are mentioned in the material (employees, collaborators, the customer’s clients and other people); the customer’s contact persons.
- Special categories of data (Art. 9 GDPR): the service is not designed for them. If you include them in content, you are responsible for having a legal basis.
A.4 Our obligations (Art. 28(3) GDPR)
- (a) Documented instructions. We process the data only on your documented instructions — these terms, the configuration in the app and the actions you take in it — including with regard to transfers outside the EEA, unless the law requires otherwise (in which case we inform you beforehand, where the law allows). We tell you immediately if we believe an instruction infringes the GDPR or other data protection rules.
- (b) Confidentiality. People authorised to process the data have committed to confidentiality or are under a statutory obligation of confidentiality.
- (c) Security. We apply the measures required by Art. 32 GDPR (section 14).
- (d) Sub-processors. We engage them only under the conditions in A.5 and impose the same data protection obligations on them by contract; we remain liable to you for them.
- (e) Data subject requests. We help you, through appropriate technical and organisational measures, to respond to requests to exercise rights. A request we receive directly is forwarded to you without undue delay.
- (f) Arts. 32–36 GDPR. We help you meet your obligations on security, breach notification, impact assessments and prior consultation, taking into account the nature of processing and the information available to us.
- (g) At the end. When the contract ends, at your choice, we return the data to you (through the export in section 11) and then delete it, except for data the law requires us to keep. Content in Drive stays with you in any case.
- (h) Information and audits. We make available the information needed to demonstrate compliance with Art. 28 GDPR and allow audits, including inspections, by you or an auditor you mandate: with reasonable notice (normally 30 days), at most once a year (except after an incident or at an authority’s request), without access to other customers’ data and with the auditor bound by confidentiality. You bear the costs of the audit unless it reveals a material breach of our obligations.
A.5 Sub-processors
You give us general authorisation to engage the sub-processors below. Before adding or replacing a sub-processor, we inform you by email at least 30 days in advance. You may object, with reasons, within that period; if we cannot find a solution together, you may terminate the contract at no cost before the change applies.
| Sub-processor | Entity | What it does and where |
|---|---|---|
| Google Firebase (Firebase Authentication, Cloud Firestore) | Google Ireland Limited (Ireland) / Google LLC (USA) | Account authentication and the app database: accounts, teams, invitations, settings (with tokens and keys encrypted), usage statistics. Cloud Firestore runs in the europe-west3 (Frankfurt, Germany) region; Google’s technical access from the USA follows A.7. |
| Application hosting | Hostinger International Ltd. | The server that runs the app: working memory (the temporary copy of content) and the encrypted sessions. Data centre: Germany (European Union). |
| Email (SMTP) | Google Workspace (Google Ireland Limited) | Sends password reset emails (email address and reset link). Without a configured SMTP server, the email goes out through Firebase Authentication (Google). |
The integrations you choose are not our sub-processors. Zernio, WordPress, Webflow, the webhook address and your own Google Drive account are your providers: you choose them, you use them with your own accounts and keys, and data reaches them on your instruction. Your relationship with them, including a data processing agreement where applicable, is directly with them. For your information: Zernio receives the text of posts, images and videos, the name and email of the person scheduling and Drive identifiers (file names become part of the media addresses); WordPress and Webflow receive the article HTML and images; the webhook receives the full text of the published post and the page data.
A.6 Personal data breaches
We notify you without undue delay after becoming aware of a breach of personal data processed on your behalf — our target is 48 hours — with the information required by Art. 33(3) GDPR, to the extent we have it: the nature of the breach, the categories and approximate number of data subjects and records concerned, the likely consequences, the measures taken or proposed and the contact person. Information not available at first is provided in phases. We help you notify the supervisory authority and, where required, the data subjects.
A.7 Transfers outside the EEA
Some sub-processors (Google LLC) may access data from the United States. These transfers rely on the adequacy decision for the EU-US Data Privacy Framework, supplemented by the European Commission’s standard contractual clauses (Decision (EU) 2021/914). We make no other transfers outside the EEA without the appropriate safeguards required by Chapter V GDPR.
A.8 Liability
Liability under this annex follows section 9, without affecting data subjects’ rights (Art. 82 GDPR) and without limiting what the law does not allow to be limited.