Policies

Privacy and service providers

The Privacy Policy describes the information MeetSwift processes, why it is used, who can access it and how to make requests. We share information with service providers only to operate MeetSwift. Google user data is handled as described in the Google user data section of the Privacy Policy.

Provider 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 Replit infrastructure, Clerk authentication, Google or Microsoft calendars, Recall.ai capture, OpenAI through Replit's AI service, Stripe payments and email or task-delivery services. Optional integrations send selected information to the destinations you choose.

Recipients may retain separate copies under their applicable retention policies. Disconnecting an integration does not recall information already delivered. We may disclose information as required by law or valid legal process; Google user data remains subject to Google's Limited Use restrictions.

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. The parties' legal roles depend on the processing and applicable law.

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.

Email info@meetswift.com with “Privacy request” and identify the relevant account and request. This contact accepts account, website and workplace-data requests. Do not send passwords, payment-card numbers or meeting recordings/transcripts.

MeetSwift handles individual account and website requests directly. For workplace data, MeetSwift coordinates with the relevant organization and may need to act on its instructions. You do not have to contact your organization first to submit a request to MeetSwift. Request routing does not determine the parties' legal roles, grant access to another attendee's private meeting, expand an employer's meeting access or override others' rights.

We take proportionate steps to verify control of the relevant account and, where needed, authority to act for another person or organization. We request only information needed to verify and handle the request. We do not routinely collect identity documents for this purpose.

We follow applicable statutory response periods, permitted extensions, exceptions and appeal requirements where they apply. We do not promise an additional fixed voluntary response period. This does not permit an unlimited response time or replace a legally required deadline.

If we deny a request, we explain the decision where permitted. You can request review by replying to the decision or emailing “Privacy appeal” to info@meetswift.com. We review the decision and follow any applicable appeal requirements. Where applicable, you may contact the relevant regulator.

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.

Recording notice and consent

Scheduling a bot requires the person scheduling it to acknowledge that participants have been informed and consent. That acknowledgement records the scheduler's statement; it does not independently notify attendees or prove that each attendee gave legally sufficient consent. Connecting a calendar is not participant consent.

You and your organization are responsible for applicable notice, consent, workplace and recording requirements before a bot joins, before recording with a microphone and before uploading audio or transcripts. You must also have permission to upload and process the material. Requirements can differ by participant location and context.

Acceptable use and account responsibilities

Use MeetSwift lawfully and with appropriate authorization. Protect your account, manage workspace roles and integrations carefully, and do not record or access meetings or data without permission. Do not upload unlawful or harmful material, interfere with the service or bypass security controls.

AI output and sensitive information

Summaries, decisions, tasks and briefs are provisional outputs. Check them against the source evidence, including names, dates and assignments. We do not guarantee their accuracy.

MeetSwift is not HIPAA compliant or HIPAA ready. Do not submit protected health information. MeetSwift does not hold SOC 2 or ISO certification and cannot guarantee security.

Subscriptions, cancellation and refunds

What you pay depends on your selected plan, seats, billing interval and the terms shown at checkout. Monthly subscriptions renew monthly and annual subscriptions renew annually, based on when the subscription began. Existing plans, prices and arrangements are preserved.

To cancel, the workspace owner uses Settings → Manage payment details to open the Stripe hosted billing portal. Cancellation takes effect at the end of the paid period. If that option is unavailable, email info@meetswift.com.

MeetSwift does not provide refunds or prorated credits for unused time when you cancel, except where applicable law requires otherwise. Access continues through the end of the paid period. Seat changes are separate and may result in a prorated invoice under the applicable checkout and billing terms.

Cancelling a subscription is not the same as deleting your data.

Cookies, browser storage and analytics

Cookies and browser storage support authentication, sessions, preferences, signup recovery and locally staged recordings. 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.

An analytics tracker can process technical context under its configuration. MeetSwift does not offer a cookie-consent preference center. Blocking or clearing browser storage may interrupt sign-in, signup recovery and saved preferences.

Retention, deletion and account closure

MeetSwift schedules deletion of Free-plan meeting records 30 days after the meeting. Paid workspaces can configure meeting retention in Settings; the default is 30 days. Legal holds can pause deletion on any plan. The background deletion process must complete; a visibility cutoff is not proof of erasure. Linked actions, decisions and briefs are included in local meeting cleanup where applicable. Provider-held copies, storage-deletion retries and backups are separate and can follow different schedules.

Source transcripts can remain after analysis until the applicable cleanup. 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.

Retention of account information, security logs, legal acknowledgements and support records depends on service operations, security needs and applicable legal obligations. We do not offer a universal deletion deadline or immediate removal from every provider or backup.

Send account or data deletion requests to info@meetswift.com. We use the verification, organizational coordination and response process described below. We may retain information where required or permitted by applicable law.

International processing

MeetSwift is based in Texas. Its providers may process information in the United States and other jurisdictions whose laws differ from yours. MeetSwift does not offer a data-residency commitment.

Texas law and contact

MeetSwift is based in Texas. To the extent permitted by law, Texas law governs the Terms of Service. Court proceedings use the Harris County, Texas state courts or, where federal jurisdiction exists, the Southern District of Texas, Houston Division. Applicable non-waivable rights are preserved. See the Terms of Service for the full agreement.

Contact info@meetswift.com for policy questions or requests.