Privacy Policy

Last updated: 16 October 2026, effective from that date

The Slovak version is the binding one. This English version is a translation provided for understanding.

1. Data controller

The controller of the NowAds.ai platform is 1st Agentic Engineering, s. r. o., Čajakova 2173/4, 010 01 Žilina, Slovensko, IČO: 57 542 031, DIČ: 2122810778. Obchodný register Okresného súdu Žilina, oddiel Sro, vložka č. 90781/L. Not registered for VAT. Contact: [email protected], phone +421 908 537 299.

2. Who the service is for and whose data we process

Since 26 September 2026 the Service is intended only for businesses, that is companies and sole traders ordering it in the course of their business; we do not provide it to consumers (Terms of Service, Art. 3).

The customer is therefore a business, but personal data belongs to people. This policy concerns the users the customer invites to its workspace, the customer's contact persons (for example for billing) and sole traders, whose billing details (name, business address, company ID) are personal data too.

Data the Service reads from the customer's advertising and analytics accounts, including any personal data of other people in them, is processed on behalf of the customer as a processor. For that data the customer is the controller and the relationship is governed by a separate data processing agreement (Terms of Service, Art. 16).

3. What data we process

  • Registration data: first name, surname, e-mail address, country, password (hashed); when signing in with Google, name, e-mail address, profile photo and Google account identifier
  • Authentication data: Google OAuth access tokens, session tokens
  • Advertising data: access tokens for Google Ads, Meta, Microsoft Advertising and Sklik, granted by you through OAuth
  • Operational data: IP address, browser user agent, sign-in time and entries in the system log (for example a sign-in with the e-mail address and IP address)
  • Content data: campaigns, templates, banners and scraped data created by the user, conversations with the assistant and files uploaded for processing
  • Billing and payment data: customer billing details, documents, payments and payment e-mails (section 5)
  • Business declaration made at registration (section 6)
  • Record of artificial intelligence usage (section 7)

4. Purposes and legal bases

  • Performance of a contract (Art. 6(1)(b) GDPR): providing the Service, that is creating and managing advertising campaigns, the assistant and reports; authentication and account security; communication (verification e-mails, invitations, notifications); proforma invoices and tracking the limits set out in the Terms of Service
  • Legal obligation (Art. 6(1)(c) GDPR): issuing and keeping invoices and recording payments received under Slovak Act No. 431/2002 Coll. on Accounting (section 5)
  • Legitimate interest (Art. 6(1)(f) GDPR): security and prevention of abuse; showing that the contract is not a consumer contract (section 6); showing what we sent to the customer and when, and establishing or defending legal claims (section 5); keeping the cost of artificial intelligence under control (section 7); measuring traffic without cookies or a persistent identifier until you consent to analytics cookies (section 10)
  • Consent (Art. 6(1)(a) GDPR): analytics, preference and marketing cookies (section 10) and improving the service from anonymised analytics

The data needed for registration and billing is a contractual requirement: without the business declaration we do not create an account, and without billing details we cannot issue a proforma invoice.

5. Billing details, documents and payments

To issue proforma invoices and invoices, the workspace administrator enters the customer's billing details: name or business name, address (street, city, postcode, country), company ID (IČO), tax ID (DIČ), VAT ID (IČ DPH), the e-mail address for documents, and a note. Without the company ID, the tax ID (or VAT ID) and the address no proforma invoice is issued.

  • Documents: proforma invoices and invoices. Each document carries a copy of the customer's billing details as they were when it was issued, which does not change afterwards; the Service administrator may adjust the due date and period of an open proforma invoice. An incorrect document is cancelled, not deleted.
  • Payments: transactions on our account at Fio banka, which we download from the bank automatically: date, amount, variable and other symbols, the payer's account name and number and the message for the recipient. We store the whole transaction record as the bank sent it, including outgoing payments. They are used to match a payment to a document.
  • Payment e-mails: a record of sending a document, a payment confirmation, reminders, a request to complete billing details and a notice of suspension of the Service: to whom (e-mail addresses), when, through which service and with what result. They go to the billing e-mail address or, if none is set, to the workspace administrators.

Legal basis. Performance of a contract. Invoices and records of payments received are part of our accounts, which we must keep under Act No. 431/2002 Coll. on Accounting (Art. 6(1)(c) GDPR). We keep proforma invoices and payment e-mails on the basis of our legitimate interest in showing what we sent to the customer and when, and in establishing or defending claims under the contract (Art. 6(1)(f) GDPR).

