Last updated: 2026-06-12
This Privacy Policy explains how Epinova AB ("we", "us", or "our") processes information in connection with Proxima AI Assistant ("Add-on").
Proxima AI Assistant is an add-on for Optimizely CMS that helps editors and marketers create, optimize, and manage content faster. It supports content generation, metadata suggestions, alt text generation, translation, SEO improvements, editorial automation, and related AI-assisted workflows.
The Add-on may integrate with Google Search Console, Google Analytics, and Google Ads to provide insights that help improve content quality, accessibility, SEO, advertising relevance, and editorial efficiency.
1.Customer-Hosted Add-on
Proxima AI Assistant is installed in the customer's own Optimizely CMS environment.
The customer controls:
- The CMS installation
- The hosting environment
- The Google service account used by the Add-on
- User access inside the CMS
- The content and data processed by the Add-on
- The AI service configuration used by the Add-on
We do not host the customer's CMS as part of Proxima AI Assistant unless a separate hosting or service agreement says otherwise.
2. Customer-Owned Google Service Account
Proxima AI Assistant uses a Google service account created, owned, and configured by the customer.
The customer is responsible for:
- Creating and managing the Google service account
- Granting the service account access to Google Search Console, Google Analytics, or Google Ads
- Limiting permissions to the required scope
- Protecting, rotating, or revoking service account credentials when needed
- Ensuring that the service account is used in compliance with Google's policies and the customer's internal policies
The Add-on can only access Google data that the customer has made available to the service account.
3. Google Services Used by the Add-on
Depending on which features are enabled by the customer, Proxima AI Assistant may retrieve data from the following Google services.
The Add-on may retrieve data such as:
- Google Search Console site, page, query, click, impression, position, and click-through rate data
- Google Analytics account, property, data stream, page views.
- Google Ads keyword, spend, click, impression, cost, conversion, bid range.
4. Data Storage
Proxima AI Assistant is designed to process data inside the customer's Optimizely CMS environment and stores integration data inside the customer's CMS database.
Google data retrieved by the Add-on, including data from Google Search Console, Google Analytics, and Google Ads, may be stored in the customer's CMS database to provide the requested Add-on features, improve performance, support reporting, avoid repeated API requests, and enable editorial workflows inside Optimizely CMS.
This may include data such as:
- Google Search Console site, page, query, click, impression, position, and click-through rate data
- Google Analytics account, property, data stream, page views.
- Google Ads keyword, spend, click, impression, cost, conversion, bid range.
The customer's CMS may also store configuration data required for the Add-on to function, such as:
- Service account credential configuration or references
- Connected Google Search Console site property identifiers
- Connected Google Analytics account, property, and data stream identifiers
- Connected Google Ads account identifiers
- AI service connector settings
- Add-on settings
- Logs used for troubleshooting, auditing, or security
We do not store customer content or Google data from Google Search Console, Google Analytics, or Google Ads on our own servers or systems.
We may store limited account and usage data on our own systems to operate, secure, and manage Proxima AI Assistant and Proxima AI Service. This may include:
- User email address or username
- AI token usage
- License or subscription information
- Usage limits and quota information
- Request timestamps
This account and usage data is not Google Search Console data, Google Analytics data, Google Ads data, or customer CMS content. It is used only to provide the service, track usage, enforce usage limits, support billing or licensing, and operate Proxima AI Assistant and Proxima AI Service.
The customer's CMS may also temporarily cache Google API responses for performance, reliability, rate-limit handling, or troubleshooting, depending on the Add-on configuration.
Any data stored inside the customer's CMS environment or CMS database is controlled by the customer.
5. How Proxima AI Assistant Uses Data
Proxima AI Assistant uses data only to provide features requested by the customer or the customer's authorized CMS users.
This may include:
- Generating or improving page content
- Generating metadata such as titles and descriptions
- Suggesting SEO improvements
- Suggesting target keywords
- Automating image alt text
- Supporting translations
- Improving accessibility and consistency
- Displaying website performance insights
- Showing analytics and advertising metrics inside Optimizely CMS
- Generating or improving ad copy suggestions
- Supporting editorial workflows and content optimization
- Troubleshooting technical issues
The Add-on processes Google data only within the customer's Optimizely CMS environment and only for the features configured and requested by the customer.
We do not have direct access to the customer's Google Search Console data, Google Analytics data, Google Ads data, or CMS content.
6. AI Processing Options
Proxima AI Assistant supports different AI processing options. The customer controls which option is configured and used.
Proxima AI Service
When a customer or authorized CMS user requests an AI-assisted action, the Add-on may send selected content and related data from the customer's Optimizely CMS environment to Proxima AI Service.
This may include:
- Page content
- Page metadata
- Image information used for alt text generation
- Keywords
- Editorial instructions
- Language and culture information
- Other information included by the customer or required to complete the requested AI task
Google data from Google Search Console, Google Analytics, or Google Ads is not sent to Proxima AI Service unless it is included in the content, context, or instructions requested by the customer for the specific AI-assisted action.
Proxima AI Service does not store customer content or Google data. It acts as a pass-through service that sends the requested content and context to the configured AI service provider in order to generate the requested AI output.
Data sent through Proxima AI Service is used only to process the customer's request and return the AI-generated result.
Processing and retention by the configured AI service provider is governed by the applicable terms for that provider and the relevant agreement under which the provider is used.
Direct AI Service Connector
As an alternative to Proxima AI Service, the customer may configure a service connector that connects directly to the customer's selected AI provider, such as Azure AI or OpenAI.
When a direct AI service connector is used:
- The customer's CMS sends selected content and related data directly to the configured AI provider.
- The customer controls the AI provider configuration, credentials, endpoint, and access permissions.
- Google data is sent to the configured AI provider only if it is included in the content, context, or instructions requested by the customer for the specific AI-assisted action.
- Proxima AI Service is not used for that AI request unless the customer has separately configured it.
The customer is responsible for reviewing the privacy, security, data retention, and data processing terms of the selected AI provider.
7. AI Output
AI-generated output may include text, metadata, translations, alt texts, summaries, SEO suggestions, or keyword suggestions.
AI-generated output may contain inaccuracies, omissions, or unsuitable wording. The customer and authorized CMS users are responsible for reviewing and approving AI-generated output before publishing or using it for business purposes.
8. Access by Us
We do not have direct access to the customer's CMS content, Google Search Console data, Google Analytics data, or Google Ads data.
We may access limited information only when necessary to:
- Provide technical support requested by the customer
- Investigate errors or security issues
- Comply with legal obligations
Such limited technical information may include logs, configuration details, error messages, or other information provided by the customer for support or troubleshooting.
Any such access is limited to what is necessary for the relevant purpose.
9. Security
Proxima AI Assistant relies on the customer's Optimizely CMS environment and infrastructure for storage, access control, and credential protection.
Customers should:
- Store service account credentials securely
- Restrict CMS administrator access
- Use least-privilege permissions for the Google service account
- Protect AI service connector credentials
- Rotate credentials when required
- Remove credentials when the Add-on is no longer used
- Keep Optimizely CMS and the Add-on updated
- Use secure connections when communicating with Google APIs, Proxima AI Service, Azure AI, OpenAI, or other external AI services
10. Data Retention
Because Proxima AI Assistant is installed in the customer's Optimizely CMS environment, the customer controls the retention of data stored in the CMS and the customer's CMS database.
We do not store customer content or Google data from Google Search Console, Google Analytics, or Google Ads on our own servers or systems.
Data sent to Proxima AI Service is not stored by Proxima AI Service. Proxima AI Service processes the request transiently by passing the selected content and context to the configured AI service provider and returning the generated result to the customer's CMS.
Retention by the configured AI service provider used through Proxima AI Service is governed by the applicable provider terms and the relevant agreement under which the provider is used.
We may retain limited account and usage data, such as CMS user email address or username, token usage, license or subscription information, usage limits, request timestamps.
For direct AI service connector usage, data retention by Azure AI, OpenAI, or another configured AI provider is governed by the customer's agreement with that provider.
11. Customer Responsibilities
The customer is responsible for:
- Ensuring they have the right to connect Google Search Console, Google Analytics, and Google Ads accounts to Proxima AI Assistant
- Managing Google service account permissions
- Configuring the Add-on appropriately
- Choosing whether to use Proxima AI Service or a direct AI service connector
- Managing Azure AI, OpenAI, or other AI provider credentials and configuration, where applicable
- Controlling access to Optimizely CMS
- Reviewing AI-generated content before use
- Ensuring their use of the Add-on complies with applicable laws, Google policies, AI provider terms, and internal requirements
- Updating their own privacy policy where required
12. Contact Us
If you have questions about this Privacy Policy or how Proxima AI Assistant processes data, contact us at:
Epinova AB
Email: info@epinova.se