Skip to content
Zinley
BlogDocumentationPricing
Sign In

Privacy Policy

Last updated: October 26, 2026

The English version is the authoritative privacy policy.

This Privacy Policy explains how Zinley ("Zinley," "we," "us," or "our") collects, uses, and protects your information when you use Zinley.

For questions about this policy, contact us at [email protected].

We believe you should understand how Zinley processes your data and which controls are available to you. This policy applies to Zinley's hosted services across the plans and features we offer.

Information We Collect

We collect information necessary to provide and improve Zinley's services. The following describes each category of data we collect and its purpose:

Account Information

Email address, name, and authentication credentials collected during registration. This information is required to provide account access and maintain account security.

Device and Platform Information

Device identifiers, operating system information, device capabilities, and connected platform details (messaging apps, integrations). This information enables Zinley to function across your devices and connected platforms.

Inputs and Outputs

Your conversations, commands, files, and requests to Zinley ("Inputs"), and the responses and actions Zinley generates ("Outputs"). We process these to provide requested features and retain conversation history so Zinley can maintain context. Limited request and response content is also stored in restricted operational logs for reliability, debugging, safety, support, and security. Authorized personnel may access that information for those purposes or when required by law.

Usage Data

Feature usage, performance metrics, error logs, and interaction patterns. This data is used to improve the service and resolve technical issues.

Automatic Collection

We automatically collect device and connection information (IP address, device type, browser data), browsing patterns, and log files. This data supports service operation, security monitoring, and performance optimization.

Feedback and Reports

When you submit feedback, bug reports, or rate responses, we collect that information and any conversation context you choose to attach so we can investigate the issue.

How We Use Your Information

We use your information for the following purposes:

Service Delivery

  • Process AI requests, make calls, access files, and run tasks on your behalf
  • Maintain persistent memory to learn your preferences and maintain continuity across sessions
  • Synchronize data and settings across your devices and connected platforms
  • Deliver Zinley through supported web, desktop, and connected communication channels
  • Maintain account security and authentication

Service Improvement

  • Analyze usage patterns to improve existing features
  • Monitor system performance and reliability
  • Develop new features
  • Log errors, performance metrics, and operational data to diagnose issues and improve the system

Service improvement activities do not use the contents of Gmail messages, Google Drive files, Google Docs, Google Sheets, Google Slides, Google Calendar events, or other Google user data obtained through Google APIs.

Safety and Compliance

  • Enforce our Terms of Service, including their Acceptable Use provisions
  • Prevent fraud, abuse, and security threats
  • Investigate policy violations and resolve disputes
  • Comply with legal obligations

Communications

  • Send important service updates and security notifications
  • Provide customer support and technical assistance
  • Respond to your inquiries and feedback

AI Providers and Model Training

Zinley does not train any model on customer content. To provide AI features, we send the information needed for a request to third-party model, inference, search, and routing providers. The provider, endpoint, and region can depend on the model and feature in use.

What This Means

  • We send model traffic only to enterprise API endpoints whose terms exclude customer content from provider training, and we do not enrol those accounts in any data-sharing or model-improvement program
  • Data you connect from Google Workspace is additionally subject to the Limited Use restrictions described under Google User Data below, which prohibit its use for training any generalized AI or ML model
  • Provider retention and data-use terms vary by endpoint and may change when routing changes
  • Some request and response content is retained in restricted operational logs for a limited period
  • Authorized access may occur for support, safety, abuse prevention, security investigations, service reliability, or legal obligations

Safety and Support Review

Content flagged by automated safety systems, submitted with a support request, or needed for a security investigation may be reviewed by authorized personnel. Access is limited to the purpose of that review.

Data Sharing and Disclosure

We do not sell your personal data. We may share information only in the following limited circumstances:

Service Providers

Depending on the features you use, providers may include Google Cloud and Firebase for hosting, authentication, and storage; Portkey and model or inference providers for AI routing and processing; Perplexity and similar services for search; Sentry for diagnostics; Twilio for phone features; SendGrid for email delivery and inbound routing; and Stripe for billing. Providers receive only the information needed for their role, subject to their applicable terms and our agreements. See the Security page for a current summary of primary providers.

Affiliates

We may share data with our affiliates and related entities, who are bound by this Privacy Policy.

Third-Party Integrations

If you connect third-party applications to Zinley, those services will receive the data necessary to provide the integration. Their use of your data is governed by their own privacy policies.

Legal Requirements

We may disclose information if required by law, court order, or government request, or to protect our rights, property, or safety, or that of our users or the public.

Business Transfers

If Zinley is involved in a merger, acquisition, or sale of assets, your information may be transferred as part of that transaction. We will notify you of any such change and your options regarding your data.

Google User Data

