Privacy Policy

Last updated: October 27, 2026

Polaris is a product of Orka Growth S.R.L. (CUIT 30-71739101-9), with its registered address at Gorostiaga 2097, Ciudad Autónoma de Buenos Aires, Argentina ("Orka"). This privacy policy explains how Polaris collects, uses, and protects information when organizations use the Polaris platform.

Information we collect and how we use it

Polaris processes account information such as names and email addresses, information needed to secure login, workspace activity, and authorized marketing, advertising, analytics, and commerce data made available through customer-selected integrations. Passwords are never stored in plaintext, and password reset tokens are stored only as a SHA-256 hash.

We use this information to provide the Polaris service, operate dashboards and reports, generate AI-powered marketing insights, support authorized users, improve reliability, and protect the platform from misuse. Customer data is only available to authenticated users who have authorization for the relevant workspace.

Cookies

We use an essential cookie to keep users signed in. With the visitor's consent, Polaris also loads Google Tag Manager, which can set analytics and advertising measurement cookies; these tags load only after the visitor accepts them in the cookie banner.

Roles, legal bases, and international transfers

Orka is the controller of Polaris users' account information. For the data a customer connects or uploads to its workspace, the customer is the controller and Orka processes that data on its behalf and under its instructions, as a processor; customers can request a data processing agreement. We process personal data to perform our contract, for our legitimate interest in securing and improving the service, to comply with legal obligations, and with consent for measurement cookies. The providers listed below process data mainly in the United States, under each provider's data processing terms. Polaris does not make decisions about individuals that produce legal or similarly significant effects. If a security incident affects personal data, we notify the affected customers without undue delay and, where the law requires it, the competent authority and the affected people.

Your rights

Users can request access, correction, deletion, objection, blocking, portability, and withdrawal of consent by writing to [email protected]; we answer within 30 calendar days. Users in Chile can also file a complaint with the Agencia de Protección de Datos Personales.

Google API Services User Data

Polaris's use of information received from Google APIs adheres to the Google API Services User Data Policy, including the Limited Use requirements.

The Google Sheets add-on requests the following permissions and uses them only as described:

See, edit, create, and delete only the specific Google Sheets spreadsheet you use with this application (spreadsheets.currentonly): to write the results of the queries you run into the open spreadsheet. The add-on does not access any other file in your Drive.
Connect to an external service (script.external_request): to send your query to Polaris servers and receive the requested data.
See your primary email address (userinfo.email, openid): to identify you against your Polaris account and determine which workspaces you can access.
Display the sidebar (script.container.ui): to render the add-on's interface inside Google Sheets.

When you connect a Google account under Settings → Integrations → Google Workspace, Polaris requests only the permissions you approve on Google's consent screen and uses them only as described:

See, edit, create, and delete only the specific Google Drive files you use with this app (drive.file): to save the presentations, documents, and spreadsheets you export from Polaris into your Drive as Google Slides, Docs, and Sheets. Polaris cannot see any other file in your Drive.
View and edit events on calendars you own (calendar.events.owned): to show upcoming events on your primary calendar and create the events you ask for and confirm. Older connections may retain a previously granted calendar.events permission; new connections request the narrower owned-calendar permission.
Send email on your behalf (gmail.send): to send the emails you ask for and confirm. Polaris cannot read your mailbox.
See your Google Account email address (openid, email): to show which Google account is connected.

For the advertising, analytics, BigQuery, Google Sheets, and Merchant Center features you connect, Polaris uses these permissions:

Access your Google Ads accounts (adwords): to discover authorized advertising accounts, select a reporting account, and read campaign performance such as cost, clicks, and impressions. The native integration provides reporting; it does not change Google Ads budgets or create campaigns or ads. Google Ads does not provide a separate read-only OAuth scope.
See and download your Google Analytics data (analytics.readonly): to discover accessible GA4 properties, select a property, and read traffic and engagement reports. Polaris does not use this integration to edit Analytics settings.
View your data in Google BigQuery (bigquery.readonly): to discover accessible projects, datasets, and tables, read schemas, and execute read-only SELECT queries on the tables you select using jobs.query. These queries provide Analytics dashboards, reports, filters, custom fields, and assistant analysis. Polaris does not edit or delete source tables. Older connections may retain a previously granted bigquery permission; new connections request read-only access.
Read the Google Sheets files you choose (drive.file): you explicitly select spreadsheets using Google Picker and enable the tabs you want to use in Polaris. Polaris reads their headers and cell values to build dashboards, reports, and assistant analysis. This source integration does not edit your spreadsheets or request access to all files in Drive. Only the connection owner manages the selection; authorized members of the workspace can query enabled tabs.
Manage your Merchant Center accounts (content): to discover authorized accounts and read their products, data sources, issues, and performance. Users can import products into Catalog Studio. After the user approves images and chooses Publish, Polaris creates or updates its supplemental data source, links it through the selected primary source's rules, and submits images for the original product identifiers. Google processes these changes asynchronously; Polaris does not replace the primary source.
Identify the connected Google account (openid, userinfo.email, and, where requested by the connection, userinfo.profile): to identify the authorizing Google account and show its identity in Polaris.

Google Workspace connections are personal: only the Polaris user who connected an account can use its Drive, Calendar, and email capabilities. For native Google Ads, GA4, BigQuery, and Merchant Center connections, only the user who authorized the connection can browse the available accounts or tables, change the selection, reconnect, or disconnect. Authorized members of the same workspace can view the connections and use only the accounts, properties, and tables already enabled by the connection owner. Analytics queries require the corresponding Analytics access, and Merchant publishing requires Catalog Studio permissions and an enabled account for the selected destination. Google credentials are never exposed to other workspace users. Existing Google Sheets add-on reporting connections are workspace connections and are distinct from these native Google connections.

