How MeetSwift handles your meetings.

Read the dedicated Privacy Policy (draft) for versioned privacy disclosures and requests. The overview below remains available alongside the other policies on this page.

Depending on how you use MeetSwift, information processed may include:

• Account and workspace identity, contact information, roles, authentication and access records, plan and billing status, and support messages.
• Connected calendar account and event details, integration permissions and credentials. We do not ask for your calendar password.
• Recordings, transcripts and what is derived from them: summaries, decisions, tasks and briefs.
• Service usage, device/browser and diagnostic information, and security or operational logs.

We use information to provide and support meetings, scheduling, transcription and AI processing, collaboration, billing, security, service reliability, legal compliance and coarse usage measurement.

MeetSwift does not sell personal information. We disclose relevant information to service providers that help operate the service and to providers of integrations you choose. This is intended for service delivery, not advertising. A provider’s legal role and any statutory exception depend on the actual data flow, contract and applicable law; this draft does not make a legal determination about a particular provider or disclosure.

Provider categories may include hosting and storage, authentication, calendars and meeting capture, transcription and AI, payment processing, email, analytics, and integrations you choose. This is not a complete provider or subprocessor inventory. Some providers may process information in other jurisdictions; their identities, locations, contracts, retention and deletion practices, subcontractors, and any model-training restrictions have not all been verified. “Vendor terms” means those providers’ contracts and data-handling practices. Do not assume that every provider is contractually restricted from using information for its own purposes until those terms are checked. For information received from Google APIs, the specific purpose and transfer restrictions in Google user data below apply; these general descriptions do not authorize unrelated uses of Google data.

Who can see meeting content

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.

Who can see tasks

Tasks follow a separate rule. Owners and admins can see workspace tasks. Members 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.

Privacy rights and requests (draft; subject to applicable law)

Depending on the law that applies to you, the information and MeetSwift’s role, you may be able to ask to access, correct or delete personal data, receive a copy of data you provided, or opt out of certain processing such as a sale, targeted advertising or specified profiling. Some rights apply only to people acting in an individual or household capacity, and laws may exempt certain businesses or data. For example, Texas’s consumer privacy law generally excludes individuals acting in a commercial or employment context and generally exempts qualifying small businesses, subject to exceptions. MeetSwift has not determined whether that law or another privacy law applies to each user, workspace, or data type.

For information in a work account, you may also contact your employer or workspace owner; depending on the data and applicable law, MeetSwift may need to coordinate with that organization or route the request to it. To contact MeetSwift, email info@meetswift.com with “Privacy request” in the subject. Identify the right you are seeking to exercise and the relevant account. Do not send passwords, payment-card numbers, or meeting recordings/transcripts. We may take reasonable steps to verify your identity or authority and may ask for information needed to locate the account, subject to applicable law.

Where a privacy law sets a response period, we will follow that law, including any permitted extension and notice. For example, where the Texas Data Privacy and Security Act applies, it generally requires a response without undue delay and no later than 45 days after receipt; a controller may extend once by up to 45 additional days when reasonably necessary and with notice. The Act also provides an appeal process, generally requiring a response within 60 days. If we deny a request where that law applies, you may appeal by replying to our decision or emailing the address above with “Privacy appeal” in the subject. If an appeal is denied, Texas law requires information about how to submit a complaint to the Texas Attorney General. See the Texas Data Privacy and Security Act and the Attorney General’s consumer privacy complaint process.

Some information may need to be retained or may not be subject to a requested action because of legal requirements, legal holds, security needs, or other exceptions allowed by law. A request does not itself guarantee immediate deletion from active systems, service providers, or backups. The request channel, verification steps, scope of rights, and applicable deadlines need owner and legal review before this draft is finalized.

This section of our Privacy Policy explains how MeetSwift accesses, uses, stores and shares information received from Google when you connect Google Calendar. Connecting a calendar is optional and is separate from signing in to MeetSwift or giving consent to record a meeting.

Access and permissions

For an individual Google Calendar connection, we request openid and email to verify the Google account, and https://www.googleapis.com/auth/calendar.readonly to read the calendars available to that account. Google shows the permissions before you authorize access. The read-only permission does not let this integration create, edit or delete your Google Calendar events. This calendar integration does not request access to your Gmail messages, Google Drive files, contacts or Google password.

