adsideō Privacy Policy

Privacy notice. This describes current practices, available controls and their limits. Publishing it is not certification of worldwide compliance or permission to record other people. Feature availability and controls differ by app version.

Who is responsible

Adsideo Inc, a United States company, operates adsideō and adsideo.ai. Business contact address supplied for this notice: 701 17th Ave Apt 407, Seattle, WA 98122, United States. Privacy requests and complaints: support@adsideo.ai. Support: support@adsideo.ai.

We determine the purposes of website, account, billing and support processing. An organization deploying adsideō may separately determine how its work information is processed. Local-only processing does not automatically make Adsideo Inc a processor or remove privacy duties. Organizational roles and any required data-processing agreement must be established for the actual deployment.

This policy includes information about people whose messages, documents or speech appear in permitted work context. It does not authorize covert recording or override anyone else's rights. adsideō is for adults aged 18 or over.

Data and purposes

Website and waitlist: Email address, referral/campaign source and communications you submit; network/browser information needed to deliver and protect the site. Used for invitations, requests and site operation. Joining the waitlist is not consent to unrelated marketing. See website technologies.
Account and subscription: Account identifiers, email, authentication/session information, subscription status and billing references. Used for sign-in, access, purchased services and necessary transaction records. Stripe handles payment details; our account service stores billing identifiers/status, not full card numbers.
Desktop context: Permitted accessibility text and OCR output, application/window metadata, file references or indexed text, microphone/system audio and transcribed speech. Used locally for enabled recall, summaries, suggestions and draft previews. Sources can contain third-party, confidential or sensitive information. Recognition and interpretation can be wrong.
Derived information: Summaries, source excerpts, speaker labels, decisions, commitments, corrections, drafts and retrieval metadata. Used for source-backed assistance across enabled features. Generated statements are not independent proof of events.
Diagnostics and support: App/build and OS versions, launch/crash/hang markers, runtime settings and performance metadata; information you send to support. Used for reliability, security and troubleshooting. Updated builds require a separate opt-in to minimal diagnostic uploads; the server rejects uploads without the current consent marker and does not accept free-text logs. Older builds may still show an enabled setting, but that is not current upload consent. Local exports can include privacy-filtered app logs: inspect them before manually sharing and send no unnecessary work content.

Ordinary work-context inference uses local models. Local-first does not mean all services are offline: authentication, licensing, payments, downloads, connected-account APIs, enabled diagnostics and support use the network. Updated builds use local pattern embeddings and do not use a configured OpenAI key for that legacy route. Older builds may contain a conditional cloud-embedding path; update before processing sensitive or connected-account content, or remove that configured key.

We do not use personal work content or Google API data to train a general-purpose AI model, sell it to advertisers, build advertising profiles, or determine credit, employment, insurance or similar eligibility. Separate research/training would require independently reviewed data sources and permissions; ordinary product consent is not training consent.

Google accounts

Connecting Google is optional. Native Google sign-in supplies basic identity information, such as your account identifier, email and profile information, and requests gmail.readonly and calendar.events.readonly. Each account is connected separately. Customers never provide a Google password, client ID or app client secret to adsideō.

The current connector imports Gmail headers, participants and bounded message text, plus calendar titles, descriptions, dates, attendees and meeting links. Initial import covers the previous 30 days of mail, excluding Spam/Trash, and primary-calendar events from 30 days before to 14 days after import. Updates are fetched while the app runs, subject to permissions and limits. Attachments are not downloaded by this connector.

The current integration stages data in an encrypted local account cache and displays import status. A future ontology, draft or briefing feature is not grounds to request extra permissions now, nor is it represented here as completed. Read-only permission does not allow sending mail, editing messages or changing events.

Credentials are managed through the native sign-in SDK and protected device-local Keychain storage. The import service does not send message bodies or calendar descriptions to an Adsideo server or external model. Server-side app-account authentication is separate from this local provider authorization.

