MeetSwift Privacy Policy

About this draft

MeetSwift is a Texas-based service for meeting preparation, capture, transcription, AI-assisted analysis and follow-through in company workspaces. This draft explains how information is handled across the public website and company portals. Contact info@meetswift.com for privacy questions.

The legal entity name, business address and whether additional provider-identification disclosures are required remain for owner and legal review. We have not determined which privacy laws apply to every person, organization or data flow. This draft is not a certification of compliance.

Acknowledging this Privacy Policy is separate from agreeing to the Terms of Service. It is not consent to advertising, consent to record meeting participants, or a waiver of privacy rights.

Information we collect and process

Account and workspace information: names, email addresses, authentication identifiers, verification and security information, workspace membership, roles, invitations, plan status and legal acknowledgement records. Authentication providers process credentials and factors; passwords are not submitted to the MeetSwift application API.

Calendar and integration information: connected account identifiers, permissions and access credentials, event titles, times, organizers, attendees and join links, and synchronization details needed for chosen features. Calendar passwords are not requested. Signing in with Microsoft does not itself connect a calendar.

Meeting information: uploaded or captured audio, recordings, transcripts, speaker and attendance information, meeting metadata and source evidence. Inputs can include third parties' personal information. You and your organization must have appropriate authority, notice and consent before capture or upload.

AI-derived information: summaries, decisions, suggested and assigned tasks, briefs, grounded answers and related evidence references. These outputs can contain personal information and can be inaccurate; review them against source material.

Billing and support information: customer and subscription identifiers, selected plan and seats, payment status, checkout and invoice details available from the payment provider, contact messages and support correspondence. Payment providers process payment-card details.

Technical information: device and browser context, authentication/session records, preferences, service activity, security and diagnostic logs, and coarse public-site analytics. The analytics provider's full technical collection is not yet verified.

Why information is used

We process information to create and secure accounts; manage workspace access; connect selected integrations; schedule and capture meetings; store, transcribe and analyze material; display and share permitted content; deliver task reminders and other requested notifications; manage billing; answer support requests; troubleshoot and maintain reliability; prevent abuse; and meet applicable legal obligations.

The website uses coarse usage measurement to understand entry points such as call-to-action selections, demo entry and completed Free-plan signup attribution. We do not sell personal information or use it for third-party targeted advertising. Legal bases, organizational instructions and any consent requirements depend on the data flow and applicable law and require review.

Workspace and organizational access

Meeting summaries, decisions, transcripts and recordings are limited to recognized attendees within the workspace. Being a workspace owner or administrator alone does not bypass this meeting-content restriction. A calendar invitation alone is not proof of attendance.

Tasks follow separate sharing rules: workspace owners and administrators can see workspace tasks; members can see tasks from meetings they attended or tasks assigned directly to them. Task-only access does not expose the source meeting title, summary, decisions, transcript or recording.

Your organization manages membership, roles, integrations and available workspace settings. For workplace content, your organization may determine the purposes of processing and handle requests. MeetSwift may act on its instructions; individual account and public-website information may have a different role. Those legal roles are not finally determined by this draft.

Service providers, integrations and other disclosures

MeetSwift does not sell personal information. Relevant information is disclosed to necessary service providers and providers of integrations you choose to operate the service, not for independent advertising. Categories include hosting and storage, authentication, calendar and meeting capture, transcription and AI processing, payment processing, email, analytics and optional delivery integrations.

Current service flows include Clerk authentication, Google or Microsoft calendar connections, Recall meeting capture/transcription, external AI processing, Stripe billing, Resend email and chosen Slack or Microsoft Teams delivery features. This is a description of service flows, not a complete or legally verified subprocessor inventory. Available providers can differ by feature and configuration.

We do not promise that information remains inside MeetSwift or that every provider is prohibited from model training or other independent uses. Provider identities, contracts, legal roles, subcontractors, data locations, model-training restrictions and retention/deletion terms have not all been verified. These require owner and legal review before finalization.

Information may also need to be disclosed to comply with applicable law or valid legal process, protect people and service security, or address a business transfer subject to applicable protections. The required notices, limits and contractual safeguards for these circumstances remain for review.

Cookies, browser storage and analytics

Cookies and browser storage support authentication, sessions, preferences, signup recovery and locally staged recording drafts. Locally recorded audio may remain in the browser for recovery rather than being uploaded immediately. Use the product's discard controls and take care on shared devices.

The public website sends coarse CTA, demo and signup-attribution events through an available analytics tracker. A limited CTA placement value and timestamp can be stored in sessionStorage, removed when used for attribution and expired after 24 hours if unused. These events do not include meeting content.

