Privacy

MeetSwift Privacy Policy

Effective: October 27, 2026 · Version 2026-10-27-4

Stable text for version 2026-10-27-4

Earlier version: 2026-10-27-3 Earlier version: 2026-10-27-2 Earlier version: 2026-10-27 Earlier version: 2026-10-26 Earlier version: 2026-10-25

About this policy

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

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: account identifiers, names, email addresses, organization and workspace details, memberships, roles, authentication and access records, plan and billing status, preferences and support messages.

Calendar and integration information: connected account identities, permissions, encrypted credentials, selected calendars and event information used for the features you choose. The Google user data section below describes Google Calendar in detail.

Meeting material: recordings, transcripts, participant information, meeting dates and related metadata. Material you submit may include other people's 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.

How MeetSwift handles Google user data

Connecting Google Calendar is optional. Here is what we access, how we use and share it, and how we keep and delete it.

MeetSwift's use and transfer of information received from Google APIs adheres to the Google API Services User Data Policy, including the Limited Use requirements.

What Google user data we access

We request your basic Google account identity (openid and email) and read-only Calendar access (calendar.readonly). We access:

Your verified email address and Google account identifier, to link the connection to your MeetSwift account and workspace.
Calendar names, identifiers and primary-calendar status, so you can choose calendars. We save your selected calendar identifiers.
Event titles, start and end times, status, event and recurring-series identifiers, organizer name and email, attendee email addresses, meeting links, locations and descriptions.
An encrypted refresh token and temporary access tokens, so your connection keeps working. Temporary authorization records secure sign-in.

Calendar lists normally cover the previous 30 days and the next 30 days. We also refresh individual selected events when needed. We check locations and descriptions for supported meeting links and joining details, including inline passwords. We do not store complete event response bodies, locations or descriptions.

This Calendar connection does not let MeetSwift create, change or delete events. It does not request Gmail, Drive or contacts access.

How we use Google user data

We use this data for the features you choose:

Show meetings from your selected calendars.
Find Google Meet, Microsoft Teams or Zoom links and schedule capture when you choose it or enable Auto-Join with the required acknowledgement. Connecting a calendar is not recording consent and does not notify participants.
Match recurring meetings and prepare briefs from earlier meeting results. Briefs are assembled locally from summaries, tasks and other evidence; earlier results may be AI-generated.
Check invitations for shared pre-meeting briefs. Captured meeting content requires recognized attendance. An invitation or administrator role alone does not grant access.

MeetSwift does not use Google user data to develop, improve or train generalized or non-personalized artificial intelligence or machine learning models. We use AI to produce the meeting results you request.

We do not sell Google user data or use it for advertising, creditworthiness or lending. Google's Limited Use rules restrict human reading to your specific affirmative permission, necessary security or legal purposes, or qualifying aggregated and anonymized internal operations. These restrictions also apply to processors.

How we share Google user data

We share relevant information to operate your chosen features:

Replit hosts our servers, database and files. Some integration traffic and AI requests also pass through Replit's services.
Recall.ai receives the meeting link, a scheduled join time when applicable, an opaque internal bot identifier and routing/configuration information. Bot creation does not send the Google event title, attendee list or complete event details. After joining, Recall separately observes participants and captures meeting audio, recordings and transcripts.
OpenAI, through Replit's AI service, processes transcripts and evidence for summaries, action items and answers. Prompts do not include Google event objects or OAuth tokens. Analysis includes meeting dates; cross-meeting questions can include calendar-derived titles and dates. Captured content can itself contain calendar information.
Authorized workspace users may see capture or brief metadata. Full meeting content remains attendee-restricted; tasks have separate assignment and role-based sharing. Optional email, Slack or Teams delivery sends selected outputs to your chosen recipients.
We may disclose information as required by law or valid legal process. Business transfers remain subject to Limited Use requirements, including explicit prior consent where required.

Google's restrictions also apply to derived data and downstream providers. Sharing does not permit unrestricted reuse.

How we keep and delete Google user data

We keep connection details, selected-calendar identifiers and encrypted credentials while your connection is active. Scheduling, bot, meeting and brief records can remain after a meeting or disconnection. The calendar fetch window is not a deletion schedule.
Free-plan meeting records are deleted through automatic cleanup 30 days after the meeting. Paid workspaces set their own retention period in Settings; the default is 30 days. Legal holds can pause deletion, and file cleanup may finish later. Some scheduling and bot metadata remains separate from meeting content.
Disconnecting Google Calendar in MeetSwift Settings deletes the stored connection, encrypted refresh token, selected-calendar identifiers and pending authorization records. It stops future access through that connection. It does not delete existing meeting records, cancel scheduled bots or revoke Google's authorization. Review scheduled captures separately.
Remove MeetSwift's authorization at https://myaccount.google.com/permissions to revoke Google access.
Email info@meetswift.com to request deletion of Google user data or your account. We handle requests promptly after verifying your identity and authority, subject to applicable law, workspace instructions and lawful retention exceptions.
Service providers may retain separate copies under their own retention policies, such as Recall meeting URLs, bot metadata and logs, and hosting-provider backups. These copies may remain after deletion from MeetSwift and follow separate deletion schedules. Contact us about the scope and status of your request.

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. The legal basis and any consent requirements depend on the processing and applicable law.

Workspace and organizational access

Meeting summaries, decisions, transcripts and recordings are available to recognized attendees within the workspace and to the member whose connected calendar requested that capture, even if that member did not attend. If several members' eligible linked calendar events request the same deduplicated capture, each requesting calendar owner has this access. MeetSwift records the calendar-owner-of-capture access basis separately from attendance and preserves it across reanalysis. Being a workspace owner or administrator alone does not grant meeting-content access; other invitees or workspace members do not gain access merely from a calendar invitation.

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.

Service providers, integrations and other disclosures

We share information with service providers only to operate MeetSwift. Google user data is handled as described in the Google user data section above. MeetSwift does not sell personal information or disclose it for independent advertising.

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.

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.

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 compliant or HIPAA ready. Do not submit protected health information. MeetSwift does not hold SOC 2 or ISO certification. We follow applicable legal requirements for incident and breach notifications.

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.

Children and legal capacity

You must have legal capacity or appropriate authority to use MeetSwift under applicable law. This policy 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.

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.

Versions and changes

This Privacy Policy is effective October 27, 2026, as version 2026-10-27-4. Earlier versions remain available at their version-specific links.

The exact text for an acknowledged version remains available at its version-specific Privacy Policy link. Revisions receive separate versions; earlier versions and their acknowledgement records are not overwritten. Existing acknowledgements remain valid; this revision does not require existing account holders to acknowledge it again.

For material changes, MeetSwift will notify affected account holders by email and an in-product notice before the changes take effect, and provide any additional notice or obtain any renewed acknowledgement or consent required by applicable law.

Effective October 27, 2026.