Limited Use: adsideō's use and transfer of information received from Google APIs adheres to the Google API Services User Data Policy, including its Limited Use requirements. Google API data is used only to provide or improve the user-facing integration you authorize. It is not sold, used for advertising or creditworthiness, or used to develop, improve or train generalized AI or machine-learning models. Human access is limited to exceptions permitted by that policy, such as your explicit agreement to view specific information for support, security investigations or legal obligations.

Disconnect an account in the orb's Integrations section to stop import and request removal of its cache and authorization. You can also revoke access in Google Account connections. Provider revocation and local deletion are distinct: offline cleanup/revocation may finish when the app next runs or reconnects. Exports, independently shared copies and messages remaining at Google are not deleted by disconnecting adsideō.

Microsoft/Slack require their own configured, available integration and authorization. Unavailable connections do not import data; untested connections are not represented as verified.

Meetings and voice identities

In updated builds, background audio defaults off and requires a separate choice in Privacy. For a detected meeting, capture also waits for your acknowledgment that participants were notified and you have the required permission; the acknowledgment applies to that meeting, not later meetings. This is an account user's attestation, not independent participant consent, and the app does not itself deliver the required notices.

Transcription, anonymous speaker separation, assigning a text label and remembering a voice are different operations. A participant list, visible name or audio channel does not prove who spoke. Recognition may misidentify people and is not suitable for authentication or significant decisions about them.

Remember this voice can store a name-linked numerical voice template and compare it with later speech on that Mac. This can be biometric personal information. Your account consent, microphone permission or choice of name is not another participant's consent to biometric enrollment.

Before recording/enrollment, give required notices and obtain permissions applicable to participants and workplaces. Where required, obtain the speaker's separate informed explicit consent or written release before capture. Offer a genuine alternative: remain unnamed or use a meeting-only text label. Publicly available audio is not blanket permission to build a voice identity.

Updated enrollment controls require a release-reference record and your attestation of separate written speaker permission before remembering a voice. This is not independent verification of the speaker or their release. Use Forget voice when permission or purpose ends; do not use persistent recognition where additional legal safeguards have not been established. See the voice-data notice and retention policy.

Legal grounds and choices

Where a legal basis is required: necessary account/service processing relies on performance of the agreement; financial records on applicable legal obligations; proportionate security, fraud prevention and administration on legitimate interests after balancing rights; optional marketing/capture on consent where required. A service contract does not justify all workplace monitoring or sensitive-data processing.

Biometric identification and other specially protected information need an additional applicable condition. Consent must be specific, informed, withdrawable and valid; employee consent is not automatically freely given. Without a valid ground, processing must not occur.

Declining optional capture or an account limits that feature, not unrelated permissions. Available controls include monitoring pause, Private Mode, exclusions, macOS permission revocation, account disconnect, speaker-name removal and forgetting voices. Stopping capture does not itself erase saved information.

Retention and deletion

Local limits and separate operational records
Information	Current rule
New raw context observations	Seven days from capture in the new evidence path, not reprocessing time. This is not a full-recording archive.
Selected context excerpts	Up to 90 days from capture, subject to earlier source deletion/exclusions/access checks. A summary is not a verbatim source.
Google message text and metadata	Local message text: seven days from body capture. Cached metadata: 90 days. Not deletion from Google.
Voice templates/name bindings	Updated reusable templates expire within 90 days of the recorded authorization; reusing the same release reference does not renew it. Expired templates are excluded and removed when the profile is accessed and during active-profile maintenance. Forget voice removes a template and linked names earlier. Device backups and inactive profiles need separate cleanup.
Reports, context and history	Depend on source, feature and deletion settings; do not assume every historical record has the limits above. Expiry/deletion must reach quotations, dependent answers and caches.
Uploaded diagnostic reports	Report-only storage rules target 30 days from upload, including older reports. Additional cleanup checks new minimal reports. Provider deletion may lag; this is not a guarantee of deletion at an exact instant or from independent backups.
Privacy-request case records	Open requests are retained while being resolved, with internal response targets; they are not subject to diagnostic-report expiry. After a documented closure, minimal case records are kept for up to 90 days, subject to provider cleanup delay. A documented legal hold is separate, limited to what is necessary and reviewed for release. A receipt or closure record is not proof that requested deletion was performed.
Account, waitlist, billing and support	Kept while needed to deliver the requested service, answer requests, maintain necessary financial/legal records or resolve disputes. Contact us to leave the waitlist or close an account. Provider-specific backup expiry and complete automated erasure are not represented as verified; lawful retention exceptions are assessed per request.

