Privacy Policy
This Privacy Policy explains how PneumAI, LLC collects, uses, shares, stores, and otherwise processes personal information when you visit our website, use our products and services, or interact with our AI features.
No Data Sales Or Advertising
We do not and will never sell your data. We will never inject advertisements, sponsored placements, or paid promotions into your conversations or AI responses. We do not and will never use or share your data for advertising or ad targeting.
These commitments apply to all users and all service tiers, including free services, and cover personal information, service content, usage data, and aggregated or de-identified versions of that data. They take precedence over any broader permissions elsewhere in this document.
1. Scope
This Privacy Policy applies to the PneumAI, LLC website, our hosted products and services, demos, APIs, applications, and related business operations. It does not govern third-party services that we do not control, even if our Services link to them or integrate with them.
Google integrations and Google user data
Pneum.ai (Pneum), operated by PneumAI, LLC, connects Gmail, Google Calendar, and Google Drive to the agents and tools you authorize. This section applies to Google API data and copies of that data in tool results, conversations, notes, and outputs. It takes precedence over broader permissions elsewhere in this Policy, including provisions about training, analytics, sharing, and retention, on both free and paid services.
Data we access and how we use it
We access your Google account after you authorize a connection. Requested permissions depend on the tools you enable. We store the account identifier, account email or calendar name, granted permissions, and OAuth access and refresh tokens to identify the connection and maintain authorized access.
- Gmail: Message and thread identifiers, headers, senders, recipients, subjects, bodies, attachments, labels, and drafts. Selected tools use this information to search and read mail, answer email questions, prepare and send messages or replies, manage drafts and labels, and move messages to or from Trash.
- Google Calendar: Calendar identifiers, titles, time zones, event details, attendees, and availability. Selected tools use this information to identify calendars, answer scheduling questions, find free time, and create, update, or delete events in authorized calendars.
- Google Drive: File and folder identifiers, names, metadata, file contents, exported documents, comments, and sharing permissions. Selected tools use this information to find and retrieve existing files, upload files, create folders, organize or copy files, trash or restore files, and manage sharing and comments.
Relevant content may be included in an agent's context to generate a response or carry out your enabled workflow. Write tools change data in your Google account according to the access you grant.
Sharing and AI processing
We share relevant Google data with the agent runtime you authorize and with hosting, storage, security, and AI inference providers as needed to deliver the connected features. Where a voice response is requested, relevant text may also be processed by a speech provider. Providers process this data only to deliver the requested service, not for their own general-purpose model training. The providers involved depend on your deployment and model configuration.
Your instructions may also disclose data to recipients, collaborators, or connected services, for example when sending an email or sharing a Drive file. We do not sell Google user data or use or transfer it for advertising, data brokerage, creditworthiness, or lending decisions.
Google Workspace APIs are not used to develop, improve, or train non-personalized AI or machine-learning models. We do not use Google user data, including derived or de-identified copies, to train or fine-tune general-purpose models, and we do not permit our providers to do so. Free-tier training provisions and general training opt-ins elsewhere in this Policy do not apply to Google user data.
Personnel may read Google user data only with your affirmative agreement for specific data, when necessary for security investigations or legal compliance, or for internal operations on aggregated data anonymized as permitted by Google's Limited Use requirements. Other transfers are limited to security purposes, legal requirements, or a merger, acquisition, or asset sale with your explicit prior consent.
Pneum's use and transfer of information received from Google APIs adheres to the Google API Services User Data Policy, including the Limited Use requirements.
Storage and protection
Our integrations router stores connection records and encrypted credentials, tool invocation inputs and results, approval records, and audit events. Retrieved content can also be stored in your agent's conversation history, notes, or files when used by those features. Data may be processed in the locations described in Section 9.
We use HTTPS for Google API requests and hosted service connections. Saved connector credentials are encrypted using AES-256-GCM. Authenticated workspace access, tool permissions, and resource grants restrict access to connections and tool execution.
Retention, disconnection, and deletion
Connection credentials are kept while the connection remains active. Disconnecting an account in Pneum removes that connection and its saved credentials from the router's active storage, preventing further use of that connection. To revoke Google's authorization as well, remove Pneum from your Google Account's third-party connections.
Disconnecting or revoking access does not automatically erase previously stored tool history, conversations, notes, or files. These records are retained while needed to provide your saved history and workflows, unless you request their deletion; limited records may be kept as necessary for security or legal obligations. We do not retain Google data for general-purpose model training.
To request deletion of Google-derived data held by Pneum or its service providers, email [email protected] with your account email and the connection or records concerned. Do not send passwords or tokens. We may verify your identity and clarify the scope of the request. We delete data no longer needed for the disclosed purposes, subject to applicable legal retention requirements.
You may also request account deletion from Account Settings; see our account deletion instructions. If paid access remains, account deletion may be scheduled for the end of that term. A separate Google-data deletion request can be submitted by email. Deleting Pneum records does not delete the original emails, events, or files in Google, or copies already delivered to recipients or retained in environments you control.
Changes to Google data use
We will notify you of changes to how we access, use, store, or share Google user data and obtain your consent before using it for a new purpose beyond what you previously authorized.
2. Information We Collect
We may collect the following categories of information:
- Contact and account information, such as your name, email address, mobile phone number, company, username, and billing contact details.
- Messaging information, such as SMS opt-in and opt-out records, message content, delivery status, and your interactions with Mobile Agent.
- Voice and transcript data, such as microphone input, call/session recordings, transcripts, timestamps, and related interaction metadata when voice features are enabled.
- Service interaction data, such as prompts, text inputs, outputs, and support messages you submit through the Services.
- Usage and technical information, such as log data, browser type, operating system, device identifiers, IP address, user agent, approximate location, session identifiers, diagnostics, and interaction events.
- Cookies and similar technologies used for security, preferences, analytics, load balancing, and fraud prevention, including services such as Google Analytics.
- Payment and transaction information, if purchases are offered, which may be processed by third-party payment processors on our behalf.
- Contact and interest form information, such as name, email, company, message content, and anti-abuse metadata (including reCAPTCHA verification and request metadata) when you submit forms on our website.
3. How We Use Information
We may use personal information to:
- provide, operate, maintain, and secure the Services;
- authenticate users and manage accounts;
- process voice, transcripts, prompts, and other inputs to generate outputs;
- debug, monitor, troubleshoot, and improve reliability and safety;
- communicate with you about the Services, support, updates, and legal notices;
- send Mobile Agent setup messages, responses, reminders, task updates, and account or service notifications when you opt in;
- detect, investigate, and prevent misuse, fraud, spam, or security incidents;
- process payments, invoices, and related operational records;
- run lead handling and customer support workflows;
- train, tune, evaluate, and improve models only as described in Section 4;
- comply with law, enforce our agreements, and protect rights and safety;
- create aggregated or de-identified analytics, benchmarks, and product insights.
4. AI And Training Data Use
Google user data is excluded from the training and model-improvement permissions below. The Google integrations section above governs that data.
Because PneumAI, LLC provides voice-enabled AI products, we process service content for model inference, quality assurance, abuse prevention, reliability testing, safety review, and feature operations.
Free services: we may use anonymous or de-identified voice data, transcripts, and related interaction signals from free tiers to train, tune, evaluate, and improve our models and voice systems. We apply data minimization and remove direct identifiers before this use where reasonably possible.
Paid services: we do not use paid customer content, including voice recordings and transcripts, to train or fine-tune shared or general-purpose AI models, unless you explicitly opt in or we agree otherwise in a separate written agreement.
For all tiers, we may still process content as needed to provide the Services (for example, inference, abuse detection, debugging, incident response, support, and legal compliance). We may also use aggregated and de-identified data for analytics and service reliability.
Where local or self-hosted configurations are used, service content may stay in your environment depending on deployment settings. If content is not sent to us, we cannot use it for model improvement.
Public live demo: text submitted to the website demo is sent through our model gateway to an AI inference provider to generate a response. We request routes that do not collect prompts for training and request zero-data-retention processing. The Pneum.ai demo application keeps its chat, notes, and approvals only in memory for the live connection and destroys them when that connection ends. Network, security, reCAPTCHA, and access-log metadata may still be processed as described elsewhere in this Policy. Do not submit sensitive information to the public demo.
5. How We Share Information
Subject to our no-data-sales and no-advertising commitments and the Google integrations restrictions above, we may disclose personal information to:
- hosting, infrastructure, analytics, support, and security providers;
- AI, speech, and model subprocessors that help us deliver inference and voice features;
- fraud prevention and anti-abuse providers, such as reCAPTCHA services;
- payment processors and professional advisers;
- affiliates and successors in connection with financing, acquisition, merger, or asset sale;
- government authorities, courts, regulators, or counterparties where required by law or legal process;
- other parties when necessary to enforce our rights, investigate violations, prevent harm, or protect users, the public, or the Services.
Service providers receiving data on our behalf may not sell it or use it for advertising or ad targeting. Any successor receiving data in a merger, acquisition, or asset transfer must honor these commitments; such a transaction does not authorize selling your data or using it for advertising.
Mobile information and SMS consent
We do not sell or share mobile phone numbers, SMS opt-in data, or consent records with third parties or affiliates for their marketing or promotional purposes. We may disclose this information only to service providers that help us operate the messaging program, when required by law, or to protect the Services. Those providers may use it only to perform services for us.
If you opt in to Pneum Mobile Agent messages, message frequency varies based on your activity and settings. Message and data rates may apply. Reply STOP to opt out or HELP for assistance. Consent to receive text messages is not a condition of purchase.
6. Legal Bases
Where applicable, we process personal information under one or more of the following legal bases: performance of a contract, compliance with legal obligations, our legitimate interests, and your consent.
7. Cookies And Similar Technologies
We may use cookies, local storage, pixels, SDKs, and similar tools to remember preferences, authenticate sessions, analyze usage, improve performance, and secure the Services. You can control cookies through your browser settings, though some features may not function properly if cookies are disabled.
8. Data Retention
Google user data follows the retention and deletion rules above.
We retain personal information for as long as reasonably necessary for the purposes described in this Privacy Policy, including to provide the Services, maintain business records, resolve disputes, and comply with law. Retention periods vary based on data type, product tier, your settings, contractual commitments, and applicable legal requirements.
For free services, anonymous or de-identified voice/transcript datasets used for model improvement may be retained longer. For paid services, content is retained according to service configuration and contractual terms and is not retained for model training unless you explicitly opt in.
9. International Data Transfers
We may process and store information in the United States and other jurisdictions where we or our service providers operate. If you use the Services from outside the United States, you understand that your information may be transferred to and processed in countries that may have different data protection laws than your jurisdiction.
10. Security
We use reasonable administrative, technical, and organizational safeguards designed to protect personal information. No method of transmission or storage is completely secure, and we cannot guarantee absolute security.
11. Your Rights And Choices
Depending on where you live, you may have rights to access, correct, delete, restrict, port, or object to certain processing of your personal information, and to appeal certain decisions. You may also have the right to withdraw consent where processing is based on consent. We may need to verify your identity before acting on a request.
To submit a privacy request, contact us at [email protected].
12. Children
The Services are not directed to children under 13, and you may not use the Services if you are under 13. If you are between 13 and the age of majority in your jurisdiction, you may use the Services only with permission and supervision from a parent or legal guardian. If we learn that we collected personal information from a child in violation of applicable law, we may delete it.
13. Sensitive And High-Risk Data
Do not submit highly sensitive information to the Services unless you are confident the Services are appropriate for that use and you have all required rights and consents. This includes biometric identifiers, protected health information, government identification numbers, financial account credentials, and other data subject to heightened regulatory obligations, unless we have expressly agreed in writing to support that use case.
If you use speaker verification or similar voice identity controls, you are responsible for providing required notices and obtaining required permissions from end users.
14. Changes To This Privacy Policy
We may update this Privacy Policy from time to time. The updated version will become effective when posted, unless otherwise required by law. If changes are material, we may provide additional notice. Updates will not remove or weaken our no-data-sales and no-advertising commitments.
15. Contact Us
If you have questions about this Privacy Policy or our privacy practices, contact us at [email protected] or by mail at Pneum.ai Legal.