The analytics tracker may collect additional technical context under its configuration. Its full collection, retention, consent and opt-out settings have not been verified. This draft does not claim that there is no analytics or that a cookie-consent platform is in place. Blocking or clearing browser storage may interrupt sign-in, signup recovery and saved preferences.

Retention, deletion and account closure

On the Free plan, meeting history older than 30 days is hidden, not deleted. Source transcripts can remain after analysis. Where available, workspace retention settings govern eligible meeting records subject to product limits, legal holds and operational requirements; they do not necessarily govern provider or backup copies.

Cancelling a subscription, disconnecting an integration, removing a local activity item and deleting a workspace are different actions. Provider cancellation and file cleanup can be staged, delayed or blocked while deletion is verified. Removing an item from the MeetSwift interface does not always establish that all provider copies are erased.

We have not established a complete retention schedule for accounts, meeting material, security logs, legal acknowledgements, support records, providers or backups. Exact periods, legal-hold exceptions and backup/provider erasure practices require review. We do not promise immediate deletion or disappearance from every system.

Send account or data deletion requests to info@meetswift.com. We may need to verify identity or authority, coordinate with the relevant organization and retain information where required or permitted by applicable law. Where a law requires a response or deletion deadline, that law applies; this draft does not replace it with an unlimited response period.

Security and sensitive information

MeetSwift uses authentication, MFA and workspace access controls, but no service or transmission method can guarantee security or uninterrupted availability. Protect your credentials, manage workspace permissions carefully and report suspected unauthorized access to info@meetswift.com.

MeetSwift is not HIPAA ready. Do not submit protected health information. MeetSwift does not hold SOC 2 or ISO certification. Incident response, breach-notice duties and any additional contractual security commitments require review; this draft does not assert certification or legal compliance.

Privacy rights and requests

Depending on applicable law, your circumstances, the information and MeetSwift's role, you may have rights to access, correct or delete personal data, receive a portable copy, object to or restrict certain processing, withdraw a consent where processing relies on it, or opt out of sale, targeted advertising or specified profiling. Not every right or law applies to every user or workspace. This list is not a blanket promise of worldwide legal coverage.

For individual account or website requests, email info@meetswift.com with “Privacy request” and identify the relevant account and request. Do not send passwords, payment-card numbers or meeting recordings/transcripts. We may take reasonable steps to verify identity and authority and request the minimum information needed to locate the relevant data.

For workplace information, also contact your employer or workspace owner. MeetSwift may need to coordinate with that organization or route the request to it. A request does not grant access to another attendee's private meeting or override others' rights.

We will follow applicable statutory response periods, permitted extensions, exceptions and appeal requirements where they apply. If a request is denied, ask about review or appeal by replying to the decision or emailing “Privacy appeal” to info@meetswift.com. Where applicable, you may contact the relevant regulator. Request handling, verification, appeal and jurisdiction-specific notices need owner and legal review.

Texas law generally excludes individuals acting in a commercial or employment context from its consumer definition and generally exempts qualifying small businesses subject to exceptions. This does not establish whether Texas law or any other law applies to MeetSwift or a particular request. Acknowledging this policy does not waive non-waivable rights.

Children and legal capacity

You must have legal capacity or appropriate authority to use MeetSwift under applicable law. This draft does not set a numeric age cutoff or override laws on minors and parental consent. A parent, guardian or organization representative's acceptance does not by itself satisfy child-data requirements.

Do not submit children's personal information unless the use is lawful and all required authorizations, notices, consents and safeguards are in place. Contact info@meetswift.com before proposing a use involving children's information, or if you believe it has been submitted without appropriate authority. Eligibility and child-data handling require legal review.

International processing

MeetSwift is based in Texas and its providers may process information in the United States and other jurisdictions whose laws differ from yours. We have not verified every processing location, transfer mechanism or required contractual safeguard. This draft does not promise data residency, adequacy, standard contractual clauses or other transfer compliance. These details require review before finalization.

Versions, changes and review notes

This draft is version 2026-10-25, prepared October 25, 2026. It remains pending explicit owner approval and legal review. Signup acknowledgement records identify this exact draft version and a server acceptance time; they are not evidence of owner approval or legal review.

The exact text for an acknowledged version remains available at its version-specific Privacy Policy link. Future revisions should have separate versions. The notice process for material changes and any legally required renewed acknowledgement or consent must be confirmed before adopting a revised policy.

Before approval, review the legal entity and address; controller/processor roles and applicable jurisdictions; provider inventory, contracts and model-training terms; retention and deletion schedules; international transfer safeguards; analytics configuration and consent duties; rights/request handling; children and legal capacity; security/incident notices; and the effective date and change-notice process. These unknowns have not been invented or resolved by this implementation.