The data we use should have a clear job.

Information we handle

• Account and organization data: name, email address, verified identity, memberships, roles, and product access.
• Commercial data: subscription state, billing customer references, purchases, and AI credit purchases and usage history.
• Product data: the business, live-session, or execution information a customer places in a Zelikore product.
• Support and security data: messages, diagnostics, and information supplied to investigate a request or protect the service.
• Technical records: request, authentication, error, and operational logs needed to run and secure the service.

Google sign-in data

Google sign-in is a standard way to authenticate a Zelikore account. The shared Google sign-in client requests only the basic OpenID Connect scopes openid, email, and profile. When a person chooses this option, Google provides the stable account subject identifier, verified email address, given and family name, display name, profile photo, and managed Workspace domain when Google supplies them.

Zelikore uses those basic identity attributes to authenticate the account, safely connect a verified Google identity to an existing Zelikore identity, populate the account profile, protect sign-in, and administer organization and product access. This shared sign-in client does not request or read Gmail, Drive, Calendar, YouTube, Ads, Merchant, Search Console, or other Google API content.

Basic identity attributes are stored in the Zelikore identity plane and its Cognito service provider. Authorized product workspace directory records may contain the minimum name and email context needed to serve a Zelikore organization, but products do not receive Google access or refresh tokens through this shared client. Zelikore does not sell Google user data or use it for third-party behavioral advertising. Our use of information received from Google APIs follows the Google API Services User Data Policy, including its Limited Use requirements.

A person can revoke Zelikore's Google authorization from their Google Account security controls or ask privacy@zelikore.com about access, export, or deletion. Revoking Google authorization stops future Google sign-in authorization; it does not by itself delete the Zelikore account.

How information is used

We use information to create and protect accounts, authorize product access, deliver the requested product workflows, administer subscriptions and AI-token balances, answer support requests, prevent misuse, diagnose failures, and improve service reliability.

Google sign-in is used only for the basic identity and account purposes described in the Google sign-in data section. Choosing Google sign-in does not by itself authorize Zelikore to read a person's Google product data.

Essential cookies and first-party site analytics

Zelikore also receives first-party analytics from Zelio's public pages and sign-in starts. We record the website source separately and never infer an account's signup origin from missing page events. Zelio's tab identifiers stay separate from the company website's identifiers, and each website provides its own analytics choice.

Signed-in surfaces use essential security and session cookies so an account can remain authenticated and requests can be protected. The public company site uses first-party analytics and the separate advertising measurement described below. Advertising conversion reports are sent by our server; no advertising pixel is loaded in your browser.

By default, our public pages measure page and section views, selected calls to action, and time on a page. Events may include a referring website domain, bounded campaign labels, a broad device and viewport category, browser and operating system category, and approximate country or region. Where local rules permit it, a random tab session ID is created only in memory to connect activity during the current tab visit. In the UK, European Economic Area, Switzerland, and locations we cannot identify, default events are sent without a session ID and retained as aggregate counts. We do not create a persistent visitor ID by default. Analytics events exclude form entries, email addresses, private page paths, URL query strings or fragments, and browser fingerprints. We do not store raw IP addresses in site analytics.

You can turn site analytics off here or from the footer. We also honor Global Privacy Control and Do Not Track signals. If you expressly allow linked visits below, we store a random visitor ID in this browser so visits can be connected over time. You can return to tab analytics or opt out at any time, which removes that ID. Linked visits may include verified interest or beta milestones, without account details or verification tokens. Tab journeys expire after seven days where permitted, and linked visits expire after 90 days. First-party site analytics records are kept separate from advertising conversion reports. We do not sell these analytics records.

Zelikore stores company-product interest, verified email subscriptions, beta applications, optional interest choices, industry and workflow answers, and notification preferences independently of its products. We use this information to review beta requests and send the notifications you request. We retain bounded campaign identifiers supplied with a request to understand which advertising brings interested visitors. We do not put email addresses or workflow answers into tracking URLs or send these submissions to Zelio. Verification requests expire after 24 hours and are removed after their short recovery window. Confirmed records are retained while needed for your request and notification preferences. You can unsubscribe through the private link in our emails without creating an account, or contact privacy@zelikore.com to request deletion. AWS hosts the records and delivers verification, beta and launch emails. Access is limited to authorized Zelikore operators. Email-only signup does not create a login account.

Advertising measurement and your privacy choices

When permitted, we send OpenAI an ad-click reference provided in an advertising link, a conversion action and its timestamp to measure our ads. Actions include public landing page views, starting or completing a sample business demo, and verified interest or beta milestones, and verified account registration. Demo actions may include the sample business category. These reports do not contain your email address, name, form answers, customer data, or private confirmation URL.

Advertising measurement is allowed by default for visitors whose location is identified as the United States. Elsewhere, including locations we cannot identify, it stays off unless you explicitly allow it here. We honor Global Privacy Control and Do Not Track. Turning site analytics off also stops advertising measurement. Your advertising choice is separate from permission to link first-party analytics visits.

Where measurement is allowed, a cookie that browser scripts cannot read refers to a server-held ad-click reference for up to 30 days. We store only your advertising choice in browser storage. Choosing to opt out stops future conversion reports and clears the cookie and its active reference; it does not retract reports already sent to OpenAI. You can return here through Your privacy choices in the footer at any time.

A separate first-party opt-out cookie records only that advertising measurement is denied, lasts up to one year, and helps apply your choice while pages change. It does not contain an ad-click reference or a visitor identifier.

Service providers and connected services

We use infrastructure and specialist providers to deliver the service, including AWS for hosting, Google when a person chooses Google identity, and Stripe when paid billing is used. A product may also connect to a third-party service at a customer's direction. OpenAI receives permitted advertising conversion reports as described above. We share only the information needed for that provider or connection to perform its role.

For a verified beta request from a custom email domain, we may review publicly accessible pages on that domain to learn what the business does. Limited page excerpts may be sent to OpenAI for a company summary. We do not include the applicant's email address, name, or form answers in that request. We reuse a previous domain summary where one exists, mark automated findings as unverified, and have an operator review them before using them to prepare beta access.

Information may also be disclosed when required by law, to protect users or the service, or as part of a company transaction subject to appropriate handling of the information. We do not sell personal information. You can opt out of sharing advertising conversion reports using the advertising measurement choices above.

Access, correction, and deletion

Account and organization administrators can manage memberships and access from the Zelikore account surface. Zelikore coordinates verified export, organization-closure, and account-deletion requests, while each Zelikore product exports or deletes the product-domain records it owns. Access is disabled before destructive deletion proceeds.

To ask about access, correction, export, or deletion, email privacy@zelikore.com. We may need to verify identity and organization authority before fulfilling a request. A legal hold, active dispute, security investigation, or recordkeeping duty can delay deletion; we will identify that exception and the next review step in the response.

Retention and protected backups

OAuth login transactions expire within minutes. Browser sessions have an eight-hour idle limit and a 30-day absolute limit, and server-held refresh credentials are erased through the revocation workflow. Customer webhook delivery metadata is retained for 90 days. Webhook receipts, integration audit records, and mutation-id records are retained for up to 400 days so retries cannot duplicate charges, access grants, identity correlations, or token movements. Destination response bodies are not retained.

Active account, subscription, entitlement, token-ledger, audit, and product records are retained while needed to provide the service and resolve customer or security issues. Billing and audit records may be retained longer when required for accounting, fraud prevention, a legal hold, or another legal duty. Deletion removes records from active systems first; encrypted backups then age out under their bounded backup lifecycle and are not restored to ordinary service after a verified deletion.