Zinley accesses Google services only when you explicitly connect an account from Settings. Each Google service is a separate connection with its own consent screen and its own token. Connecting one service never grants access to another.

Scopes We Request, and Why

  • Gmail (gmail.readonly, gmail.send). We read the messages you ask Zinley to search, summarize, or reply to, and send email on your behalf when you ask it to. A narrower scope is not available: gmail.metadata returns no message body, so it cannot support summarizing or drafting a reply.
  • Google Calendar (calendar.events, calendar.calendarlist.readonly, calendar.freebusy). We create, update, and delete the events you ask for, read the calendars on your list to know which ones to check, and read your free/busy windows to find a time. We do not request the full calendar scope: Zinley never creates or deletes a calendar and never changes calendar sharing permissions.
  • Google Meet (calendar.events). A Meet link is conferencing data attached to a calendar event, so this reuses the Calendar event permission and requests nothing further.

Zinley does not request any Google Drive, Sheets, Docs, Slides or BigQuery permission. It cannot see your Drive.

Each connection is separate and requests only the scopes listed above for that service; Google's consent screen shows exactly what is granted.

How We Use Google Data

Data retrieved from Google APIs is accessed and used only with your explicit consent and only to provide the user-facing feature or action you request. For example, this may include reading or searching your Gmail messages, sending an email you approved, and reading or managing your calendars and events. Google user data is:

  • never used for advertising, profiling, analytics, or developing unrelated features
  • never used, transferred, or sold by Zinley or by any provider we use to create, train, or improve any foundational or generalized artificial intelligence or machine learning model, whether in raw, aggregated, anonymized, or derived form
  • never sold or rented to anyone
  • transferred to contracted service providers only as necessary to complete the feature or action you explicitly request, and never for their own purposes

Retention

We store OAuth access and refresh tokens for each connected service in hosted storage protected by our infrastructure provider. Content fetched from Google APIs may become part of a saved conversation or limited operational log. Deleting a conversation moves it to Trash for up to 30 days unless you permanently delete it sooner. Disconnecting a service disables the connection and clears the stored access and refresh token values.

How to Revoke Access

You can disconnect any Google service from Settings in Zinley at any time. This erases the access and refresh tokens we hold and stops all further access.

Disconnecting in Zinley does not by itself remove the grant recorded on your Google Account. To revoke it there as well, open myaccount.google.com/permissions, select Zinley, and choose Remove Access. We recommend doing both.

Limited Use

Zinley's use and transfer of information received from Google APIs to any other app adheres to the Google API Services User Data Policy, including the Limited Use requirements. Google user data is used only to provide or improve user-facing features that are visible and prominent in Zinley and that you explicitly request or authorize.

Limited Use and AI Models

Zinley uses third-party AI models to carry out the actions you ask for. Google Workspace user data, whether raw, aggregated, anonymized, or derived, is never used, transferred, or sold to develop, train, improve, fine-tune, or evaluate any foundational or generalized artificial intelligence or machine learning model, whether ours or a provider's.

Workspace content reaches a model only as the input to the single request you asked for, and only through providers that are contractually bound not to train on it. We route model traffic through enterprise API endpoints whose terms exclude customer content from provider training by default, and we do not opt in to any data-sharing or model-improvement program on those accounts. Zinley trains no model of its own on any customer content.

Our current list of AI providers

Health Data

The Zinley mobile app can read Apple Health (HealthKit) on iPhone or Health Connect on Android. Nothing is read until you turn on Health sharing in the app and allow it in your phone's Health permissions. You can turn it off at any time.

What We Read

Depending on what you allow, Zinley reads activity (steps, distance, active energy, exercise, stand hours, flights climbed, time in daylight), workouts, sleep, heart rate, heart rate variability, breathing rate, blood oxygen, VO2 max, blood pressure, blood glucose, body temperature and wrist temperature, body measurements (weight, body fat), mindful minutes, and nutrition (calories, protein, water, caffeine, alcohol). Menstrual cycle data is read only if you turn on cycle tracking separately. Zinley only reads from Health. It never writes to Apple Health or Health Connect.

What Leaves Your Phone

Your phone sends Zinley's servers daily totals for each day, plus steps per hour for the last 8 days. It does not send the individual raw samples stored in Health. Each phone sharing Health says whose data it is. If a family member's phone shares Health through your account, you label it as theirs, and their data is kept separate from yours. Please share someone else's Health only with their agreement.

You can also add things yourself, such as a health card (for example allergies, medications, conditions, or an emergency contact) and logs of how you feel, symptoms, meals, or readings. These are treated as Health data too.

How We Use It

  • To write your daily health reads and weekly review, and to show your trends, charts, goals, and week-long experiments
  • To send care alerts when your numbers, or a family member's, look unusual against their own usual, if care watch is on
  • To answer your questions about your health when you ask Zinley in chat
  • To do things you approve from a read, such as adding a calendar block or setting a reminder