Retention. Invoices and payment records for 10 years following the year to which they relate (Section 35 of the Accounting Act), including after the workspace is closed. Proforma invoices and payment e-mails for as long as the workspace exists and 4 years after it is closed (the general limitation period under Section 397 of the Slovak Commercial Code); if a dispute starts in that time, until it is resolved. A proforma invoice that an invoice refers to is not deleted before the invoice. The billing details in the workspace settings are deleted when the workspace is closed; they remain on documents already issued.

6. The declaration “I am ordering as a business”

When registering by e-mail or with Google you confirm a declaration that you are ordering the Service as a business, in the course of your business activity and not as a consumer. No new account is created without it; a person joining an existing workspace by invitation does not make it.

What we store: the exact wording of the declaration you saw, the language in which you saw it, the time, the registration method (e-mail or Google) and the identifiers of your profile and workspace.

Purpose and legal basis: to show that the contract is not a consumer contract (Terms of Service, Art. 3) and to establish or defend legal claims; legitimate interest (Art. 6(1)(f) GDPR).

Retention: for as long as the workspace exists and 4 years after it is closed (the general limitation period under Section 397 of the Slovak Commercial Code); if a dispute starts in that time, until it is resolved. Closing the profile or the workspace does not delete it, because it may be needed precisely after the contract ends.

When registering with Google, the declaration is carried through the redirect to Google and back by the short-lived cookie nowads_podnikatel (section 10).

7. Artificial intelligence

The assistant and ad text generation work with a language model of an AI provider (Anthropic or OpenAI). When you use them, we send the provider the content of the conversation (your messages and earlier replies), the results of tools, that is data read from your advertising and analytics accounts and spreadsheets, the list of accounts you have access to, and the content of files you give the assistant to process. Without it the assistant would have nothing to answer from. If you use neither the assistant nor text generation, nothing is sent to the provider.

Who holds the contract with the provider depends on the key the assistant is running on:

  • The NowAds key (the assistant only, during the trial and in the subscription up to the limit set in the Terms of Service, Art. 4 and 5): we choose the provider (Anthropic or, where set, OpenAI) and it processes the data as our processor, and for data we process on behalf of the customer as a sub-processor.
  • Your own key or the workspace key: we send the data to the provider whose key you or the workspace administrator connected, and it processes it under the contract the customer has with it (Terms of Service, Art. 14). If more than one key is available to you, you choose which one is used in the assistant.
  • The NowAds.ai connector in your own AI tool: the data you request through it goes to that tool under your contract with its provider.

Transfers outside the EU. Both providers also process data outside the European Economic Area, in particular in the United States; Anthropic states that data is stored in the US (Anthropic Privacy Center). For the NowAds key our contracting party, as we are established in the EEA, is Anthropic Ireland, Limited (Commercial Terms) or OpenAI Ireland Ltd. Anthropic's data processing agreement (Anthropic DPA) contains the European Commission's standard contractual clauses (Art. 46(2)(c) GDPR), which apply where the law requires them; how Anthropic Ireland passes data to Anthropic, PBC in the US is not stated in the public agreement. For OpenAI the contracting party is OpenAI Ireland Ltd., which transfers data to OpenAI affiliates or third parties on the basis of standard contractual clauses or an adequacy decision (OpenAI DPA, section 4.1). Neither Anthropic nor OpenAI is certified under the Data Privacy Framework. With your own key, whatever the customer agreed with the provider applies.

Training. We do not use the data to train models. On the NowAds key, under the contract terms, neither does the provider: Anthropic may not under its Commercial Terms, and under its documentation OpenAI does not use API data for training unless the customer explicitly opts in. With your own key, the customer's contract with the provider decides.

Usage records. For each model call we record who started it, in which workspace and conversation, whose key it ran on (own, workspace or NowAds), the provider, the model, the name of the skill, the number of tokens and the cost. Spending on the NowAds key is also summed per day for the whole workspace, without data about a particular person. This serves the AI limits on the NowAds key, the budget of the workspace key and the usage overview; the legal basis is performance of the contract and our legitimate interest in keeping costs under control. A person's call records are deleted when their profile is closed; what they spent from the workspace key stays with the workspace so that its administrator can see where the budget went. Usage totals and the workspace key budget are deleted when the workspace is closed; the limits we set for the workspace remain (section 11).

