Privacy Policy
This policy explains what personal data the Content Engine app (https://content.thrivenexus-team.com) processes, where we get it from, why, who receives it, how long we keep it and what rights you have. Content Engine is a workspace on top of Google Drive™: your material stays in Drive, and we do not copy it to disk or to the database.
In short
- We read file content only from the Drive folders you choose. To let you choose them, we show you the names of the folders in your Drive.
- Drive content is kept only in server memory, for at most 7 days. We do not write it to disk or to the database.
- While Drive is connected, the app also works in the background: it re-syncs the folders, moves items according to their scheduling status and keeps the media of scheduled posts fresh (see background actions).
- We send material only to the publishing services you connect. We do not sell data, we do not advertise and we do not train AI models.
- You can disconnect Drive and delete your account yourself, from Settings (see the steps).
1. Who we are and how to reach us
The controller of your personal data is the company that develops and provides Content Engine:
- Company 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
- Tax identification number (CUI)
- 48861692
- European Unique Identifier (EUID)
- ROONRC.J2023001443249
For any question about your data or to exercise your rights, write to us at contact@thrivenexus.ro. We have not appointed a data protection officer (DPO); requests about personal data reach us at the same address.
1.1. When we are the controller and when we act for the customer
- We are the controller for your account data, sessions, security and logs, usage statistics, Game Mode and support correspondence. For these we decide why and how the data is processed.
- We are a processor (Art. 28 GDPR) for your team’s content: the material in Drive, the people mentioned or pictured in it and the posts you publish. For this data, the controller is the organisation that uses Content Engine (the company or professional who created the team). We process it only to provide the service, on its instructions. The terms are in Annex A of the Terms and Conditions.
If your data appears in the material of a team that uses Content Engine (for example, you are mentioned in a post), contact that organisation. If you write to us, we pass your request on to it without delay.
2. What data we process
This section covers the data we do not receive from Google. Data from your Google account and from Google Drive has its own section: Google user data.
2.1. Account and team
- When you create an account: your email address, password and display name. The sign-in account is held by Firebase Authentication (a Google service): the email address, the password in protected form and technical account data such as the creation date. The name and the rest of the profile are stored in the database. The app does not store your password.
- Optional: your profile photo, stored as an image in your profile in the database. If you own a team, your name and photo also appear in the team data, visible to its members.
- Acceptance of the terms: the version of the Terms and Conditions you accepted and when you accepted it.
- Team: your role on the platform and in the team, the team you belong to, the team name and its approval status.
- Invitations: the email address of the invited person (who may not have an account yet), the proposed role, the status, who sent the invitation and, once accepted, the member’s name.
- Publishing activity: how many articles you published through the app, per day.
2.2. Session
When you sign in, your browser receives the ce_session cookie. It holds only a random, signed identifier. The session data (who you are, the active team, your connections, including the Google tokens) stays on the server, encrypted. The identifier changes every time you sign in. Details in the Cookie Policy.
2.3. Publishing integrations
If you connect them, we keep the Zernio API key, the WordPress site address, the WordPress username and application password, the Webflow token with the selected site and collection, and the notification webhook address. We use them only to send material to your services and to follow the status of scheduled posts. Keys, passwords, tokens and the webhook address are encrypted before they are written to disk or to the database. Data that is not secret (the WordPress site address and username, the Webflow identifiers) is stored unencrypted.
2.4. What we send when you publish
- To Zernio: the text of the posts, the images, clips and PDF documents (LinkedIn document posts), the name and email of the person who scheduled the post, the item’s Drive identifiers (so the app can find it again) and the notification webhook address, if one is configured. File names become part of the media file addresses at Zernio. When you tag a person or a company on LinkedIn, the profile or page link goes through Zernio so we can get the tag’s LinkedIn identifier.
- To your WordPress or Webflow site: the article (title, HTML text and the article’s other fields) and its images.
- To your notification webhook: when a post is published on a Facebook page, the link and full text of the post, the page account (identifier, username, display name), the post identifier, and the published and scheduled times.
2.5. Usage statistics
For each day you use the app we count active minutes and actions (edits, approvals, scheduling, sending to Brain) and record the time of your last activity and your team. The platform administrators (our team) use them; your team’s owner does not see them. We keep them for 12 months, after which they are deleted automatically.
2.6. Game Mode (optional)
Game Mode is an optional leaderboard that you turn on only if you want to, from Settings → Account (Cont). If you turn it on, we process the username you choose, an internal account identifier (not your email address; linked to the entry, not displayed), the number of social posts published, per day, and the level calculated from them. We count the posts from your teams’ Zernio calendars, by the email of the person who scheduled them. The leaderboard shows only the username, level and number of posts, displayed in the app to users with approved access, across all teams.
When you turn Game Mode off, your leaderboard entry is deleted. The username stays saved in your account, so you can pick it up again, until you delete your account.
2.7. Security, logs and support
- IP address: used only in server memory, to limit repeated attempts at sign-in, account creation, password reset and account deletion. We do not write it to disk. When the reset email is sent through Firebase (Google), we also pass on the IP address of the request, to protect against abuse.
- Password reset log: the email address, the outcome of each step, the technical code received, the sending channel (our email server or Firebase), the email server’s response and a support reference code. It contains no IP address. We use it when someone tells us the email did not arrive.
- Error log: the account email, the app route, the error message and technical details about the error. It contains no Drive file names. Only the platform administrators see it, to fix errors.
- Server technical logs: IP address, browser type (user agent) and the requested address, kept by the hosting infrastructure.
- Support correspondence: what you write to us at contact@thrivenexus.ro and our replies.
2.8. Data in your browser
Cookies and the other data kept in your browser (display preferences, technical markers, the offline page) are described in the Cookie Policy. We do not use analytics or advertising cookies.
3. Google user data: what we access and how we use it
This section describes separately the data we receive through Google APIs, in particular from Google Drive. In addition to the rest of this policy, the Limited Use rules below apply to it.
3.1. The permissions we request
https://www.googleapis.com/auth/drive: access to the files in Google Drive, so the app can read the items in the selected folders, save your edits and organise the files;openidandemail(https://www.googleapis.com/auth/userinfo.email): the email address of the connected Google account, so you know which account is linked.
Why narrower permissions are not enough. You work with folders that already exist in Drive and where new files keep appearing, placed there by you, by colleagues, by other tools or by Google Drive for Desktop. The drive.file permission only grants access to files the app created or that were opened or picked individually through it, so files added to the folder later from outside the app would not be visible. The drive.readonly permission is not enough because the app also writes to Drive: it saves edits, moves items between folders, creates folders and uploads images.
The drive permission technically allows access to your whole Drive, but the app uses it only as described below.
3.2. What we read from Drive
- Folder names, so you can choose your working folders: the folders in My Drive, in “Shared with me” and in shared drives, plus searching by folder name. Only the team owner or an admin can make this choice.
- File content, only from the selected folders and their subfolders: the text of the items, images, clips and PDF documents — including the files and folders (with all their contents) that shortcuts you placed in the selected folders point to.
- The metadata of those files: identifier, name, type (MIME), parent folder, creation and modification dates, size and shortcut targets.
- The email address of the connected Google account. We show it in Settings; your team members see it too.
To let you choose folders we show you the names of the folders in your Drive; file content is read only from the folders you chose (and from the files and folders that shortcuts placed there point to). Images and clips are displayed through an app proxy that serves only files from these places.
3.3. What we write to Drive
- we create the “Content Engine” folder with its working subfolders (De revizuit, Aprobate, Programate, Postate, Respinse — to review, approved, scheduled, posted, rejected) and category folders;
- we create and update the
content.md(the item’s text) and_review-meta.json(status, schedule and Brain path) files; - we upload the images you add to items;
- we rename, move and copy items between the working folders and into Brain;
- we permanently delete, without going through the Drive Trash, an item’s copy in Brain: when you send the item to Brain again, the file with the same name in its category is replaced, and when you remove the item from Brain, its copy is deleted.
3.4. What the app does in the background
While Drive (and, where applicable, Zernio) is connected, the app also performs operations without you pressing a button, even when you are not signed in:
- every few minutes (at most 10) it re-reads the selected folders so the review list is up to date, for teams active in the last 7 days, including when nobody is signed in;
- it automatically moves items to Programate or Postate (or back to Aprobate if the scheduling was cancelled), according to the post’s status in the Zernio calendar;
- about every 5 days it re-uploads to Zernio the images and clips of scheduled posts, so they do not expire before publication; if a copy has already expired, it reads it again from Drive. The files pass only through server memory, without being written to disk;
- it publishes scheduled Webflow articles, once their time has come, when someone on the team opens the app (the calendar or a re-sync);
- it sends the notification to your webhook, if you configured one, when a post is published on a Facebook page.
3.5. Team members
Drive is connected by the team owner or an admin. Approved members then work with that person’s Drive access: their encrypted server sessions receive a copy of the team’s Google tokens. Members see the items in the selected folders and the email address of the connected Google account. This is a feature you ask for when you invite people to your team.
3.6. How we keep Google data
- file content is kept only in server memory, for at most 7 days, so it loads quickly; it is gone on restart and when Drive is disconnected. We never write it to disk or to the database;
- images and clips pass through server memory only while we display them or send them to the publishing service you chose; your browser may cache them for at most 5 minutes;
- Google tokens are stored encrypted (AES-256-GCM) in the server sessions, in the background sync file and in the team settings in Firestore;
- in Firestore and in sessions we also keep the IDs and names of the selected folders and the email address of the connected Google account, never file content.
The periods for each category are in the storage table.
3.7. Who receives Google data
Drive data reaches only the publishing services you connect (Zernio, your WordPress or Webflow site, your webhook), and only what you send or schedule: the item’s text, images and clips, its Drive identifiers and the names of the media files. The app runs on our hosting provider’s server, and the encrypted tokens are stored in Firestore (Google); these are our infrastructure providers (see Who receives data), not recipients to whom we give data for their own purposes.
3.8. Limited Use of Google user data
Limited Use disclosure
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.
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.
Google’s policy: Google API Services User Data Policy.
In practice, for the data we receive from Google:
- we use it only to provide and improve the features visible in the app’s interface, described in this section;
- we do not transfer it except: to provide the visible features you use and only with your consent (for example, when you publish or schedule an item to a service you chose); for security purposes (for example, investigating abuse); to comply with the law; or as part of a merger, acquisition or sale of assets, only with your explicit prior consent;
- we do not use or transfer it for advertising, including personalised, interest-based or retargeted advertising;
- we do not sell it and we do not transfer it to advertising platforms, data brokers or other information resellers;
- we do not use it to determine creditworthiness or for lending purposes;
- we do not use it to create, train or improve artificial intelligence or machine learning models (the app has no AI features);
- we do not build databases and we do not keep permanent copies of Drive content.
Who can read your content. Your team members see the team’s items; that is a feature you ask for. Our team does not read your Drive content, except where:
- you give us explicit consent for specific files, for example when you ask support for help with a particular item;
- it is necessary for security purposes, for example to investigate a bug or abuse;
- the law requires it;
- the data is aggregated and anonymised and used for internal operations, in line with the law.
The same rules apply to everyone who works for us. You can revoke the app’s access to your Google account at any time; the steps are in section 8.
4. Purposes and legal basis
| Purpose | Data | Legal basis |
|---|---|---|
| Creating and running your account, sign-in, the session, teams and invitations | Account and team data, the session | Performance of the contract — Art. 6(1)(b) GDPR |
| Connecting Google Drive and working with your items: reading, saving, moving, background sync | Google user data (section 3) | Performance of the contract — Art. 6(1)(b). The access you grant through Google is an authorization you can revoke at any time. |
| Publishing and integrations (Zernio, WordPress, Webflow, webhook), including refreshing the media of scheduled posts | Integration credentials, the content sent, the name and email of the person scheduling | Performance of the contract — Art. 6(1)(b) GDPR |
| Sending the password reset email | Email, the IP address of the request | Performance of the contract — Art. 6(1)(b) GDPR |
| Support for the service | Our correspondence with you | Performance of the contract — Art. 6(1)(b) GDPR |
| Service security: rate limiting, request origin checks, server technical logs | IP address, browser type, requested address | Legitimate interest — Art. 6(1)(f): protecting accounts and the service against attacks and abuse. |
| Password reset log | Email, the outcome of each step, the reference code | Legitimate interest — Art. 6(1)(f): helping people who do not receive the reset email and spotting abuse. |
| Error log | Account email, route, error message | Legitimate interest — Art. 6(1)(f): finding and fixing errors quickly. |
| Usage statistics | Active minutes and actions per day, last activity, team | Legitimate interest — Art. 6(1)(f): running the platform and understanding how the service is used. |
| Game Mode (optional) | Username, email, number of published posts, level | Consent — Art. 6(1)(a). You withdraw it by turning Game Mode off. |
| Legal obligations: answering data requests and requests from authorities, accounting and tax records where applicable | The data each obligation requires | Legal obligation — Art. 6(1)(c) |
For team content, where we are a processor, we process data on the customer organisation’s instructions, and the legal basis is determined by that organisation. Information about how we assessed our legitimate interest is available on request.
Right to object (Art. 21 GDPR)
You can object at any time, on grounds relating to your particular situation, to processing based on our legitimate interest: service security, the password reset log, the error log and usage statistics. Write to us at contact@thrivenexus.ro. We stop the processing unless we demonstrate compelling legitimate grounds that override your interests, rights and freedoms, or the processing is needed to establish, exercise or defend legal claims.
4.1. Which data is required
To create an account you need an email address, a password and a display name; without them we cannot create the account or provide the service. The profile photo, Game Mode and the publishing integrations are optional. Connecting Google Drive is not required for the account, but without it the Drive review and publishing features cannot work.
4.2. Automated decisions
We do not make decisions based solely on automated processing, including profiling, that produce legal effects concerning you or similarly significantly affect you. Game Mode levels and scores are calculated automatically, but they have no such effects. New teams are approved manually by a platform administrator.
5. Where we keep data and for how long
Drive material is not duplicated: its content is kept only in memory, for a short time. For the rest of the data, here is where it is kept and for how long:
| Data | Where | How long |
|---|---|---|
| Account, profile, team and invitations (email, name, photo, roles, acceptance of the terms, publishing activity) | Firebase Authentication and Cloud Firestore (Google), region europe-west3 (Frankfurt, Germany) | Until you delete your account; deletion in the app is immediate (see the steps). Team data remains for as long as the team exists. |
| Session | The ce_session cookie (only the signed identifier); session data on the server, encrypted with AES-256-GCM | The cookie: until you close the browser or, if you tick “Remember me”, 30 days. On the server: 30 days from the last update; deleted immediately when you sign out. |
| Google tokens (access and refresh) | The server sessions of the owner and of approved members, the background sync file and the team settings in Firestore — encrypted with AES-256-GCM everywhere | Until you disconnect Drive: the token is revoked at Google (any remaining copies stop working) and removed from the settings. Otherwise, until the team is deleted or the session expires. |
| Drive file content (texts, lists of items) | Server memory only, for fast loading | At most 7 days; gone on restart and when Drive is disconnected. Never written to disk or to the database. |
| Images and clips from Drive | They pass through server memory only while we display them or send them to the publishing service; your browser may cache them | On the server, only for the duration of the transfer, without writing to disk. In the browser, at most 5 minutes; the cache is cleared when you sign out. |
| IDs and names of the selected folders | Team settings (Firestore) and the session | Until you change the folders, disconnect Drive or the team is deleted. |
| Background sync targets (folder IDs, the Google refresh token, the team’s Zernio key) | A file on the server, encrypted with AES-256-GCM | Deleted after 7 days without activity, when Drive is disconnected (the Zernio key: when Zernio is disconnected) or after repeated authentication failures. |
| Media keeper registry (the Zernio keys of accounts whose scheduled posts we keep up to date, technical counters) | A file on the server, encrypted with AES-256-GCM | Until you disconnect Zernio, the team is deleted or Zernio rejects the key 3 times in a row. |
| Registry of withdrawn connections (cryptographic fingerprints of disconnected keys and tokens, not the keys themselves; team and brand identifiers) | A file on the server, encrypted with AES-256-GCM | 30 days after the disconnection (we use it so that a withdrawn connection cannot come back from a session open on another device). |
| Integration credentials (Zernio key, WordPress application password, Webflow token, webhook address) | Team or brand settings in Firestore, encrypted with AES-256-GCM before writing; copies in the server sessions | Until you disconnect the integration or the team is deleted. |
| Usage statistics | Firestore | 12 months. |
| Game Mode | Firestore: the leaderboard entry; the username, in your account | The entry: until you turn Game Mode off. The username: until you delete your account. |
| Password reset log | A file on the server, encrypted with AES-256-GCM | 30 days, at most 1,000 entries. Contains no IP addresses. |
| Error log | Server memory only | Until the app restarts, at most 200 entries. Contains no Drive file names. |
| IP addresses used for rate limiting | Server memory only | Rate-limit windows of a few minutes; gone at the latest on restart. Never written to disk. |
| Server technical logs (IP address, browser type, requested address) | The hosting infrastructure | At most 30 days. |
| Support correspondence | The contact@thrivenexus.ro mailbox | As long as needed to resolve the request and to be able to show how we answered it. |
| Posts, articles and media sent to Zernio, WordPress, Webflow or your webhook | At those providers, in your accounts | Under their policies. You delete them there; deleting your account with us does not touch them. |
| Data in your browser | Your browser | See the Cookie Policy. |
We do not make separate backups of the database. If the infrastructure provider keeps backups, they are overwritten in their normal cycle. When a period expires, the data is deleted automatically.
6. Who receives data
We do not sell or rent personal data and we do not use it for advertising. Data reaches only the recipients below.
6.1. Our providers (processors)
- Google (Firebase Authentication and Cloud Firestore): accounts, teams, settings (with the secrets encrypted), usage statistics and Game Mode. Database region: europe-west3 (Frankfurt, Germany). Firebase also sends password reset emails when we do not use our own email server or when it fails; it then receives the email address and the IP address of the request.
- Hosting provider: Hostinger International Ltd., with the server in Germany (European Union). The app runs on this server: the memory holding Drive items, the sessions and encrypted files described above, and the technical logs.
- Email provider: Google Workspace (Google Ireland Limited), through which we send password reset emails (your email address and the reset link).
6.2. Google, as the provider of your Drive account
Drive data flows between the app and your Google account through the Google Drive API. Google processes it as the provider of your account, under its own terms.
6.3. Integrations you choose
Zernio, WordPress, Webflow and the notification webhook are services you choose and connect yourself, with your own accounts and keys. We send them only what you publish or schedule and what is needed for scheduling to work (details in What we send when you publish). Data that reaches them is processed under those providers’ own terms and policies.
- Zernio (according to its privacy policy, ZERNIO SOFTWARE SL, Spain): posts, media and their metadata.
- Your WordPress or Webflow site: articles and their images.
- The webhook address you configure: notifications about published posts.
Some transmissions happen without a click from you, as part of the features you turned on: re-uploading media for scheduled posts, publishing scheduled Webflow articles and notifications to the webhook (see background actions).
6.4. Authorities
We disclose data to authorities only when the law requires us to, on the basis of a lawful request.
6.5. Transfers outside the European Economic Area
- Google LLC (USA): transfers rely on the adequacy decision for the EU-US Data Privacy Framework (Commission Implementing Decision (EU) 2023/1795), under which Google LLC is certified, and on the standard contractual clauses adopted by the European Commission (Commission Implementing Decision (EU) 2021/914), included in Google’s data processing terms.
- Hosting: the app’s server is located in Germany (European Union).
- Zernio: according to its policy, it is established in Spain, in the European Economic Area.
- Integrations you choose: if the provider you chose (for example, the one hosting your site) is outside the EEA, the transmission takes place on your instruction, as part of the service you requested, with the safeguards offered by that provider.
On request, we send you a copy of the safeguards used. Write to us at contact@thrivenexus.ro.
7. Your rights
You have the following rights over your personal data:
- Right of access: to find out whether we process your data and to receive a copy of it.
- Right to rectification: to correct inaccurate data. You can change your name, photo and password yourself, in Settings → Account (Cont).
- Right to erasure: you can delete your account yourself, immediately (see the steps), or ask us by email to delete your data.
- Right to restriction of processing: to ask us to stop using the data for a period, for example while we check a dispute.
- Right to data portability: to receive the data you gave us in a structured, commonly used and machine-readable format, or to have us send it to another provider where technically feasible. Your material is in Google Drive anyway.
- Right to object: to processing based on our legitimate interest (see the right to object).
- Right to withdraw consent: for Game Mode, at any time, by turning it off in Settings → Account (Cont). Withdrawal does not affect processing carried out before it.
How to exercise them: write to us at contact@thrivenexus.ro, preferably from your account’s address. We reply within one month (extendable by two further months for complex requests, with notice within the first month), free of charge. If we cannot confirm that the request comes from you, we may ask for additional information. For team content, where the customer organisation is the controller, we pass your request on to it and help it respond.
7.1. Complaint to the supervisory authority
If you believe we process your data in breach of the law, you can lodge a complaint with the Romanian supervisory authority:
- Authority
- Romanian National Supervisory Authority for Personal Data Processing (ANSPDCP)
- Address
- B-dul G-ral. Gheorghe Magheru nr. 28-30, Sector 1, cod poștal 010336, București, România
- Phone
- +40 318 059 211, +40 318 059 212
- Website
- www.dataprotection.ro
You can also lodge a complaint with the supervisory authority of the Member State where you live, where you work or where the alleged infringement took place (Art. 77 GDPR). If you write to us first, we can often resolve the matter faster.
8. How to manage and delete your data
You control your data directly from the app. The steps below are in the order you would usually follow; you can also take them separately.
- Disconnect Google Drive.
Settings → Connections (Conexiuni) → Google Drive → “Deconectează Drive” (Disconnect Drive). Only the team owner or an admin can do this; if you are a member, ask them. The effect is immediate: we revoke at Google the access granted to the app, stop background sync, clear the items from server memory and remove Drive from the team settings. Your files stay untouched in Drive.
- Revoke access from your Google account.
Open your Google account permissions, choose Content Engine and remove its access. From that moment our tokens stop working and the app can no longer read or write anything in Drive. To remove the settings from the app as well, then disconnect Drive as in step 1.
- Disconnect the publishing integrations.
Settings → Connections (Conexiuni) → Zernio, WordPress, Webflow or the notification webhook (owner or admin). We delete the key from the team settings and the session; for Zernio, also from background sync and the media keeper. The key stays valid at the provider until you revoke it from your account there.
- Turn off Game Mode.
Settings → Account (Cont) → Game Mode. Your entry disappears from the leaderboard.
- Delete your account.
Settings → Legal and data (Legal și date) → “Șterge contul” (Delete account). If your account is still waiting for activation or was rejected, the “Șterge contul” button is right on the waiting screen. If you are asked to accept updated Terms and you do not agree, the “Șterge contul” button is also in the acceptance window. You confirm with your password and type STERGE. Deletion is immediate and automatic.
What is deleted:
- the sign-in account (Firebase Authentication) and your profile (name, photo, roles, acceptance of the terms, publishing activity, Game Mode username);
- your invitations (and therefore your membership of other teams), your Game Mode entry, your usage statistics and your address in the error log;
- all your sessions on the server and the session cookie in the current browser;
- if you own a team with no other members: the team, with its settings and credentials, and the team’s invitations. We also revoke the Google token, stop background sync, remove the Zernio key from the media keeper and clear the items from memory.
If your team still has members, first remove them in Settings → Team (Echipă) or write to us to transfer the team, then come back.
What is NOT deleted:
- the files in Google Drive: they are yours, and deleting the account does not touch them;
- posts and media already sent to Zernio and published on social networks, articles on WordPress or Webflow and notifications already delivered to the webhook; you delete them directly at those providers. Your name and email remain in the metadata of the posts you scheduled in the team’s Zernio account;
- the access keys you created at Zernio, WordPress or Webflow; you revoke them from your accounts there.
After deletion, any copies left in server memory disappear within at most 7 days or on restart. The password reset log keeps entries with your address for up to 30 days, and the server technical logs for at most 30 days. If automatic deletion does not fully succeed, the app tells you and does not delete the sign-in account, so you can try again (the team’s Google access may already be revoked); you can also write to us at contact@thrivenexus.ro, and we complete the deletion within one month.
- Request a copy or deletion of your data by email.
Write to contact@thrivenexus.ro, preferably from your account’s address, and tell us what you need: a copy of the data, a correction or deletion. We reply within one month (extendable by two further months for complex requests, with notice within the first month), free of charge.
- Clear the data in your browser.
You can clear it at any time in your browser settings. When you sign out, we clear the app’s cache in the browser anyway. Details in the Cookie Policy.
9. How we protect data
- Encrypted connections: all traffic goes over HTTPS, and the browser is instructed (HSTS) to use HTTPS only.
- Sessions: the session cookie is HttpOnly (page scripts cannot read it), Secure and SameSite=Lax. It holds only a random identifier signed with HMAC, verified in constant time, which changes every time you sign in. The session data stays on the server.
- Encryption at rest: sessions, sync targets, the media keeper registry and the password reset log are encrypted on disk with AES-256-GCM. Google tokens and integration secrets are encrypted the same way before they are written to Firestore. The key is derived (HKDF) from a server secret kept in environment variables, separate from the code and the data.
- No copies of content: Drive content is kept only in memory, for at most 7 days.
- Access control: Firestore rules allow a team’s data to be read only by its approved members and the platform administrators; only the owner or an admin can change the team’s resources.
- Page protection: a content security policy (CSP) with a nonce on every request, a ban on framing the pages in other sites, security headers and an origin check on requests that change data.
- Rate limiting on sign-in, account creation, password reset and account deletion.
- Validation: everything you send is validated on the server, and text displayed as HTML is escaped before display.
- No third-party scripts: we load no analytics, advertising or tracking scripts.
9.1. Security incidents
If a security breach affects personal data, we notify ANSPDCP within 72 hours of becoming aware of it, where the law requires, and we inform the affected users without undue delay when the risk to them is high. For team content we inform the customer organisation without undue delay. If the incident concerns data received from Google, we also notify Google.
Found a security issue? Write to us at contact@thrivenexus.ro. We treat such reports as a priority.
10. For adult professionals only
The service is intended only for professionals (companies, sole traders, liberal professions) who are at least 18 years old and use it in their business. It is not intended for minors, and we do not knowingly collect data from people under 18. If we learn that an account belongs to a minor, we delete it.
11. Changes to this policy
- When we change this policy, we update the date at the top of the page.
- For significant changes we notify you before they take effect, by email or with a message in the app.
- Before we use Google data in a new way or for a new purpose compared with what this policy describes, we ask for your consent again.
- We send you previous versions of this policy on request, at contact@thrivenexus.ro.