Privacy Policy
How Meetyn handles organizer accounts, email-free guest responses, shared meetings, billing and device information.
Effective September 23, 2026 · Version 2026-09-28 · Postly Technologies, Inc.
1. Who handles your information
Postly Technologies, Inc. operates Meetyn and is responsible for account administration, security, service operations and other processing it determines. An organization may separately determine why it collects meeting and guest information; we process those records to provide its requested service, subject to applicable law and any agreed data-processing terms. Contact support@postly.ai with the subject Meetyn privacy. This notice covers the website, PWA, native clients and associated support.
2. Accounts and authentication
We process account identifiers, display names, email addresses, email-verification status, sign-in information and provider identifiers. Google or Apple sign-in shares the information permitted by your provider settings; Apple may provide a relay address. Email/password and passwordless sign-in use Firebase authentication. Meetyn does not need access to your address book to schedule a meeting. Authentication providers maintain their own security and processing practices. Native clients and the website use the same account identity.
3. Meetings, guests and organizations
When you use AI assistance, your submitted brief and our drafting instructions are sent to Google Gemini. Do not include sensitive guest or payment information. We record usage counts, token counts and estimated costs for fair usage and service management; we do not store briefs or outputs in AI usage logs. Google processes requests under its applicable API terms and privacy practices. Applied drafts become regular meeting content when saved. We store titles, descriptions, joining links or locations, dates, timezones, poll choices, guest names, RSVPs, optional bring/help requests and guests' offers, organizer-entered item costs and budgets, optional contribution purposes, recipient names, external payment links, organizer-entered bank details or other payment instructions, goals, deadlines and organizer-reported totals, timestamps and organizer/workspace relationships. Contribution cards, payment instructions and aggregate progress are visible to anyone with the invitation link. Meetyn does not receive card details. Meetyn does not process contribution payments or connect payment accounts. We store guest pledges and amounts the organizer manually confirms, with confirmation history and timestamps. Meetyn charges no contribution transaction fee. Public totals show organizer-confirmed amounts separately from unverified pledges. External payment providers apply their own terms and privacy practices. Deleting a meetup does not refund a payment or erase the provider’s records. Other guests see only how much of each item is promised; authorized organizers see who offered to bring it, and costs and budgets are visible only to them. Team administration uses member emails, invitations, roles and permission records. Guest-detail access follows workspace defaults or selected active organizers, with access retained by the meetup creator and workspace Owners. Guest participation does not require an email or account, but is not anonymous to authorized organizers: they can see submitted names and responses. A random browser credential lets a guest edit their own response; its server-side representation links that browser to the response. Optional verified notification emails and preferences are processed only for the enabled service you request. Providing an email for meeting updates does not create an account. If you separately request an account and organizer trial, confirming your email creates that account and starts the eligible trial and trial emails. We record this choice and its time. Gathering pages list meetings the organizer explicitly attaches; minimum-turnout settings record the response target, deadline, decision and optional automatic cancellation. Account reminder subscriptions also connect the meeting to your account for dashboard notices; reminder jobs track delivery and retries.
Connected meeting providers
You can optionally connect Google Meet or Zoom where available to create joining links from the website or native app. We store the connected account identifier and email, authorized permissions, and encrypted access and refresh tokens to provide this feature. Google Meet receives requests to create meeting spaces; Zoom receives the meeting title, start time, duration and timezone when you generate a link. We save the returned joining link with your meeting when you save it. We do not receive video-call recordings. Native connection handoffs expire after ten minutes and are then scheduled for deletion; their authorization codes are encrypted. Disconnecting removes the stored connection from Meetyn, and account deletion removes these connections and pending handoffs. Disconnecting or deleting Meetyn does not cancel meetings already created with the provider. You can also revoke access in your provider account. Provider terms, account limits and privacy notices apply.
Connected Google Calendar
You can optionally connect Google Calendar and choose, per meeting, to add it to your primary calendar. For those meetings Meetyn sends Google the title, description, time, timezone, location or joining link and invitation link, and keeps the resulting event identifier. To bring your changes back, Meetyn reads the change feed of your primary calendar and receives change notifications from Google. It uses only the events it created for your synced meetings; other events are discarded as they are read and are not stored. Edits you make to a synced event's title, time or description update the Meetyn meeting and may notify its guests, as an edit in Meetyn would. Guests are not added to the Google Calendar event and Google does not email them. We store the connected account email, authorized permissions, an encrypted refresh token, a sync position and push-channel details. Disconnecting stops syncing and removes these from Meetyn; events already in your calendar remain there. Account deletion removes the connection. You can also revoke access in your Google account.
4. Technical, support and payment records
Our infrastructure processes IP addresses, browser/device information, request times and operational errors to deliver and secure the service. Meetyn rate-limit records use a salted representation of the request address, while infrastructure providers may retain their own logs. Support receives the information you send. Billing can include customer, subscription, transaction and invoice references, organizer quantity and payment status. Stripe/Link handles payment information; Meetyn does not store full payment-card numbers or security codes. Do not send passwords, private sign-in links or full card details to support.
5. Purposes and legal bases
We use information to provide requested scheduling and account features, apply permissions, authenticate users, send service messages, administer billing, answer support, prevent abuse and meet legal obligations. Where data-protection law requires a legal basis, these purposes rely on contract performance, legitimate interests in operating and protecting a proportionate service, legal obligations, or consent for optional activities that require it. Guest scheduling may be provided on an organizer's instructions and legal basis. You may object to applicable legitimate-interest processing or withdraw optional consent for the future. We do not make legal or similarly significant decisions about you solely through automated profiling.
6. Visibility and sharing
Workspace owners and admins can enable Make, Zapier and Discord destinations. These receive selected meeting titles, times, status and invitation links; RSVP events add a response choice without guest names, email addresses or identity tokens. Webhook credentials are encrypted at rest. Delivery payloads and history are retained for up to 30 days. Those services handle received data under their own terms and the organizer’s configuration. Enabled group calendar feeds share all attached scheduled meeting details, including descriptions, locations and joining links. Optional address checking sends the entered address and postal code to Google Maps. The organizer-entered address and selected Google place identifier are saved with the meeting; Google address suggestions are displayed temporarily. Embedded invitation maps share the destination and normal browser request information, such as IP address, with Google under its privacy policy. Directions open Google Maps with the organizer-supplied destination; Meetyn does not request the guest’s device location for this action. Anyone with an invitation link can access its meeting details. The same applies to a permanent gathering-page link and a meeting calendar-subscription URL. Calendar providers retrieve subscription details on their own refresh schedule. Other guests generally see response totals; authorized workspace organizers can see and export individual guest responses. Meeting pages are marked not to be indexed, but a shared link is not confidential and search or preview services may not honor every instruction. Sharing an invitation lets chat platforms retrieve its title, scheduled time, status and preview image, including a countdown snapshot. Chat previews, screenshots, exports and third-party calendar copies are outside Meetyn's control and may remain cached after changes or deletion. We do not publish notification email addresses as a guest list. Organizations must explain their own use of participant information and protect exported copies.
7. Providers and other recipients
Firebase/Google supports authentication, MongoDB Atlas stores product records, Heroku/Salesforce hosts the application, Amazon SES delivers service emails and Stripe/Link supports payment services. Cloudflare currently provides domain/DNS services. Google also supplies selected website services such as consented Analytics, requested translation and web fonts. Opening a video, calendar or sign-in provider sends information to that provider under its own notice. See Service Providers for details. We may disclose necessary information to advisers, authorities where legally required, or a business successor subject to appropriate protections and notice. We do not sell personal information or share it for cross-context behavioral advertising.
8. Analytics, storage and translation
Google Analytics on eligible public pages loads only after your analytics choice is granted. Private invitations, authentication and dashboard pages are excluded from our page measurement. Measurements omit URL queries and fragments, and we do not intentionally send guest names, meeting titles or email addresses. Advertising personalization and Google signals are disabled. Cookie preferences lets you change your choice. Essential authentication and response-editing storage remains separate. Choosing another interface language loads Google Translate; user-content fields marked for exclusion are not intended for translation, but translation is a third-party page service and not a confidential-document tool. Google Fonts requests also expose ordinary connection information to Google. See the Cookie Policy for storage details.
9. PWA and native clients
The PWA uses the same web data practices. Its service worker caches public icons and a generic offline page, not private account, meeting or billing pages, and does not queue offline writes. Native clients store authentication state and may remember the email used for a pending passwordless sign-in on the device. Native account responses contain selected profile fields, workspace choices and feature-access flags, not subscription or invoice records. Native apps do not request push notification permissions. They store a random guest response credential and your self-confirmed calendar action on the device. You may explicitly turn meeting email reminders on or off from an invitation; this preference is shared across your account. Opening the app alone does not change it. Authentication emails remain available.
10. Retention
Account, meeting, RSVP, poll and organization records remain while needed for the requested service and are reviewed in response to deletion requests; they do not automatically disappear when a meeting ends or is cancelled. Support, security and financial records may remain as needed for their purpose, dispute resolution and legal obligations. Rate-limit entries are scheduled to expire after approximately two minutes; database expiry is asynchronous. Cookie expiry does not delete the related server record. Provider logs, backups and legally required records follow their applicable retention arrangements and may persist after removal from the active service. We do not promise instant erasure from every backup or third-party copy. Contact us for information about retention relevant to your request.
11. Your choices and rights
You can edit your profile and, using the originating browser, your guest response; change optional analytics choices; and manage available web notification settings. Contact support to request access, correction, export, deletion, restriction or objection. Depending on your location you may also have portability, appeal and consent-withdrawal rights. We verify identity and authority proportionately, explain lawful exceptions, respond within applicable deadlines and do not discriminate for exercising applicable privacy rights. Guests without an account can identify the meeting and response through support. You may complain to your local data-protection authority, including the ICO where applicable. Full account deletion also stops renewal of subscriptions for organizations you own. Cancelling renewal alone does not delete your account.
12. Children and sensitive information
Meetyn is not directed to children under 13 and does not offer a parental-consent enrollment service. Do not submit personal information for children under 13 or use public meeting text for medical records, government identifiers, payment credentials or other highly sensitive information. If you believe a child has submitted information in breach of these requirements, contact support so we can investigate and remove it as appropriate. Organizers arranging family or youth activities should communicate with eligible adults and avoid unnecessary child information.
13. International processing and security
Providers may process information in the United States and other countries. Where required, international transfers must rely on an applicable legal mechanism and safeguards, not this notice alone. Contact support for information about safeguards relevant to your data. We use measures such as encrypted transport, server-side permissions and revocation checks, but no system can guarantee absolute security. Meetyn is not described as end-to-end encrypted. Report suspected security incidents promptly; we will handle required notices and responses under applicable law.
14. Updates and contact
We update this notice when data practices change and provide additional notice or seek consent where required before materially different processing. The effective date identifies this version. Send privacy questions and rights requests to Postly Technologies, Inc. at support@postly.ai, with the subject Meetyn privacy. Our Data Deletion page explains how organizers and guests can request removal.
Questions? support@postly.ai