We receive the Google account identifier and verified email address, authorized scopes and connection information. Calendar information accessed can include calendar identifiers and names; event identifiers, recurring-event identifiers, titles, dates and times, organizer names and email addresses, attendee email addresses, meeting/conference links, locations, descriptions and cancellation status. Locations and descriptions can be read to find supported meeting links. Reading these fields is not the same as storing every complete event description.

The current calendar feed reads selected calendars in a limited upcoming-event window, normally the next 30 days with a short look-back for ongoing meetings. That feed window is not a promise that all information derived from those events is deleted after 30 days. An existing workspace-managed Google connection may be handled through our integration infrastructure rather than the individual connection flow.

How we use Google information

• Verify and associate your connected Google account with your MeetSwift account and workspace, discover calendars, and display your selected upcoming meetings.
• Find supported meeting links, schedule or refresh meeting-bot participation when you choose capture or enable auto-join, and maintain the related scheduling records. Google authorization alone is not recording consent.
• Identify recurring meetings and relevant participants, prepare requested or enabled pre-meeting briefs, and apply attendee-based sharing checks. AI-assisted briefs may process relevant event context together with permitted prior meeting information.
• Operate and secure the connection, refresh authorization, handle errors and respond to support, deletion or legal requests as applicable.

MeetSwift does not sell Google user data or use it for advertising, retargeting, credit or lending decisions, or surveillance. MeetSwift does not run general-purpose model training or fine-tuning jobs using Google user data; generating a requested AI-assisted feature is distinct from training a model. Restrictions on downstream providers’ use, including model training, must also be checked before the policy is finalized.

Storage and protection

Connection records are stored in our application database with the account/workspace association, Google account identity, granted permissions, selected calendars and connection status. Individual-connection refresh tokens are encrypted before database storage; short-lived access tokens can be cached in server memory to make authorized requests. Managed connections use the integration provider’s credential handling. Credentials are not displayed to other workspace members.

Selected event information may also be stored in scheduling, bot, brief and related meeting records where needed for features you use. A personal calendar connection does not give every workspace member unrestricted access to browse your Google Calendar, but selected event metadata can appear in workspace scheduling or capture records under the applicable workspace permissions. Access to resulting meeting content and tasks follows the separate rules above. We use HTTPS for Google API requests; no system can guarantee absolute security.

Sharing and service providers

We send authorization and calendar requests to Google and use hosting, storage and integration infrastructure, including Replit, to operate the connection. When you enable meeting capture, the relevant meeting link and scheduling information may be sent to our meeting-capture provider, Recall. When you request or enable AI-assisted briefs, relevant event context may be processed through our AI-processing infrastructure and providers. If you enable sharing to another integration, the selected output can be sent to that destination under its sharing controls. A recipient may retain a copy under its own terms; disconnecting Google does not recall those copies.

Google API data may be used or transferred only as permitted by the Google API Services User Data Policy, including its Limited Use requirements where applicable. These restrictions also cover data derived from Google API data. Transfers must be limited to providing or improving the prominent user-facing features with the user’s consent, necessary security purposes, legal obligations, or a qualifying business transfer with explicit prior consent. Google data is not provided to advertising platforms or data brokers.

Human access to Google API data must be limited to the exceptions Google permits, such as your affirmative agreement to access specific data, necessary security investigation, applicable legal requirements, or permitted aggregated internal operations. General support access is not blanket permission to browse a connected calendar. This draft describes the required limits; it does not state that Google has verified or approved MeetSwift or that all downstream contracts have already been verified.

Disconnecting, retention and deletion

You can disconnect Google Calendar from MeetSwift’s calendar settings. This removes the saved MeetSwift connection and stops future calendar access through it. You can also remove MeetSwift’s authorization in your Google Account’s third-party connections. Disconnecting in MeetSwift does not itself revoke the grant at Google.

Disconnecting or revoking permission does not automatically erase already-created meeting, bot or brief records, delete provider copies, or cancel every bot that was previously scheduled. Review scheduled captures separately. Retained event-derived records follow the applicable workspace deletion and retention processes. Company-plan owners and administrators have custom meeting-retention and Legal Hold controls; the meeting-retention job is manually triggered in this build. Free’s 30-day history visibility limit is not deletion. A legal hold or required security/legal retention can delay deletion, and provider or backup retention may differ.