Conversations with the assistant are stored in the workspace so that you can return to them. You can delete them in the assistant; otherwise they are deleted when the workspace is closed.

8. Recipients and transfers outside the EU

We pass data only to these recipients:

  • Hosting: RackNerd LLC (USA). The Service, including its database, runs on a virtual server rented to us by RackNerd in a data centre in the US (Buffalo, New York). The data the Service processes is therefore stored in the US. RackNerd is not certified under the Data Privacy Framework and does not offer a data processing agreement with standard contractual clauses (it confirmed this at our request on 28 September 2026); the transfer of data to the US therefore does not rely on safeguards under Article 46 GDPR.
  • Cloudflare, Inc. (USA): traffic to the website and app at nowads.ai passes through Cloudflare's network, which delivers the Service and protects it from attacks. Your AI tool connects to the connectors on subdomains (such as mcp.nowads.ai) directly on our server; the central connector mcp.nowads.ai, however, calls the app through nowads.ai, so the arguments and results of its tools pass through Cloudflare. In doing so Cloudflare processes IP addresses, browser data and the content of the pages and responses transmitted. We also receive e-mail to @nowads.ai addresses through Cloudflare. Cloudflare is our processor, is certified under the Data Privacy Framework, and its data processing agreement contains standard contractual clauses.
  • Resend (Plus Five Five, Inc., USA): we send e-mails primarily from our own mail server. An e-mail goes through Resend in full, including addresses, subject, body and attachments, if one of its recipients is an Outlook, Hotmail, Live or MSN mailbox, or if our server does not accept the message at the moment of sending. Resend sends it from Amazon Web Services infrastructure in the US; the transfer relies on the Commission's adequacy decision for the EU-U.S. Data Privacy Framework, under which Resend is certified, and on the standard contractual clauses in its data processing agreement.
  • Backblaze, Inc. (USA): we encrypt the nightly database backup on our own server and store a copy in Backblaze B2, in its EU data centre (Amsterdam, region eu-central-003). Backblaze receives only the encrypted file; only we hold the key. Backblaze is certified under the Data Privacy Framework and its data processing agreement contains standard contractual clauses.
  • Google reCAPTCHA (Google LLC, USA): reCAPTCHA v3 runs on the sign-in and registration page. The script in your browser sends Google data about your device, browser and interaction with the page, including your IP address, and Google returns a score on which we refuse requests that look automated. Google processes this data as our processor, also outside the EEA, in particular in the US; the transfer is covered by standard contractual clauses and Google LLC's certification under the Data Privacy Framework.
  • Google Tag Manager and Google Analytics 4 (Google LLC, USA): traffic measurement and, with consent, advertising signals (section 10). Google Analytics is our processor; it may process data in the US, covered by standard contractual clauses and Google LLC's certification under the Data Privacy Framework.
  • AI providers (Anthropic, OpenAI): only when you use the assistant or text generation, to the extent and on the terms described in section 7.
  • Fio banka, a.s., pobočka zahraničnej banky (Bratislava; the bank is based in Prague): holds our account; we download payment data from it, and the bank processes it as a separate controller.
  • The targeting map in the interface loads its map tiles from openstreetmap.org; OpenStreetMap sees your IP address when it does. Country borders and map icons come from our own server.
  • Google profile photo: for anyone who signs in with Google, the interface shows their profile photo straight from Google's servers (in the menu and the profile, in Team to the workspace administrators, and in administration to the Service administrators); Google sees the IP address of whoever is viewing the page.

Advertising and analytics platforms (Google Ads, Google Analytics, Google Sheets, Meta, Microsoft Advertising, Sklik): when you connect the Service to your account, we read data from it and write the changes you confirm, on the basis of the authorisation you granted. The platforms are not our processors in this; they process the data in your accounts under your own contract with them.

We never sell your data to third parties and it is not used to train artificial intelligence models (section 7).

9. Data security

To protect your data we use:

  • Encryption of access tokens (AES-256-GCM)
  • A random session token with limited validity, stored only as a hash (SHA-256)
  • Two-factor authentication (TOTP)
  • Password hashing (scrypt)
  • CSRF protection, rate limiting, IP blocking
  • HTTPS (TLS) for all communication
  • Security headers (CSP, HSTS, X-Frame-Options)

10. Cookies