Connected Google access credentials are encrypted at rest and never exposed to other users. Disconnecting a Google integration in Polaris deletes its stored connection record and credentials, together with any enabled-resource selections attached to that connection, and stops its use for new API requests. It does not revoke the app's authorization at Google, because doing so could affect other Polaris integrations using the same Google OAuth client. Disconnecting does not automatically delete imported catalogs, saved reports, conversations, exports, or data already shared. The retention and deletion options are explained below. You can revoke Polaris's Google authorization at any time from your Google Account permissions.

Data obtained from Google APIs is not sold or used for unrelated advertising and is not used to develop, improve or train generalized AI models. Human access occurs only with your explicit consent, as necessary to investigate abuse or security issues, to comply with applicable law, or for internal operations on aggregated and anonymized data as permitted by Google's Limited Use requirements.

We share Google user data only to provide the user-facing features you authorize, for security, or as required by law. The recipients and purposes are:

Hosting and storage providers: Replit, Neon, Google Cloud, and Vercel process the account information, configurations, query results, files, and conversation content needed to host Polaris, store your work, and operate its assistant.
AI service providers: when you request assistant analysis, insights, or creative generation, relevant prompts, selected data, query results, or product images may be processed by Google AI, FAL.ai, Anthropic, OpenAI, or Vercel's AI Gateway and agent infrastructure, depending on the feature. Vercel AI Gateway forwards assistant requests to the inference service configured for the model and routing. Configured routes include Anthropic, Google Cloud Vertex AI, Amazon Web Services Bedrock, Baseten, Fireworks AI, Particle, DigitalOcean, and Together AI. A model's developer is not necessarily the service that hosts inference. This processing provides your requested output; Polaris does not use Google API data to train generalized AI models.
Account communication providers: Freshworks processes account contact information, such as your name and email address, for account communications. It does not receive access to your Gmail mailbox through the Gmail integration.
Recipients and destinations you choose: enabled Google account or table data can be viewed by authorized members of your workspace. Reports, exported files, email contents, calendar invitations, and product images are disclosed to the recipients, connected platforms, or publication destinations you select. Published feed links and product image URLs may be accessible to anyone who has the link.
Legal and security disclosures: information may be disclosed when necessary to comply with applicable law or investigate abuse or security incidents, consistent with Google's User Data Policy.

Google OAuth credentials are used server-side to call Google APIs. When the connection owner opens Google Picker, a short-lived access token is provided to that owner's browser solely to select files through Google's official Picker. Refresh tokens remain on the server; credentials are not provided to AI models or other workspace users. These disclosures do not authorize selling Google user data, unrelated advertising, or generalized model training.

Data retention and deletion

We retain account information while your account is active and as needed to provide the service. Google user data is retained according to its purpose, rather than being deleted automatically when you disconnect an integration:

Connection credentials and selections: encrypted refresh tokens and, where applicable, enabled-resource selections are retained while the connection exists. Disconnecting removes the connection record, its credentials, and those attached selections. Revoking access in your Google Account prevents further authorized API access but is not a request to erase previously saved Polaris content.
Query results and metadata: analytics results and field metadata may be cached in memory or our database for the feature's configured cache period. Expired cache entries are no longer used as current results; cache expiration does not mean every stored copy is physically erased immediately.
Saved work: imported product catalogs and attributes, generated images, dashboard configurations, saved reports, conversation history, and query-result export files may remain in our database or object storage to let you return to your work. They are retained while kept in your account or workspace, unless you remove them or request deletion. Temporary links expiring does not by itself delete the underlying file.
Records outside Polaris: exported Drive files, sent Gmail messages, Calendar events, and published product updates remain in Google or the destination service until you manage or delete them there. Disconnecting Polaris does not remove these records or copies received by other people.

You can remove saved items using the controls available in the relevant feature. To request deletion of Google user data held by Polaris, including retained files, caches, and conversation data, or to close your account, email [email protected]. Identify your Polaris account, workspace, and the integration or data to remove; do not send passwords or OAuth tokens. We verify your authority over the requested data before carrying out deletion. Deleting shared workspace data requires authorization for that workspace.

Some records may need to be retained for legal obligations, fraud prevention, or security. Where this applies to a deletion request, we explain the exception and restrict use of the retained records to that purpose. Removing data through a feature can stop its display before all associated storage copies have been removed; a deletion request can include those retained copies.

Data protection mechanisms

We protect Google user data and other sensitive information using the following measures:

HTTPS/TLS protects data in transit between your browser, Polaris, and the Google API endpoints.
Stored Google OAuth refresh tokens are encrypted with AES-256-GCM. Encryption keys are provided through server-side secret configuration and are not embedded in the browser application.
Passwords for Polaris accounts are hashed with bcrypt rather than stored in plaintext.
Server-side authentication, workspace access checks, connection ownership checks, and enabled-resource checks restrict who can retrieve Google data or manage its connection.
Assistant query-result files use private object-storage access controls; browser downloads require authorization and assistant download links are time-limited. This is distinct from feed or media links you choose to publish.
Google OAuth credentials are kept out of ordinary integration responses and redacted from assistant streams before they reach the browser.

These protections apply to sensitive Google data such as account identifiers, analytics results, calendar information, and the email contents processed for an authorized send. No transmission or storage system can guarantee absolute security.

Contact

Orka Growth S.R.L., CUIT 30-71739101-9, Gorostiaga 2097, Ciudad Autónoma de Buenos Aires, Argentina. For questions about this policy or how Polaris handles information, contact [email protected]. The plain-text contact address is [email protected].