Expiry checks and bounded local cleanup require the app to run; physical bytes cannot be guaranteed to disappear at an exact instant while closed. Expired information must not be reused as current evidence. Exports, device backups and copies held by meeting tools or other services need separate management. Signing out or uninstalling is not a verified deletion request.

Requests and complaints

Email support@adsideo.ai or write to the address above for access, a copy, correction, deletion, withdrawal, restriction, objection or appeal. State what you need and the account/source involved; no special wording is required. Authorized agents may act with appropriate authority. Verification is proportionate; never send passwords, codes or an entire mailbox.

We respond within applicable deadlines and explain lawful limits, refusals or extensions. EU/UK rights requests normally require a response within one month; California requests generally within 45 days, with applicable extensions. UK privacy complaints are acknowledged within 30 days, investigated and answered without undue delay. Complaints and rights requests are separate processes. You may contact your regulator without waiving remedies.

We do not discriminate for exercising protected rights. We cannot remotely retrieve device-only information simply because you email us; we explain local steps and limitations. Where an employer is the relevant controller, we may direct requests to it while protecting others' information.

We do not sell information or share it for cross-context behavioral advertising, or use sensitive information to infer characteristics for ads. No targeted-advertising tags are configured. Optional website media stays off until allowed; Global Privacy Control or Do Not Track keeps it off. Reopen Privacy choices on the homepage to withdraw permission. Third-party media has its own practices once enabled.

Regional notices

Rights depend on applicable law and processing, not merely this list. This policy does not announce unrestricted worldwide availability.

United States: State rights may include access/knowledge, correction, deletion, portability, opt-outs from sale/targeted ads/certain profiling, sensitive-data consent and appeals. California categories can include identifiers, commercial/subscription information, internet/device activity, audio/electronic information, inferences and sensitive information such as communication content or identifying voice templates. Sources, purposes, recipients and retention appear above. CCPA thresholds and state exemptions need assessment; no exemption from biometric, recording or consumer laws is assumed.
EEA and United Kingdom: Access, rectification, erasure, restriction, portability, objection, consent withdrawal and complaints to your supervisory authority or the ICO may apply. adsideō is not used for solely automated decisions with legal or similarly significant effects. Required representatives, impact assessments and transfer arrangements must be established before relevant launch.
Switzerland: The revised FADP may provide access/information, correction and other remedies. Actual overseas countries/safeguards must be disclosed. Contact the FDPIC where appropriate.
India: Contact us for access information, correction, erasure, withdrawal and grievances. The DPDP Act/Rules have staged commencement; as of October 24, 2026, most substantive duties are scheduled for a later phase. We do not describe all DPDP rights or Board remedies as already operative. Existing Indian requirements and upcoming commencement dates require review. adsideō does not intentionally enroll children.
Canada: Applicable federal/provincial law may provide meaningful-consent, access, correction, withdrawal and complaint rights. Quebec adds governance, language, transfer and biometric requirements. Contact the OPC or provincial authority. No Quebec biometric declaration/authorization is claimed.
Australia and New Zealand: Applicable access, correction and complaint rights remain, including the OAIC or New Zealand Privacy Commissioner. Sensitive-information consent, overseas processing and New Zealand's Biometric Processing Privacy Code need separate assessment.
Brazil and Singapore: Applicable access, correction, withdrawal and other rights remain. Brazil's LGPD adds confirmation, portability, deletion and review rights where applicable. Singapore's PDPA does not create an unconditional erasure or universal portability right. Contact the ANPD or PDPC.

Additional translations, representatives, registrations, notices and sector rules may apply. Assess eligibility before offering adsideō in another market. One English policy is not sufficient everywhere.

Changes

Material changes require appropriate notice and renewed consent where required. An updated policy is not retroactive permission for incompatible uses. Privacy questions: support@adsideo.ai.