Health reads, weekly reviews, care alerts, and experiment results are sent as notifications in the Zinley app and on your devices. They are never sent by text message, email, or Telegram. If you ask Zinley about your health in a conversation on another channel, the answer goes to that conversation. Health data is only shared with you, the account owner. Zinley does not mention it to anyone else or include it in anything it sends on your behalf.

Who Processes It

  • AI model providers: To write reads and reviews and to answer your questions, the relevant Health data is sent through our AI gateway (Portkey) to model providers. Today these are OpenAI GPT models hosted on Microsoft Azure, and open-weight models (such as Qwen and MiniMax) served by Fireworks AI. They process it under the terms described in AI Providers and Model Training above, and no model is trained on it.
  • Search providers: Zinley may look up general health research or news (for example, about sleep and caffeine) through our search providers. These searches are checked before they are sent so they contain no health numbers, no names, no contact details, and nothing about you. If you share an area for local news, searches for local health news or outdoor places may include your city name.
  • Open-Meteo: For local air quality, UV, pollen, and heat, we use the approximate area you shared for News. Only the center of an area of a few kilometers across (or your city name, to find that area) is sent to Open-Meteo, never your exact location and never any Health data.

You can turn off local context and health research in Settings › Health.

What We Never Do

  • We do not use Health data for advertising or marketing, and we do not sell it
  • We do not share Health data with third parties for their own purposes
  • We do not use Health data to train any AI model
  • We comply with Apple's rules for HealthKit data, which prohibit using it for advertising, marketing, or similar data mining

Not Medical Advice

Zinley's health reads, alerts, and suggestions are general wellness information based on your own numbers. They are not medical advice, a diagnosis, or a substitute for a doctor. Zinley is designed never to tell you to start, stop, or change a medication. If you are unwell or worried, contact a medical professional or emergency services.

Retention

  • Daily rows sent by a phone are kept for 90 days. A phone that has not sent anything for 30 days is forgotten, along with its daily rows
  • Daily health reads are kept for 30 days, and weekly reviews for 26 weeks
  • Monthly summaries of your usual numbers are kept for 24 months so Zinley can notice longer changes
  • Logs you enter yourself are kept for 2 years. Your health card is kept until you change or delete it

Your Controls

  • Turn off sharing on any phone. The daily data it sent is deleted from Zinley's servers
  • Remove a family member. Their Health data, goals, alerts, health card, and logs are deleted
  • Turn off cycle tracking. Stored cycle data is deleted
  • Use "Delete all Health data from Zinley" in Settings › Health to delete everything, including reads, weekly reviews, goals, alerts, health cards, and logs
  • Delete your account. All Health data is removed as part of account deletion

You can also remove Zinley's access in your phone's Health settings at any time. After that, Zinley cannot read anything new.

Data Security

We use technical and organizational safeguards designed to protect your information. No security measure eliminates all risk.

Encryption

  • Supported network traffic is encrypted in transit using TLS
  • Our cloud providers provide encryption at rest for hosted data under their platform controls
  • The desktop app encrypts selected local values in production when WebCrypto initialization succeeds; not all local values use that mechanism
  • Files are accessed locally on your device. File content is not uploaded to our servers unless a specific task needs it, such as AI analysis. File hashes and embeddings may be synced for indexing.

Access Controls

  • Authorized access is limited by role, service permissions, network controls, and secret management
  • Multi-factor authentication is used where supported
  • Customer content is accessed only for operational, support, safety, security, or legal purposes described in this policy

Monitoring

  • Operational monitoring and error reporting
  • Security review and incident-response procedures

Data Retention

Different records have different retention rules. Current product behavior includes:

  • Account Data: Retained while the account is active and then handled through the account-deletion process described below
  • Conversation History: Saved until you delete it. Deletion moves a conversation to Trash for up to 30 days unless you permanently delete it sooner. A permanent purge may retain a minimal hashed deletion tombstone without message content
  • Persistent Memory: Retained until you clear it or the account-deletion workflow erases it
  • Operational AI Logs: Some request and response content is stored in restricted operational logs configured to expire after seven days
  • Phone and Email History: The history shown in the product depends on your plan. Those visibility windows do not by themselves delete older records, and some call records and recordings may be stored longer
  • Product Telemetry: Raw product events are configured to expire after 90 days and session rollups after 180 days. Per-user telemetry is included in the account-deletion workflow; aggregate records may remain
  • Feedback, Safety, Security, and Legal Records: Retained as reasonably needed for the purpose for which they were collected or as required by law

