creavio PRIVACY POLICY Last Updated: October 24, 2026
This Privacy Policy describes how creavio, Inc. ("creavio," "we," "us," "our") collects, uses, shares, and protects information when you use our platform and services.
1. INFORMATION WE COLLECT 1.1. Information You Provide Directly. When you create an account or use the Platform, we collect: your name, email address, password, payment information (processed by Stripe), business name and details, and any other information you choose to provide. 1.2. Information Collected Automatically. When you access the Platform, we automatically collect: IP address, device type and operating system, browser type and version, pages visited and features used, and usage analytics. 1.3. User-Uploaded Content. Creators upload content to the Platform including: photographs, videos, graphics, contracts and documents, and other files related to their creative business. 1.4. Client Data. Creators store information about their clients on the Platform, including: client names, email addresses, phone numbers, mailing addresses, booking details, payment history, and communications. 1.5. creavio write. If your agency gives you a creavio write seat, the creavio write browser extension sends creavio text, as Section 4 and the creavio write privacy policy at creav.io/legal/write-privacy describe: once you have turned on Juno suggestions, the text of a field you click or tab into, put your cursor in with a button or key, paste or drop text into, or type in, including text that was already there or that someone else wrote (in version 1.1.9 and earlier of the extension, only paragraphs you type or edit), and text you select or a prompt you type, when you click Improve or Check originality. With that text it sends the name of the site, such as mail.google.com. If that text contains personal information about other people, it is sent too. creavio also records your seat, your signed-in browsers, and a usage record for each request. A usage record does not include your text.
2. HOW WE USE INFORMATION We use information we collect to: (a) Operate, maintain, and improve the Platform; (b) Process payments and manage subscriptions; (c) Send transactional communications (account confirmations, invoices, booking notifications, contract delivery); (d) Send product updates and marketing communications (with opt-out); (e) Analyze usage patterns to improve features and user experience; (f) Comply with legal obligations and enforce our Terms of Service; (g) Detect, prevent, and address fraud, abuse, and security issues; (h) Measure how creavio's own website is used with Google Analytics 4, after you accept cookies, and, with any separate consent the law requires (Section 3(c)), use that data to inform creavio's advertising, as Section 4, Section 6.4 and Section 8.3 describe.
3. LAWFUL BASIS FOR PROCESSING (GDPR) For users in the European Economic Area (EEA) and United Kingdom, we process personal data on the following legal bases: (a) Contract Performance. Processing necessary to provide you with the Platform services you signed up for. (b) Legitimate Interests. Processing that runs without asking for your consent: the essential cookies listed in Section 2.1 of the Cookie Policy, security monitoring, fraud and abuse prevention, the first-party usage records described in Section 8.2, and improving the Platform based on them, where our interests do not override your rights. You may object to this processing as Section 6.2 describes. (c) Consent. Processing based on your consent, such as Google Analytics 4 on creavio's own website, which runs only after you click "Accept all" on the cookie banner, and marketing communications. Clicking "Accept all" is consent to GA4 analytics. It is not consent to using GA4 data to inform advertising: where the law requires consent for that, creavio asks for it separately first, and does not use your GA4 data to inform advertising until you give it. You may withdraw consent at any time. For GA4, click "Reject non-essential" on the cookie banner or use creav.io/privacy-choices. (d) Legal Obligation. Processing required to comply with applicable laws, regulations, or legal proceedings.
4. INFORMATION SHARING & SUB-PROCESSORS We do not sell personal information. When you choose to run an originality check, you direct us to send the selected text to an outside checking service; under Cal. Civ. Code 1798.140(ad)(2)(A) that is a disclosure you direct, not a sale. Because that service has no contract with us, regulators may treat it as a sale or sharing (11 CCR 7050(e)), so you can opt out at any time by not ticking, or by withdrawing consent in the extension's Settings, which stops all originality checks. We share information with the providers below only as necessary to operate the Platform, and with the writing-checks provider described under "Third parties" below. We engage the following categories of providers, which are sub-processors under our Data Processing Addendum: (a) Cloud infrastructure & hosting; (b) Payment processing; (c) Email and SMS and MMS delivery; (d) AI processing under enterprise or API terms that prohibit training on your data; (e) Search and SEO data (aggregate only, no personal data); (f) Media processing (image, print and video); (g) Analytics; and (h) Social, advertising, and business platforms that you connect (used only when a Creator or authorized Agency connects an account, and limited to publish, manage, and read access for that connected account, and to sending the conversion events the Creator sets up, as Section 8.2 describes). One exception: Meta's Facebook JavaScript SDK loads on app.creav.io only on the Connect card in the social settings of an agency client workspace, so an agency can connect that client's Facebook or Instagram accounts. It loads when that card is shown, before anyone clicks Connect, and Meta may set a Facebook session cookie then, as Section 2.1(l) of the Cookie Policy describes. creavio does not use it to track visitors or for creavio's own advertising; it connects the accounts the agency manages, including to run their ads. It is never on creavio's public website or on Creator sites. Google account connections are described in Section 14. That section does not add Google as a sub-processor. Google Analytics 4 (within category (g)) receives online identifiers including cookie IDs, IP address, browser and device information, pages viewed, and events. creavio uses GA4 for product analytics and may use GA4 data to inform advertising. Under the California Consumer Privacy Act, as amended by the CPRA, that may be "sharing" of personal information for cross-context behavioral advertising. You may opt out of this sharing at creav.io/privacy-choices or with the Global Privacy Control signal, as described in Section 6.4 (Do Not Sell or Share My Personal Information). creavio write and Anthropic (within category (d)). Juno is the AI in creavio write. It runs on Claude, made by Anthropic, our AI provider, used through Anthropic's commercial API. Juno suggestions are off until you turn them on. Once they are on, from version 1.1.10 of the extension, when you click or tab into a text field, click a button or press a key that puts your cursor in one (such as Reply), paste or drop text into one, or pause typing in it, the extension sends creavio the text of that field, one paragraph per request, with the name of the site, such as mail.google.com. That text can include text that was already in the field and text someone else wrote, such as a colleague's notes in a shared record, and any personal information in it. creavio handles that text on behalf of the agency that gave you the seat. In version 1.1.9 and earlier, the extension sends only the paragraphs you typed or edited after you turned Juno suggestions on. From version 1.1.9 of the extension, spelling and grammar underlines on web pages come from Juno suggestions. This includes rich text fields on a Salesforce site you turn on. Improve sends the text you select, or the prompt you type, only when you click. creavio sends the text, and any instruction you type for Improve, but not the site name, to Anthropic only to produce the answer. For Improve, creavio adds your agency's style guide voice and banned words. Anthropic's Commercial Terms of Service say that Anthropic "may not train models on Customer Content from Services". We do not sell this text and do not use it for advertising. See Section 7(g) and the creavio write privacy policy at creav.io/legal/write-privacy. Third parties. We also disclose information to a plagiarism-search and AI-written-text-detection provider for creavio write, which is a third party. Our only such provider is Copyscape (Indigo Stream Technologies Ltd.). Copyscape provides its service to us on its standard terms, and no contract between us contains the terms California law requires of a service provider (Cal. Civ. Code 1798.140(ag)(1)), so it is a third party, not our service provider. It receives the text a creavio write user selects, only when that user clicks Check, and only for the checks the user picks. It does not receive the user's name, email address, or the site the text came from. We tell users not to run either check on text that contains personal information about anyone, but we do not screen or block what they select, so any personal information in checked text is disclosed to this third party. See Section 7(f), Section 10, and the creavio write privacy policy at creav.io/legal/write-privacy. A current, itemized sub-processor list, including each sub-processor's name, location, and processing purpose, is available to customers on request under our Data Processing Addendum by contacting privacy@creav.io. We will notify Creators of material sub-processor changes at least 30 days before they take effect. We may also disclose information when required by law, legal process, or government request, or to protect the rights, safety, or property of creavio, our users, or the public.
5. CREATOR CLIENT DATA 5.1. Creators are the Data Controllers for all client data they collect and store on the Platform (client names, emails, phone numbers, addresses, booking details, contracts, invoices, photos, and other information). 5.2. creavio is the Data Processor, processing client data on behalf of Creators as defined under GDPR Article 28. 5.3. Creators are solely responsible for their own privacy practices with their clients, including obtaining appropriate consent for data collection and use. 5.4. For details on how we process client data on behalf of Creators, see our Data Processing Addendum. 5.5. Agency-Managed Workspaces. Some workspaces on the Platform are operated by an agency on behalf of a brand or business under creavio's Agency tier. Where a workspace is agency-managed, the agency's authorized personnel can access that workspace's data through an audited, revocable session, and the agency, or the brand, or both, not creavio, is the data controller responsible for that data and for the privacy notices and consents owed to the brand's customers and contacts. creavio processes such data only on the agency's instructions. If you are a brand or a brand's customer and have questions about an agency-managed workspace, contact the agency that manages it; you may also reach us at privacy@creav.io.
6. YOUR RIGHTS 6.1. All Users. Regardless of your location, you have the right to: access your personal data, correct inaccurate data, request deletion of your data, request a portable copy of your data (data export), and manage your data through Settings > Data & Privacy in your dashboard. 6.2. EEA and UK Users. In addition, you have the right to: restrict processing of your data, object to processing based on legitimate interests, withdraw consent at any time (without affecting prior processing), and lodge a complaint with your local supervisory authority. 6.3. California Users. Under the California Consumer Privacy Act (CCPA), you have the right to: know what personal information we collect and how it is used, request deletion of your personal information, opt out of the sale or sharing of personal information, and not be discriminated against for exercising your privacy rights. We do not sell personal information. When you choose to run an originality check, you direct us to send the selected text to an outside checking service; under Cal. Civ. Code 1798.140(ad)(2)(A) that is a disclosure you direct, not a sale. Because that service has no contract with us, regulators may treat it as a sale or sharing (11 CCR 7050(e)), so you can opt out at any time by not ticking, or by withdrawing consent in the extension's Settings, which stops all originality checks. Sensitive Personal Information. creavio collects these kinds of sensitive personal information: your account log-in with its password, which you use to sign in. When a Creator or agency uses these features, creavio also processes, on their behalf: tax identification numbers they enter for W-9 forms and vendor records; the bank accounts they connect; the contents of messages and text sent through the Platform; and descriptions of faces in their photos and in a selfie a person uploads. Our AI provider writes each face description from the image, and it may include apparent gender, age range, hair color and skin tone. creavio stores the descriptions with the photos, and stores a numeric version of each in Cloudflare Vectorize, our hosting provider's vector database, to group photos of the same person, which the Creator can name and merge, and to find a person's photos from a selfie that person uploads. Payment card numbers are entered with Stripe, and creavio does not store them. creavio uses and discloses sensitive personal information only for the purposes listed in Cal. Code Regs. tit. 11, section 7027(m), such as providing the service you asked for, keeping accounts secure, and preventing fraud. Face descriptions are used only to group and find photos for the Creator, and not for advertising or to make decisions about anyone. For that reason, California law does not give a right to limit the use of this information, and creavio does not offer a "Limit the Use of My Sensitive Personal Information" link (11 CCR 7014(g)(1)). If creavio ever uses sensitive personal information for another purpose, we will update this Policy and offer that right first.
6.4. DO NOT SELL OR SHARE MY PERSONAL INFORMATION (CALIFORNIA). Under the California Consumer Privacy Act (CCPA) as amended by CPRA, "sharing" personal information includes disclosing it to third parties for cross-context behavioral advertising, even without payment. creavio uses Google Analytics 4 (GA4) for product analytics and may use GA4 data to inform advertising. GA4 receives identifiers (IP address, device information, cookie IDs), so under California law that may be "sharing". California residents have the right to opt out of this sharing.
To opt out: (a) Use the "Your Privacy Choices" link in the footer of creav.io, which opens creav.io/privacy-choices, and choose "Opt out of non-essential cookies", or click "Reject non-essential" on the cookie banner, or (b) enable the Global Privacy Control (GPC) signal in your browser, or (c) email privacy@creav.io with subject line "Do Not Sell or Share." creavio honors GPC signals automatically: GA4 does not run while your browser sends the signal. A Do Not Sell or Share choice and a Global Privacy Control signal also stop originality checks: creavio withdraws originality consent, and a check request that carries the GPC signal is refused before any text is sent.
We do not sell personal information. When you choose to run an originality check, you direct us to send the selected text to an outside checking service; under Cal. Civ. Code 1798.140(ad)(2)(A) that is a disclosure you direct, not a sale. Because that service has no contract with us, regulators may treat it as a sale or sharing (11 CCR 7050(e)), so you can opt out at any time by not ticking, or by withdrawing consent in the extension's Settings, which stops all originality checks. GA4 is the only tool on creavio's own pages that may share personal information for cross-context behavioral advertising. Meta's Facebook JavaScript SDK, which loads on app.creav.io only on the Connect card in the social settings of an agency client workspace to connect Facebook or Instagram accounts the agency manages, is not used to track visitors or for creavio's own advertising, and is never on creavio's public website or on Creator sites, as Section 4(h) describes. If we add another tool that may share personal information for advertising, we will list it in this Policy and in the Cookie Policy, and the same opt-outs will apply. We do not share data with data brokers.
6.5. GLOBAL PRIVACY CONTROL (GPC). If your browser transmits a Global Privacy Control signal (navigator.globalPrivacyControl = true), creavio will treat it as a valid opt-out of the sharing of your personal information for cross-context behavioral advertising, consistent with California law. Google Analytics 4 does not run while your browser sends the signal. Essential cookies (authentication, security) are not affected. The same signal also stops originality checks, as Section 6.4 describes. creavio does not respond to browser Do Not Track (DNT) signals. Use the Global Privacy Control signal or creav.io/privacy-choices instead.
6.6. How to Exercise Your Rights. You may exercise your rights by emailing privacy@creav.io or using the Settings > Data & Privacy section in your dashboard.
7. DATA RETENTION (a) Account Data. Kept until the account is deleted. When you delete your account in your settings, creavio starts deleting its data right away. When our team carries out a deletion request for you, the request is held for 30 days, and after that hold a nightly deletion job deletes the data. (b) Legal Records. DMCA notices, contract signatures, and payment records are retained for 7 years per legal requirements. (c) Email Logs. Retained for 90 days. (d) Analytics Data. Google Analytics 4 keeps user-level and event-level data for the retention period set in our Google Analytics property, which Google lets a standard property set to 2 months or 14 months. Google says data from Google signals is kept for at most 26 months, and for no longer than that setting when the setting is shorter (support.google.com/analytics/answer/7667196). Creator site visitor events are deleted 90 days after they are recorded, and a visitor's profile 180 days after that visitor was last seen. (e) Backups. Purged within 30 days of deletion. (f) creavio write Checks. creavio does not store text sent for plagiarism or AI-written-text checks. Our provider for both checks, Copyscape (Indigo Stream Technologies Ltd.), has told us in writing that it keeps that text for 14 days and then deletes it, that Copyscape staff can access the text during those 14 days, and that it does not use it to improve its service or train algorithms. For the plagiarism check, Copyscape searches the web for the text, or for parts of it, through Google; Copyscape has not told us exactly what it sends to Google. Copyscape has not signed a data processing agreement with us, so do not run either check on text that contains personal information about anyone. See the creavio write privacy policy at creav.io/legal/write-privacy. (g) creavio write Juno suggestions and Improve. creavio does not store the text sent for Juno suggestions or Improve, or the text Juno writes back. The usage record for each request does not include that text and is kept while your agency's creavio account exists, as the creavio write privacy policy describes. Anthropic says it automatically deletes API inputs and outputs within 30 days, except when it must keep them longer to enforce its Usage Policy or to comply with the law, and that it keeps inputs and outputs flagged by its trust and safety systems for up to 2 years. (h) Click, Scan, Usage and Visit Records. The short-link and QR code click and scan records, the link-page click records, the dashboard usage records, the Creator site visit counts and the Creator site page speed reports described in Section 8.2 are kept until the account is deleted, including while it is suspended, and are deleted with the account's other data, as Section 7(a) describes. Clicks on a short link or a link-page link are also deleted when the Creator deletes that link. Dashboard usage records belong to the agency workspace they were recorded in, so they are deleted when that agency's account is deleted, and not when a client workspace they mention is deleted. You can also ask us to delete them at privacy@creav.io.
8. COOKIES & TRACKING 8.1. Essential. The creavio_rt sign-in cookie (HttpOnly, 30 days), short-lived cookies used while you sign in, and the other cookies listed in Section 2.1 of the Cookie Policy. In a normal session your creavio access token is kept only in the page's memory, not in a cookie or in localStorage. When you switch into an agency or open a client workspace, the access token for that workspace is kept in the browser tab's session storage, so a reload keeps you in it, and it is cleared when the tab closes. An invited collaborator's tokens are kept in local storage, as Section 2.2 of the Cookie Policy describes. These are required for the Platform to function. 8.2. First-Party Usage Records. When you use creavio's agency features, signed in, the dashboard records some actions you take, such as opening a client workspace or switching into an agency, as usage events. creavio records them only for agency workspaces, for accounts that have agency features turned on, for agency staff sessions, and for client workspaces an agency has opened, and records nothing for other accounts. Each event is stored with the agency workspace's ID and the email address of the person acting, both taken from the sign-in token, with the event name, the page path without its query string, the client workspace it concerns if any, a few details about the action such as the page it led to or a date range, a random ID for the browser tab kept in session storage, and the time. These records are not anonymous. If you work in an agency's workspace, that agency can see them, including your email address. When you are signed out, nothing is recorded. This does not use cookies, is not controlled by the cookie banner, the opt-out at creav.io/privacy-choices, or the Global Privacy Control signal, and is not sent to Google or used for advertising. We use it to understand and improve how the Platform is used. On a Creator's site, creavio counts visits to each page per day without a cookie or any identifier, and records page speed measurements with the page path and device type. creavio also accepts visitor events from a Creator's site, such as which pages or items a visitor viewed, when the site sends them with a visitor ID of its choosing, and stores each event with the label, value and other details the site sends with it; pages built with creavio's site editor do not send them today, and creavio ignores them when the Creator's adaptive intelligence setting is off. For each visitor ID creavio keeps a profile with the visitor's device type, referring site and visit count. creavio may send those events to Meta or Pinterest as conversion events for a Creator who connects that advertising account, as Section 2.3 of the Cookie Policy describes. When an event includes them, a conversion event may carry the visitor's email address, phone number, first and last name, and, for Meta, city, state, ZIP code and country, each hashed before it is sent; the visitor ID, hashed for Meta and not hashed for Pinterest; the visitor's IP address and browser user agent; Meta's fbp and fbc browser and click identifiers or Pinterest's click identifier; purchase details such as value, currency, order ID, item IDs and number of items, and search text; and, for Meta, the page address. The Creator is responsible for the notice and consent those events need. When someone opens a Creator's creavio short link or scans a Creator's QR code, creavio records the referring site, user agent, country, city, device type, browser, operating system, campaign tags in the link, a code made from the visitor's IP address and user agent to count unique visitors, and the time, and shows these records to the Creator. A click on a link in a Creator's link page records the referring site, user agent and country. These records are kept as Section 7(h) describes. 8.3. Analytics and Advertising Cookies. We use Google Analytics 4 (GA4), which sets the analytics cookies _ga and _ga_<ID>, where <ID> is our GA4 measurement ID. We use GA4 for product analytics and may use GA4 data to inform advertising. GA4 runs only after you accept cookies, and not while your browser sends the Global Privacy Control signal. You may opt out via the consent banner or at creav.io/privacy-choices. This paragraph is only about those cookies on creavio's own website. It is not about Google user data received from a Google API you connect. That data is Section 14, and creavio does not use it to inform advertising on this website. 8.4. How to Control Cookies. You can manage cookies through your browser settings. Disabling essential cookies may prevent you from using the Platform. 8.5. Creator Sites and Short Links. A Creator may add their own analytics or advertising tags to their site on creavio, such as a Google Analytics measurement ID or code the Creator pastes into the site's settings. A Creator may also add retargeting pixels from Meta, Google, TikTok, Snapchat, or LinkedIn to a creavio short link the Creator creates. Those tags may set cookies and may send visitor data to the companies that provide them. The Creator chooses and controls them, and the Creator is responsible for the privacy notice and any consent their visitors need. The Cookie Policy, Section 5, describes this in more detail.
9. DATA SECURITY We implement appropriate technical and organizational measures to protect your data, including: (a) Encryption in transit (TLS) and at rest; (b) Tenant data isolation (all queries scoped to your account); (c) Regular security monitoring and logging; (d) PBKDF2 password hashing with 100,000 iterations; (e) AES-256-GCM encryption for sensitive data such as contract signatures; (f) Role-based access controls and secure file storage.
10. INTERNATIONAL DATA TRANSFERS Except as stated in the next paragraphs, data is processed in the United States and other countries where Cloudflare operates infrastructure. For transfers of personal data from the EEA or United Kingdom, we rely on Standard Contractual Clauses as approved by the European Commission to ensure adequate protection of your data. Exception for creavio write Checks. Text sent for plagiarism or AI-written-text checks goes to Copyscape (Indigo Stream Technologies Ltd.). Copyscape has not told us in which countries it processes that text. Copyscape's terms are governed by the laws of Gibraltar; that is a choice of law, not a statement of where the text is processed. We have no Standard Contractual Clauses or other transfer agreement with Copyscape, so the protections described in the paragraph above do not apply to that text. For a transfer of that text from the EEA or the United Kingdom, we rely on your explicit consent, given when you tick Allow originality checks (GDPR Article 49(1)(a)), after you are shown these words: "It has not told us which countries it processes text in. If that is outside the US, the EU or the UK, there may be no legal finding that the country protects data adequately and no contract safeguards for your text." Do not run either check on text that contains personal information about anyone. Exception for creavio write Juno suggestions and Improve. Text sent for Juno suggestions or Improve goes to Anthropic, our AI provider. Anthropic stores API data in the United States, and it may run the AI model in other countries where it operates. For transfers of that text from the EEA, the United Kingdom or Switzerland, Anthropic's Data Processing Addendum includes the Standard Contractual Clauses and the UK and Swiss addenda.
11. CHILDREN'S PRIVACY creavio is not directed at children under 16. We do not knowingly collect personal data from children under 16. If we discover that we have collected data from a child under 16, we will delete it promptly. If you believe a child has provided us with personal data, please contact privacy@creav.io.
12. CHANGES TO THIS POLICY We may update this Privacy Policy from time to time. When we do, we post the new version here with a new "Last Updated" date. If a change is material, we will give you notice by email or in the Platform before it takes effect, as the law requires. Other changes take effect when posted. Continued use of the Platform after a change takes effect means you accept the updated policy.
14. GOOGLE USER DATA 14.1. Limited Use. creavio's use and transfer of information received from Google APIs to any other app will adhere to the Google API Services User Data Policy, including the Limited Use requirements. The policy is at https://developers.google.com/terms/api-services-user-data-policy. That page was last updated February 15, 2024. It limits use of this data to providing or improving user-facing features that are prominent in the requesting application's user interface. A transfer is allowed only to provide or improve those features with your consent, for security, to comply with applicable law, or as part of a merger, acquisition, or sale of assets after your explicit prior consent. People may not read the data except with your affirmative agreement for the specific data, for security, to comply with applicable law, or when the data is aggregated and used for internal operations. creavio does not sell Google user data. creavio does not transfer it to advertising platforms, data brokers, or information resellers. creavio does not transfer, sell, or use it for serving ads, including retargeting, personalized, or interest-based advertising, except that a Google Ads connection is used only to operate and report on the advertising account you connected, which is the feature you turned on. creavio does not use Google user data from any other Google API to serve ads. creavio does not use Google user data to determine credit-worthiness or for lending. creavio does not use it to train AI models.
14.2. What this section is, and what it does not change. This section describes Google user data creavio accesses when you connect a Google account, how creavio uses it, where it is stored, when it is shared, and how you revoke access. It does not change Section 4, Section 7(f), Section 10, the Data Processing Addendum, or the sub-processors page. Google is not added there as a sub-processor. A Google account you connect is your account. Sending it what you ask creavio to send is your instruction to that account, not creavio hiring Google to process your client database. For the plagiarism check, Copyscape may still search the text through Google, as Section 7(f) already says. That is only the plagiarism check. Section 10 does not describe a Google search. The creavio write privacy policy at creav.io/legal/write-privacy remains the full disclosure for Google Docs, and this section does not change it.
14.3. Google sign-in. If you sign in, create an account, or link Google to an existing account, creavio asks Google only for the scopes openid, email, and profile. creavio does not ask for offline access. creavio receives the name, email address, Google account id, and verified-email flag that Google returns for that sign-in. creavio uses them only to create your account, sign you in, or link Google to an existing account. creavio stores the name, email address, and Google account id as account data for the period in Section 7(a). creavio uses the sign-in token to read that profile and does not store that Google access token. creavio does not store a Google refresh token for sign-in. creavio does not receive your Google password. Revoking creavio at the page in Section 14.11 does not delete the creavio account, and it does not remove the Google account id, the email, or the name. Unlinking Google sign-in in your creavio account settings removes the stored Google account id. Otherwise creavio keeps those for sign-in until you delete the account.
14.4. Google Analytics. creavio has two Google Analytics connections. Both ask for https://www.googleapis.com/auth/analytics.readonly. Neither writes to your Google Analytics property. creavio stores each connection's refresh token encrypted, the Google email on the connection, and the property you select. A short-lived access token may be cached for up to its expiry, at most one hour, so creavio does not request a new one on every call. creavio does not use those reports to advertise on creavio's website and does not sell them.
The reporting connection also asks for openid, email, and profile. creavio receives the accounts and properties your Google account can access, and the reports you open, including standard reports and realtime reports. creavio uses them to show that property's analytics in your account. Disconnecting that reporting connection deletes the connection and the reports creavio stored for it.
The page connection asks for analytics.readonly and openid email. It does not ask for profile. creavio uses it to read a 28-day report for the property you select, by page, of sessions, users, engagement rate, average session duration, and conversions, and to write those numbers onto pages in your account. Disconnecting that page connection deletes the connection. Report numbers creavio has written onto pages in your account are not removed by that disconnect. They remain in your account, and account deletion follows Section 7.
14.5. Search Console. creavio has two Search Console connections. creavio stores each connection's refresh token encrypted, the Google email on the connection, and the property you select. A short-lived access token may be cached for up to its expiry, at most one hour, so creavio does not request a new one on every call.
The read connection asks for openid, email, profile, and https://www.googleapis.com/auth/webmasters.readonly. Reads on that connection use webmasters.readonly on the property you select. creavio receives the sites your Google account can access and the search analytics it requests for that property, including queries, pages, clicks, impressions, click-through rate, and position. creavio uses them to show that site's search performance in your account. Disconnecting that read connection deletes the connection and the reports creavio stored for it.
The sitemap connection asks for https://www.googleapis.com/auth/webmasters and openid email. It does not ask for profile. creavio uses that grant to read search analytics for a property you selected and to write clicks, impressions, click-through rate, and position onto pages in your account. Sitemap submit for a property of yours that is not a hosted creav.io site uses that webmasters scope, through this sitemap connection. Sitemaps for hosted creav.io sites are submitted with creavio's own Google account, not with your grant. You do not have to connect Search Console for creavio to submit a sitemap for a hosted creav.io site. Disconnecting the sitemap connection deletes that connection. Search numbers creavio has written onto pages in your account are not removed by that disconnect. They remain in your account, and account deletion follows Section 7.
14.6. YouTube. creavio uses YouTube API Services. If you use creavio's YouTube features, you agree to the YouTube Terms of Service at https://www.youtube.com/t/terms. Google's privacy policy is at https://policies.google.com/privacy. YouTube Developer Policies section III.A.2 also names that policy at http://www.google.com/policies/privacy.
When you connect a YouTube channel, creavio asks for https://www.googleapis.com/auth/youtube.upload, https://www.googleapis.com/auth/youtube, https://www.googleapis.com/auth/youtube.readonly, and https://www.googleapis.com/auth/yt-analytics.readonly. creavio does not ask for https://www.googleapis.com/auth/youtubepartner. The connection asks Google for offline access, and creavio stores the access token and the refresh token encrypted. A separate revenue consent, after you turn revenue on for a channel you already connected, adds only https://www.googleapis.com/auth/yt-analytics-monetary.readonly. creavio saves that revenue grant only when Google returns the same channel you selected. If Google returns a different channel, creavio does not save the grant.
creavio uses the upload and channel scopes to publish the video you submit and to read the connected channel. On upload, creavio sends the title, the description, the privacy status, the tags, the category id, and selfDeclaredMadeForKids. The title is the one you supply, up to 100 characters. If you do not supply a title, creavio sends your post caption as the title, or the word Untitled when there is no caption. The description is the one you supply, up to 5000 characters. When the post has hashtags, one publish path appends them to the description and also sends them as tags. Tags are at most 30. The privacy status is public, unlisted, or private. If you do not set one of those, creavio sends unlisted. The category id is the one you set, or 22 when you do not set one. selfDeclaredMadeForKids is true only when you explicitly say yes. Otherwise creavio sends false. creavio then sends the video file. creavio reads the channel name, handle, and image. For a video published through creavio, creavio reads viewCount, likeCount, commentCount, and favoriteCount. With the analytics scope, creavio reads a daily report for the connected channel of views, estimatedMinutesWatched, averageViewDuration, and subscribersGained. That report is returned to your account and is not stored as its own table. creavio reads estimatedRevenue, estimatedAdRevenue, and cpm only when you asked for revenue, the separate revenue scope is granted, and a 24 hour notice that the revenue request was denied is not still in effect. After a denial, creavio does not request those three fields again for 24 hours. creavio does not manage content-owner assets or analytics groups.
creavio also calls YouTube with an API key, and not with your YouTube authorization, to search public videos for listening and to read a public subscriber count for a handle you look up.
YouTube API Services Developer Policies sections III.D.2 and III.E.4 (https://developers.google.com/youtube/terms/developer-policies) require an API client to delete stored YouTube data after you revoke access inside the client, to delete stored API data after you revoke access at Google's security settings, and to delete or refresh stored API data on the clocks in section III.E.4. creavio does only what the next paragraphs describe.
If you disconnect YouTube inside creavio, creavio asks Google to revoke the token first. It then clears the access token, the refresh token, the scopes, the channel id, the channel name, the handle, and the image, marks the connection disconnected, and replaces the connection metadata with a record that stored YouTube data is still being removed, before it deletes the other stored YouTube data. It deletes the snapshots, the post metrics, and the daily stats stored for that connection, of every age. It deletes every YouTube mention, every snapshot of a YouTube public subscriber count, and every YouTube influencer-stat row stored for your account, including rows newer than 30 days. It clears the provider response, the provider request id, and the reconciliation state on publish attempts for that connection. It does not clear the HTTP status or the error message on those attempts. If the connection has no post targets and that delete finishes, creavio deletes the connection row. If that row delete fails, or a post target exists, the row stays, with status disconnected, those YouTube fields empty, and that record removed. If the delete of stored YouTube data cannot finish, the connection is still disconnected, the tokens and channel fields above are already cleared, and that record stays. creavio logs the error, and the disconnect answer uses the code youtube_data_delete_incomplete. The daily job finishes that remaining delete the next time it reaches the connection. creavio does not, on that disconnect, delete the post you wrote, the target row, the YouTube video id, the video address, or the upload session address stored on the target. Deleting data stored by creavio does not delete the video or the channel on YouTube. To delete those, use YouTube.
Once each day, at 03:00 UTC, in the scheduled job creavio already runs, creavio checks up to 25 stored YouTube connections, continuing from the last connection it checked. When fewer than 25 remain, the next run starts from the beginning. If a connection still has YouTube data left from a disconnect that could not finish, creavio finishes that delete before it does anything else with that connection, and it does not refresh the token on that run. For each connection it checks that does not have that remaining work, it first deletes or clears stored YouTube API data older than 30 days. That delete does not depend on a successful refresh. It deletes post metrics, snapshots, and daily stats older than 30 days for that connection. A daily stat counts as older than 30 days when its date is before the UTC date of that cutoff. It clears the provider response, the provider request id, and the reconciliation state on publish attempts older than 30 days. It does not clear the HTTP status or the error message. If that aged-row delete cannot finish, creavio still deletes channel fields older than 30 days on that connection, logs the error, and does not refresh that connection on that run. The check continues with the other connections in that run, and the remaining aged rows wait until a later run reaches that connection again. When that aged-row delete finishes, creavio tries to refresh the authorization. A missing refresh token is not a revocation. If the access token is still usable, with an expiry at least 60 seconds ahead, creavio uses that access token. If the access token is missing or expired, creavio logs that the refresh token is missing and does not delete the connection. If Google rejects the refresh as invalid_grant, and no publish job for that connection is locked with a lock that has not expired, creavio deletes that connection's stored YouTube API data in the same way a disconnect does. If Google rejects the refresh as invalid_grant while a publish job is locked and the lock has not expired, creavio does not delete the tokens or the connection. It marks pending publish jobs superseded, leaves the locked job, and runs the full delete the next time the daily job checks that connection after the lock has expired. The 30 day cleanup for that connection has already run. If the refresh is not attempted, including when the Google client settings are missing, creavio logs that and does not delete the connection on that run. If the refresh fails for another reason, including a network error, an HTTP 429, or an HTTP 500, creavio logs that and does not delete the connection on that run. If the channel name, the handle, the image, or a cached YouTube field is older than 30 days, or has no refresh time, creavio deletes those fields when the channel read fails, when YouTube returns a different channel, when the refresh does not succeed, when the refresh token is missing, and when a publish is in progress. The cached fields are the channel id stored in connection metadata, the partner program mark, the revenue denial time, and the metadata refresh time. A channel record refreshed within 30 days stays in place when that read fails. On that 30 day clear, the account id, the tokens, the Google email, and the revenue setting stay. If the refresh succeeds and the channel read matches the connected channel, creavio stores the channel name, the handle, the image, the channel id, and the refresh time. The account id stays. If YouTube returns a different channel, creavio does not store that channel. creavio does not delete the tokens because of age. creavio also checks up to 25 accounts that still have a YouTube mention, a snapshot of a YouTube public subscriber count, or a YouTube influencer-stat row older than 30 days, continuing from the last account it checked, including an account with no YouTube connection. It deletes those aged rows. If one of those deletes cannot finish, creavio logs the error and retries that account on a later run. It does not skip ahead past the account that failed. When a run finishes every account it selected and fewer than 25 such accounts were selected, the next run starts from the beginning. A YouTube handle you typed into a client record or into settings is not deleted by the disconnect or by the daily job.
You can also revoke creavio at https://security.google.com/settings/security/permissions. creavio does not read that page. The daily job is how creavio learns that Google has rejected the grant. The job does not check every YouTube connection every day. Questions or complaints about these YouTube practices: privacy@creav.io.
14.7. Google Business Profile. If you connect Google Business Profile, creavio asks for https://www.googleapis.com/auth/business.manage. creavio reads the Business Profile accounts your Google account can access and stores the first account's name and id on the connection. If you submit a local post, creavio sends that post to a location on an account you connected. The post includes the text you submit, a language code (the one you set, or en when you do not), a topic type (the one you set, or STANDARD when you do not), and a call to action only when you supply one. Posts sent from the social scheduler always use en and STANDARD, and include your caption followed by your hashtags. creavio uses this access to list those accounts, to publish the post and any photo you submit, and to read the view and action counts Google reports for posts creavio published. creavio stores the connection tokens encrypted. Disconnecting the profile asks Google to revoke the token and removes the tokens from the connection. The account name on the connection, and the post record in your account, are not removed by that disconnect. They remain in your account, and account deletion follows Section 7.
14.8. Google Calendar. If you connect Google Calendar, creavio asks for https://www.googleapis.com/auth/calendar.events and https://www.googleapis.com/auth/calendar.readonly. creavio reads busy times on your primary Google calendar. A busy time is a start and an end. That query does not give creavio the event title. creavio stores each busy interval with the label Busy, which creavio writes. It is not the event title from Google. creavio uses busy times so a booking page does not offer a slot that is already busy. When a booking should appear on that calendar, creavio creates an event. The event can include the title, description, start, end, and attendee email supplied for that booking. creavio does not update an existing Google Calendar event. creavio does not delete the Google Calendar event when a booking is removed. creavio stores the connection tokens encrypted, the Google email on the connection, and the calendar id. Disconnecting the calendar deletes that connection and the busy intervals creavio stored for it. The event id for a booking creavio created is not removed by that disconnect. It remains in your account, and account deletion follows Section 7. creavio asks Google to revoke the calendar token only when no other Calendar connection, and no Search Console or Analytics connection made from your website settings, still shares that Google account. That check does not look at YouTube, Business Profile, or agency Search Console and Analytics connections. A revoke can end other creavio connections that use the same Google account, and you can reconnect them. If the Google email on the connection is missing, any other Calendar, Search Console, or Analytics connection on the creavio account blocks the revoke. If that check fails, creavio does not revoke. In those cases creavio still deletes the local calendar connection and the busy intervals.
14.9. Google Ads. If you connect Google Ads, creavio asks for https://www.googleapis.com/auth/adwords. creavio receives the Ads accounts your Google account can access and the campaign reporting it requests for an account you connected, including impressions, clicks, cost, and conversions. If you ask creavio to change a campaign, budget, or similar setting on that account, creavio sends that change only when creavio has turned on live sending to Google Ads. If live sending is not turned on, creavio checks the change and does not send it. If you ask creavio to send a customer list to that account, creavio prepares the list you selected. A person on that list can include an email address, a phone number, or both, that you selected in creavio. creavio hashes each one before any send. If live sending is not turned on, creavio checks the hashed list and does not send it. When live sending is turned on, creavio sends the hashed list. That list is data you selected in creavio. It is not data creavio received from a Google API. creavio uses the Google Ads connection only to operate and report on the account you connected, with your authorization, and that use adheres to the Limited Use requirements in Section 14.1. creavio stores the connection tokens encrypted. Disconnecting Google Ads removes those tokens. Reporting creavio has stored for that account is not removed by that disconnect. It remains in your account, and account deletion follows Section 7. creavio does not use Google Ads data to train AI models and does not move that data to a different advertising platform.
14.10. Google Docs, for creavio write. The creavio write extension can read and edit a Google Doc that is open in your browser. Google's consent screen describes that permission as "See, edit, create, and delete all your Google Docs documents". The extension uses it only to read the one doc open in the Google Docs view while that view is open, and to write a fix only when you click. The Google access token stays in Chrome on your computer and is not sent to creavio. The doc is checked on your computer and is not sent to creavio, except a paragraph you send with Improve this paragraph, which goes to creavio and to Anthropic only when you click, and only to write the rewrite you asked for. That text is not used to train AI models. Juno suggestions never run in the Google Docs view, and nothing about a doc is sent to creavio automatically. docs.google.com is not one of the sites creavio write works on when you install it. If you turn creavio write on there yourself, Juno suggestions work there like on any other site you turn on, and can send the text of text fields on those pages that you click or tab into, put your cursor in with a button or key, paste or drop text into, or type in, such as comments, as Section 4 describes, unless your agency turned Juno suggestions or AI off for Google Docs. Signing out of creavio write disconnects Google. The full statement is the creavio write privacy policy at creav.io/legal/write-privacy.
14.11. How to revoke, and who to contact. You can disconnect a connected Google service inside creavio. You can also revoke creavio's access to your Google account at any time at https://security.google.com/settings/security/permissions. Revoking access on that page does not by itself delete data creavio has already stored. For YouTube, the clocks in Section 14.6 are how stored YouTube API data is deleted after that revoke. For Google sign-in, Section 14.3 says what creavio keeps. For creavio write, disconnect also asks Google to cancel the extension's token, as the creavio write privacy policy describes. Questions or complaints about the practices in this section: privacy@creav.io.