Privacy
MeetSwift Privacy Policy
Version 2026-10-27 · Prepared October 27, 2026
Prepared for owner publication as an updated draft with Google user-data disclosures. Not adopted as a final policy. Processor safeguards, legal review and other unresolved issues remain under review. The preparation date is not an effective date.
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. The provider name supplied by the owner is MeetSwift. Contact info@meetswift.com for privacy questions and requests.
A business mailing address is not yet available. Any additional legal entity or provider-identification disclosures required by applicable law remain unresolved. We have not determined which privacy laws apply to every person, organization or data flow. This remains a draft, 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.
How MeetSwift handles Google user data
MeetSwift offers an optional Google Calendar connection. This section explains what Google user data we access through Google APIs when you connect your account, how we use it, who receives 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
The individual Google Calendar connection requests your basic account identity (openid and email) and read-only calendar access (https://www.googleapis.com/auth/calendar.readonly). It accesses:
- Your verified Google email address and Google account identifier, to associate the connection with your MeetSwift account and workspace.
- Calendar names, identifiers and whether a calendar is your primary calendar, so you can choose which calendars MeetSwift checks. We save your selected calendar identifiers.
- For selected calendars, calendar lists normally cover the previous 30 days and the next 30 days. We request event titles, start and end times, status, event and recurring-series identifiers, organizer name and email, attendee email addresses, meeting links, location and description. We can also refresh a specific selected event when you use a feature that needs an up-to-date check.
- We scan event locations and descriptions to find supported Google Meet, Microsoft Teams or Zoom links, including joining details such as an inline password. Our event parser does not retain the complete location or description.
- A Google refresh token, stored encrypted, and short-lived access tokens held temporarily in server memory, so the connection can keep working. Temporary authorization records help secure the connection process.
These permissions do not let MeetSwift create, change or delete your calendar events. This Calendar connection does not request access to Gmail, Google Drive or contacts. A historical workspace-managed Google connection uses its separate provider grant; its permissions must be checked separately rather than assumed to match the individual connection.
How we use Google user data
We use the calendar connection for the user-facing features you choose:
- Display meetings from your selected calendars.
- Find supported meeting links and schedule the MeetSwift notetaker when capture is enabled and you schedule it or enable Auto-Join with the required consent acknowledgement. Connecting a calendar is not recording consent and does not itself notify participants.
- Match recurring meetings and prepare pre-meeting briefs from earlier meeting results. Briefs are assembled locally; the earlier summaries and action items may have been generated using AI.
- Use calendar invitations to check access to shared pre-meeting briefs. Captured meeting notes use separate recognized-attendance checks: an invitation alone, or an administrator role alone, does not grant access to meeting content.
We do not sell Google user data or use it for advertising, creditworthiness or lending. MeetSwift uses AI to produce requested meeting results, not to run general-purpose model training.
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
Relevant data is shared to operate the features above. We do not sell it:
- Replit hosts MeetSwift's servers, database and file storage. Some integration traffic and our AI requests also pass through Replit services and their processing chain.
- Recall.ai receives a selected meeting's join link, a scheduled join time when applicable, and an opaque internal bot identifier and related routing/configuration information. Our bot-creation request does not send the Google event title, attendee list, full description or calendar list. Separately, the notetaker can observe participants and capture meeting audio, recordings and transcripts when it joins.
- OpenAI, through Replit's AI service, processes meeting transcripts and related evidence to generate summaries, action items and answers. Calendar event objects and OAuth tokens are not included in these prompts. Meeting dates are included in analysis, and cross-meeting questions can include meeting titles and dates that originated in a calendar. Spoken or captured content may itself contain calendar information.
- Authorized workspace users can see scheduled-capture or brief metadata under the relevant access rules. Full captured meeting content is restricted to recognized attendees. Tasks have separate assignment and workspace-role sharing rules. Your personal calendar selection and unrelated calendar events are not an administrator calendar browser; scheduling or capturing a meeting creates separate stored records.
- If you enable sharing or delivery features, selected meeting outputs may be sent to their chosen recipients or integrations, such as email, Slack or Microsoft Teams. Google-derived information in those outputs remains subject to Google's restrictions.
- Information may need to be disclosed to comply with applicable law or valid legal process. A transfer of Google user data in a merger, acquisition or sale of assets is subject to Google's Limited Use requirements, including explicit prior consent where required.
Google's rules limit permitted transfers and downstream use; sharing with a provider is not permission for unrestricted reuse. These restrictions also apply to data derived from Google APIs.
How we keep and delete Google user data
- We do not save complete Google event response bodies. We do retain feature-specific data: account and selected-calendar identifiers, encrypted credentials, and relevant scheduling, bot, meeting and brief records, such as titles, times, meeting links and recurrence identifiers. These records can remain after a meeting ends. The calendar fetch window is not a deletion schedule.
- Connection details and credentials are kept while the connection is active. Meeting records are kept for the applicable workspace retention period or until authorized deletion, subject to legal holds and completion of cleanup. Some scheduling, bot and operational records have separate retention periods; we have not established a single deletion period for all such records.
- Disconnecting Google Calendar in MeetSwift Settings deletes the stored connection, encrypted refresh token, selected-calendar identifiers and pending authorization records for your connection. It stops future access through that connection. It does not automatically erase existing meeting, bot or brief records, cancel previously scheduled bots, or revoke Google's authorization. You can separately remove MeetSwift's access in your Google account permissions.
- Captured meeting records follow workspace retention settings. Free-plan meeting deletion is scheduled for 30 days after the meeting, subject to legal holds and completion of the deletion process. Provider-held copies and backups are separate and may follow different schedules.
- Email info@meetswift.com to request deletion of Google user data or your account. We verify identity and authority and handle the request under applicable law, workspace instructions and any lawful retention exceptions. This draft does not promise a universal 30-day completion deadline or a verified backup-expiry period.
- Deleting local connection or meeting data does not prove erasure from every provider. Recall may retain meeting URLs, bot metadata and logs separately from recording media; hosting, proxy, AI and backup retention also need provider-specific review. Contact us to clarify the scope and status of a deletion 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. 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
MeetSwift schedules deletion of Free-plan meeting records 30 days after the meeting. Workspace retention settings apply where available, and 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. 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 will 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 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.
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 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-27, prepared October 27, 2026, and adds Google user-data disclosures to the Privacy Policy itself. It is prepared for owner publication, not adopted as a final policy. Legal review and the issues below remain unresolved. The preparation date is not an effective date. Existing acknowledgement records continue to identify the exact version acknowledged and its server acceptance time; they are not evidence of legal review or acceptance of this revised draft.
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.
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. The owner approved this notice process; operational delivery procedures still require confirmation before adoption.
Before adoption, resolve the unavailable business address and any additional provider-identification disclosures; applicable legal roles and jurisdictions; provider inventory, contracts and model-training terms; implementation of the intended retention policy and remaining deletion schedules; international transfer safeguards; analytics configuration and consent duties; request and appeal operations; children and legal capacity; security/incident notices; material-change notice delivery; and an effective date. Owner decisions do not by themselves verify these matters or certify legal compliance.