To request deletion of Google-derived information already stored by MeetSwift, email info@meetswift.com with “Google data deletion request,” identifying the relevant account and workspace. Do not include passwords, tokens or private event contents. We may need to verify your authority and coordinate with your workspace. This draft does not promise an unverified deletion deadline or immediate removal from every backup or provider.

Changes to Google data use

Before accessing additional Google data or using existing Google data for a new purpose beyond the disclosed practices, we must update these disclosures, notify affected users and obtain the required consent. Adding text to this policy does not by itself grant a new Google permission.

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 determining and meeting 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; get legal advice for cross-border or sensitive recordings.

• Use MeetSwift appropriately and lawfully.
• Protect your account and sign-in access.
• Manage workspace roles and connected integrations with care.
• Do not record or access meetings or data without authorization.
• Do not use MeetSwift for illegal or harmful content.

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

MeetSwift is not HIPAA ready. Do not upload protected health information (PHI). MeetSwift does not hold SOC 2 or ISO certification and does not guarantee security. See Security.

What you pay depends on your selected plan, seats and billing interval, and on the terms shown at checkout. A monthly subscription renews on its monthly billing date, based on when the subscription began. An annual subscription renews on its annual billing date. Existing plans, prices and arrangements are preserved. See Pricing.

To cancel, the workspace owner uses Settings → Manage payment details, which opens the Stripe hosted billing portal. Cancellation takes effect at the end of the paid period. If that option is unavailable to you, 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. This cancellation rule is separate from seat changes: increasing or decreasing paid seats may result in an immediate, prorated invoice under the applicable checkout and billing terms.

Cancelling a subscription is not the same as deleting your data. See Retention and deletion below.

On the Free plan, meeting history older than 30 days is hidden, not deleted. Source transcripts can remain after analysis.

Where your plan provides workspace meeting-retention controls, those settings determine the retention period for eligible meeting records, subject to any stated product limits and legal holds. Retention settings do not necessarily determine how long service providers or backups retain copies. Cleanup can be delayed or blocked while provider or file deletion is verified.

A complete retention schedule still needs review, and we do not promise that provider copies or backups immediately disappear. You can send deletion requests to info@meetswift.com. Applicable statutory response periods and deletion requirements apply where required by law.

MeetSwift uses cookies and browser storage for authentication, sessions, and preferences. The public website also uses an available analytics tracker for coarse events such as call-to-action selections, demo entry, and completed Free-plan signup attribution. Those events use a limited placement value and do not include meeting content.

• A call-to-action placement and timestamp may be stored temporarily in browser sessionStorage. It is removed when used for signup attribution and expires after 24 hours if unused.
• The website may send these coarse event values to its analytics tracker when one is available. The tracker may also collect technical context under its own configuration; its full collection, consent and retention settings have not been verified.
• MeetSwift does not sell this information or use it for third-party targeted advertising.

Blocking or clearing cookies and storage in your browser may affect sign-in and saved preferences. This draft does not claim that the website has no analytics, that analytics data is never transmitted or retained, or that a cookie-consent manager is in place.

The requested effective date is October 22, 2026. This page remains a non-binding draft pending owner and legal review; the date does not make it an adopted policy. The process for notifying users about future material changes still needs confirmation.

Proposed for legal review only: To the extent a choice of law is permitted, these policies and disputes concerning them would be governed by Texas law, without regard to its conflict-of-law rules. Any court proceeding would be brought in a state court located in Harris County, Texas, or, where federal jurisdiction exists, in the United States District Court for the Southern District of Texas, Houston Division, unless applicable law requires another forum. The parties would submit to those courts’ jurisdiction and venue to the extent permitted by law.

This proposal does not add arbitration, waive any non-waivable rights, or decide where a consumer may bring a claim under applicable law. The Terms of Service prepared for owner approval contain the proposed customer agreement and venue wording. Those Terms have not been reviewed by a lawyer or approved by the owner. Provider-identification requirements and enforceability remain unverified. This proposed clause is not yet a finalized term.

Questions or requests: info@meetswift.com. You can also visit Pricing, Security or Contact.