A self-service account-deletion request begins a three-day grace period. After that period, access is disabled and the deletion workflow erases supported conversations, people data, agent assets, memory, and per-user telemetry. Minimal account, billing, fraud-prevention, security, deletion, backup, aggregate, or legally required records may remain. Subscriptions and phone lines may require separate cancellation or release.

Telemetry and Diagnostics

We collect operational metrics and diagnostics to maintain service performance, security, and reliability.

Operational Metrics

We log latency, reliability, feature usage, and other operational events. We design product telemetry to minimize customer content, but limited identifiers and technical metadata may be included.

Error Reporting

We collect error logs and crash reports to identify and resolve technical issues. Automatic PII collection is disabled for supported diagnostics, but limited identifiers, error metadata, or context you submit with a report may be included.

Your Rights

Depending on where you live and the law that applies, you may have the following rights regarding your personal data:

Access and Portability

  • Access your personal data and understand how it is used
  • Export supported conversations in a machine-readable format
  • Request copies or portability of other personal data where applicable

Correction and Control

  • Update or correct your account information
  • Manage your connected devices and platforms
  • Control data sharing preferences
  • Withdraw consent for data processing at any time

Deletion and Restriction

  • Delete your account through the process described in this policy
  • Request deletion of specific data categories
  • Restrict certain types of data processing
  • Object to data processing for specific purposes
  • Appeal any denied data rights request

To exercise a privacy right, contact us at [email protected]. We will verify and respond to requests within the period required by applicable law.

International Data Transfers

Zinley is based in the United States, and our servers are primarily located in the US. If you access Zinley from outside the United States, your data may be transferred to, stored, and processed in the US and other countries where our service providers operate.

Where applicable law requires a transfer mechanism or additional safeguard, we use a mechanism appropriate to the service and transfer. Contact [email protected] for information relevant to your jurisdiction.

Cookies and Tracking

We use cookies and similar technologies on our services. The following describes how and why they are used:

Essential Cookies

These are necessary for our services to function properly, including authentication, security, and core functionality.

Analytics Cookies

These help us understand how our services are used so we can improve them. Where an analytics consent or opt-out control is available, it applies as described in that control.

Platform Identifiers

We use device and platform identifiers to enable cross-device and cross-platform functionality. This is essential for Zinley to work seamlessly across your desktop, phone, and messaging apps, and can be managed through your settings.

Children's Privacy

Zinley is not directed to individuals under the age of 18. We do not knowingly collect personal information from minors. If we become aware that we have collected personal information from a person under 18, we will promptly delete that information.

If you believe we have collected information from someone under 18, please contact us at [email protected].

Regional Privacy Laws

The rights available to you depend on your location and whether a particular law applies to Zinley's processing.

GDPR (European Union)

Where the EU GDPR or UK GDPR applies, you may have rights including access, correction, deletion, objection, restriction, portability, and the right to complain to a supervisory authority. Direct requests to [email protected].

CCPA (California)

California residents have rights under the California Consumer Privacy Act, including the right to know what personal information we collect, delete personal information, and opt out of the sale of personal information (note: we do not sell personal information).

LGPD (Brazil)

Where Brazil's Lei Geral de Proteção de Dados applies, you may have rights including access, correction, deletion, information about sharing, and review of certain processing decisions.

South Korea (PIPA)

Users in South Korea have rights under the Personal Information Protection Act, including rights of access, correction, and deletion. If we meet the thresholds under Article 31-2 of PIPA and its Enforcement Decree, we will designate a domestic agent in Korea and publish their details here. Korean users can direct all data protection inquiries to [email protected].

Canada (PIPEDA)

Where Canadian privacy law applies, you may have rights to access and correct personal information and to withdraw consent subject to legal or contractual restrictions. Data may be transferred to the United States or other countries for processing.

Other Jurisdictions

We process requests under the privacy law that applies to the request and our services.

Changes to This Policy

We may update this Privacy Policy from time to time. When we make changes, we will:

  • Update the "Last updated" date at the top of this policy
  • Provide advance notice of material changes when required by applicable law
  • Use email, an in-product notice, or another reasonable method when notice is appropriate

We recommend reviewing this policy periodically. We will notify you of material changes in accordance with the procedures described above.

Contact Information

For questions, concerns, or requests regarding this Privacy Policy, please contact us:

Data Controller: Zinley, San Francisco, CA, United States

Company Website: zinley.com

Privacy Team (all data protection inquiries): [email protected]

Human support escalation: [email protected]

We will respond within the period required by applicable law.

Zinley

Personal assistantProactive, personal, and always yours to steer.

Product

FeaturesYour personal networkPricingDownloadSign In

Support

How Zinley worksCredits, costs & limitsContact support

Company

AboutBlog
© 2026 Zinley, Inc.
PrivacyTermsSecurityX