We use the following types of cookies:

  • Strictly necessary: the session cookie nowads_session (sign-in, 30 days) and the CSRF token csrf_token (form protection, 30 days), required for the site to work. For the duration of signing in with Google, accepting an invitation or connecting the connector, the short-lived cookies oauth_state, invite_token and mcp_navrat (10 minutes). When resetting a password, completing a Google sign-in with two-factor authentication and deleting a profile, the cookies nowads_obnova (1 hour), nowads_2fa (5 minutes) and nowads_zrusenie (30 minutes): they carry the one-time code from the link or the redirect so it is not in the page address; they are deleted after successful use or on sign-out, otherwise they expire. When registering with Google, the cookie nowads_podnikatel (10 minutes, readable only by the server): it carries your business declaration, specifically the language in which you saw it, through the redirect to Google and back, and is deleted on your return. For Service administrators only, the cookie nowads_pohlad (viewing the Service as a customer, 8 hours). On the sign-in and registration page reCAPTCHA stores the item _grecaptcha for its risk assessment, and Google may set the cookie _GRECAPTCHA on its own domain (section 8).
  • Preferences: consent to this category is passed to Google tags (Consent Mode); we do not use our own preference cookies. Some interface choices (for example the last opened mailbox) are kept in the browser's storage; none of it is sent to third parties.
  • Analytics: Google Tag Manager loads on every page except a shared report (a /r/… link) and runs Google Analytics 4. Until you consent to analytics cookies, Google Analytics sets no cookies and sends Google measurements without cookies or a persistent identifier (only a random number for each page load): events on the page (page view, scrolling, outbound link click, file download, video engagement, form interaction, site search) with their parameters, time, browser type, page address, referrer, whether the address carried ad click information, and consent state. With consent it measures traffic with a pseudonymous identifier in a cookie. According to Google, Google Analytics does not store IP addresses. When you withdraw consent, we delete the Google Analytics cookies (_ga, _ga_…) from this browser.
  • Marketing: with your consent we send the Google tag the advertising signals of Google Consent Mode (ad_storage, ad_user_data, ad_personalization) as granted, without it as denied. We run no advertising tags (Google Ads, Meta Pixel) on the site today; the only tag is Google Analytics 4. With consent the Google tag may store and read Google advertising cookies (for example _gcl_aw) and the _gcl_ls item in browser storage, that is the ad click that brought you here, and Google Analytics may collect Google advertising identifiers. They can be used for advertising (remarketing, audiences) only when Google Analytics is linked to a Google Ads account. The Google tag does not send Google the email or phone you enter in forms: user-provided data collection is turned off in it. When you withdraw consent, we delete the Google advertising cookies (_gcl_…) and the _gcl_ls item from this browser. Consent to this category given before this version of the policy took effect is disregarded (it was given for a different description); advertising signals are sent as denied until you give it again through Cookie settings.

Strictly necessary cookies do not require consent (Section 109(8) of Slovak Act No. 452/2021 Coll. on Electronic Communications); we process them to perform the contract and on the basis of our legitimate interest in security.

You manage cookie consent through the banner shown on your first visit. We implement Google Consent Mode v2 for automatic consent handling. Your choice is stored in the browser (the nowads_consent item in the site's storage, with no expiry date). You can change or withdraw it at any time through here and in the footer of the public home page; if you clear the item in your browser settings, the banner appears again.

11. Data retention

  • We keep account and workspace data for as long as the account exists.
  • Closing a profile while other people remain in the workspace: we immediately delete your sign-ins, access tokens, AI key, previews of changes put up for confirmation (all of them, including confirmed, cancelled and expired ones), saved Overview views, records of your artificial intelligence calls, connector access and the monthly cap an administrator set for you on the workspace AI key. What you spent from the workspace key stays with the workspace (section 7). Workspace data stays with the workspace, including conversations and the change history with your e-mail address on the changes you made.
  • Closing the last profile closes the whole workspace, and we delete its data from the production database immediately, as well as its templates, logos, banners and uploaded fonts on the server that our records attribute to it; its other images are removed by the daily clean-up (below). What remains are the documents issued (invoices and proforma invoices, including cancelled ones, with the customer's billing details), records of payments and of payment e-mails sent, the business declaration, e-mails we exchanged, the price and limits we set for the workspace, and the system log (sections 5 and 6); an unpaid proforma invoice is cancelled. We record the day the workspace ceased to exist and its name and, 4 years later, automatically delete the declaration, proforma invoices, payment e-mails, price and limits together with that record; if a dispute begins in that time, only after it ends. Invoices and payment records are deleted automatically 10 years after the year to which they relate. E-mails we exchanged are kept for as long as they are needed to deal with the matter and to establish or defend legal claims.
  • When the contract ends by notice, we follow Art. 18 of the Terms of Service: on request we make an export available and then delete the data in the same way as when the last profile is closed (above); the same remains.
  • The system log (security and operational events, for example sign-ins with the e-mail address and IP address) is kept for 12 months from the entry and then deleted automatically. An IP address we block manually for misuse of the Service stays on the block list until we unblock it.
  • Sign-ins and links. Sign-in records (sessions), links for e-mail verification, password reset and closing the profile, and the interim two-step verification step are deleted after they expire, in the daily clean-up. An unanswered invitation to a workspace (with the invitee's e-mail) is deleted 30 days after it expires. The record of connector access you disconnect (the AI tool's name, the IP address it connected from and the times) is deleted 12 months after disconnection; the most recent ones are listed in Connections.
  • Copies of automatic e-mails (e-mail verification, password reset, invitations) that we keep in our mailbox are deleted 90 days after sending.
  • Uploaded files (.xlsx, .csv, .tsv) are kept for at most 24 hours after upload and then deleted automatically, including the file on disk; you can delete them earlier. What the assistant read from a file stays in the conversation as a tool result until you delete the conversation.
  • Template images, logos and banners that no template or campaign points to any more (deleted, replaced by newer ones or never saved) are moved away from their public address in the daily clean-up once they are more than 30 days old, and deleted 30 days later (in case the database is restored from a backup).
  • Database backups: we keep the last 14 nightly backups on the server (about 14 days), their encrypted copies off the server for 60 days, and backups taken before deploying a new version or before a manual change to the database for 30 days, then delete them automatically. Data we deleted from the database remains in backups until they are deleted.

12. Your rights

Under the GDPR you have the right to:

  • Access your data
  • Rectify inaccurate data
  • Erase data (the right to be forgotten)
  • Restrict processing
  • Data portability
  • Object to processing, in particular processing based on legitimate interest
  • Withdraw cookie consent

We cannot erase data we must keep by law or data needed to establish or defend legal claims (Art. 17(3) GDPR); for such data we will tell you how long we keep it.

Automated decision-making. A workspace is suspended automatically, without human review, when the trial, paid or manually granted period ends and the next one is not paid: we have not matched the payment to a proforma invoice by the variable symbol and amount in the bank statement, or you cancelled the subscription (Terms of Service, Art. 5). Suspension switches off the Service, including the assistant, reports and the connector, for all workspace members until the payment is matched or, for a cancelled subscription, until we restore it by agreement and the restored period is paid (or we temporarily grant access to the workspace or exempt it); no data is deleted. The decision is necessary for the performance of the contract (Art. 22(2)(a) GDPR). If you believe it is wrong, for example you paid and the payment was not matched, write to us at [email protected], phone +421 908 537 299: a person will review it, and you can express your view and contest it. We likewise automatically refuse a sign-in or registration that reCAPTCHA scores as likely automated; you can write to us in that case too.

You can exercise your rights by contacting [email protected], phone +421 908 537 299. If you believe that the processing of your data infringes the GDPR, you may lodge a complaint with the supervisory authority (section 14).

13. Changes to this policy

This policy may be updated. Users will be informed of changes by e-mail.

14. Contact and supervisory authority

If you have questions or requests concerning the protection of personal data, contact us at [email protected], phone +421 908 537 299. We have not appointed a data protection officer: Art. 37 GDPR does not require it, as our core activities do not consist of regular and systematic monitoring of individuals on a large scale or of large-scale processing of special categories of data or data relating to criminal offences.

The supervisory authority is Úrad na ochranu osobných údajov Slovenskej republiky (the Office for Personal Data Protection of the Slovak Republic), Galvaniho Business Centrum II, Galvaniho 7/B, 821 04 Bratislava, Slovakia, dataprotection.gov.sk.

15. Google API Services User Data Policy

NowAds.ai's use and transfer to any other app of information received from Google APIs will adhere to the Google API Services User Data Policy, including the Limited Use requirements. In practice this means:

  • we use this data only to provide the features you asked for, that is reports and the changes you confirm yourself;
  • we do not transfer it to anyone else except where it is necessary to provide that feature, where the law requires it, or as part of a merger or acquisition;
  • we do not use it for advertising or profiling, and we do not use it to develop, improve or train generalised or non-personalised artificial intelligence or machine learning models. When you use the assistant, the content is sent to the model provider (section 7) solely to answer that one request: that is processing, not training, and the model learns nothing from it;
  • no human reads it, except with your explicit consent, to resolve a security incident, to comply with the law, or where it is aggregated and anonymised.

You can end the access granted through Google at any time with the Odpojiť (Disconnect) button: in Moje prepojenia (My connections) for your personal connection, in Tímové prepojenia (Team connections) for the team one (only a workspace admin can do this). We delete the token on our side and the app loses access immediately. You revoke the permission itself with Google on the Third-party apps with account access page.

16. Data from Meta APIs (Facebook, Instagram)

You connect Meta with Facebook Login in Team connections or My connections. We request the permissions ads_management, business_management, pages_show_list and pages_read_engagement, and Meta gives us an access token with the ones you grant. You do not sign in to NowAds.ai with Facebook; Facebook Login only connects ad accounts.

  • What we read: the ad accounts you can access, their campaigns, ad sets, ads, creatives and custom audiences; performance (impressions, reach, clicks, spend, purchases, leads, conversion value), also by country, region, age, gender, device and placement; Business Managers (id, name, verification status, vertical) with their ad accounts and Pages; for Pages, the name, category, description, follower count and profile picture; and other fields of these objects that you ask for in the assistant or through the MCP connector. For a personal connection, also the name of your Facebook account.
  • What we do not read: posts, comments, messages, Page Insights, or the names and ids of followers. We do not publish to Pages and we do not change Business Manager settings.
  • Why: only for the features you asked for: overviews, reports and the campaign changes you confirm yourself. We do not sell Meta data and we do not use it for advertising or for training artificial intelligence models. An ad account id can appear in the address of an app page, and page addresses also reach our traffic measurement (section 10).
  • Who receives it: only at your direction, in a report link, in report e-mails to the addresses you enter, in an export, to the model provider when you use the assistant (section 7), and to your own AI client through the MCP connector; otherwise only the processors in section 8.
  • How long: the token (encrypted), the lists of ad accounts, Pages and Business Managers of the team connection (encrypted), the selection of ad accounts, Pages and Business Managers in the workspace settings (ids only), and for a personal connection the name of your Facebook account and the loaded account list in your profile, while the connection exists. We do not store Page profile pictures. Reports, the change history, the Audit log, assignments in Team and conversations belong to the workspace and remain after disconnecting; a report link can be opened until it expires, someone revokes it, the report is deleted in Reports, or the workspace is deleted. A report that can no longer be run after disconnecting can be deleted in Reports, with its links and sending schedule, by the report's author or a workspace admin, and also by anyone who still reaches its accounts. Your previews of changes put up for confirmation (all of them, including confirmed, cancelled and expired ones) and your saved Overview views also remain after disconnecting; you can delete a view yourself in Overview, and deleting your profile deletes both. We delete system log entries automatically 12 months after they are recorded; deleting the workspace does not delete them sooner. Deleted data remains in backups until they are deleted (section 11).

How to delete data from Meta:

  1. In the app, click Odpojiť (Disconnect) on Meta: in My connections for your personal connection, in Team connections for the team one (only a workspace admin can do this). We delete the token, the saved lists of ad accounts, Pages and Business Managers and their selection; for a personal connection also the loaded account list in your profile. This deletes the token only on our side; access at Meta ends only with step 2.
  2. To revoke access at Meta, go to Facebook: Settings & privacy, Settings, Business integrations (or Apps and websites), and remove NowAds.ai. Removing the app revokes access but deletes nothing in NowAds.ai: step 1 deletes the token and lists, step 3 the rest, and the system log is deleted when the period in section 11 runs out.
  3. You can delete conversations yourself in the assistant and reports in Reports (with their links and sending schedules; after disconnecting, the report's author or a workspace admin can do this too). The change history, the Audit log and the rest of the workspace data are deleted only when the whole workspace is deleted, for example by deleting its last profile: in My profile, click Vymazať môj profil (Delete my profile) and confirm the link we send you by e-mail. While other people remain in the workspace, deleting your profile deletes your sign-ins and personal connections (My connections); the team Meta connection, even if your Facebook account connected it, your conversations and the rest of the workspace data remain. So delete your conversations before deleting your profile and disconnect the team connection in step 1 (section 11). You can also ask us to delete data as described in section 12.
Back to the home page