MEETIN.GS

Meetin.gs Privacy Policy

Read how Meetin.gs handles organizer, participant, scheduling, email, contact, and operational data, including user choices.

Effective and last updated: August 12, 2026

In plain English: Meetin.gs uses personal information to run accounts, scheduling pages, bookings, reminders, support, security, and limited public-site analytics. We do not sell or rent personal information. Google sign-in gives us basic identity information only; it does not give Meetin.gs access to your Google Calendar, Gmail, Drive, contacts, or Google password.

1. Scope and who is responsible

This Privacy Policy explains how Meetin.gs (“Meetin.gs,” “we,” “us,” or “our”) collects, uses, discloses, stores, and protects personal information when you visit the website, create an account, publish a scheduling page, respond to a poll, book a meeting, receive a service email, upload profile media, or contact us.

Meetin.gs is responsible for account, website, support, and service-operation data. An organizer who creates a scheduling page decides why a meeting is offered, who receives the link, which questions are asked, and how meeting information is used. That organizer may therefore have separate privacy duties. If your request concerns an organizer's use of your information, contact the organizer as well as Meetin.gs when appropriate.

2. Information we collect

CategoryExamplesWhy it is needed
Google account informationGoogle account identifier, name, email address, and profile picture URL.Create, secure, and display your Meetin.gs account.
Organizer and meeting informationOrganizer name and email, title, description, dates, times, time zone, duration, availability rules, location, video or phone details, preparation notes, internal notes, and meeting status.Create and manage booking pages, polls, confirmations, changes, and calendar files.
Participant informationName, email address, selected time or availability, optional discussion context, response status, and timestamps.Record a response, prevent conflicting bookings, notify the parties, and keep a reliable meeting history.
Page identity and uploadsPersonal slug, page title, introduction, avatar, logo, and cover image.Customize a public scheduling page. Uploaded images are resized, metadata is removed, and the saved copy is converted to WebP.
CommunicationsContact-form name, email, message, transactional email recipient, subject, delivery status, provider identifier, error details, related meeting identifiers, and email open time and count.Answer requests, deliver service messages, and pause optional email after repeated non-opens.
Technical and security informationIP address, browser and device information, referring page, requested URL, timestamps, session identifiers, and error or security events.Operate, secure, troubleshoot, measure, and improve the service.
Browser-only preferencesTheme choice, dashboard tutorial status, and per-account browser alarm settings.Remember how the site should behave on that browser. Browser alarms remain on the device and work only while the dashboard is open and the device is awake.

3. Where the information comes from

We receive information directly from organizers, participants, account holders, and people who contact us. Google provides the basic profile fields described above when an account holder approves sign-in. We also generate operational information when the service creates a meeting, sends an email, protects a session, records an error, or receives a normal web request.

4. How and why we use information

We use information to:

  • Create and authenticate a free Meetin.gs account.
  • Publish scheduling pages, show available times, collect responses, and confirm, reschedule, or cancel meetings.
  • Save meeting history, notes, calendar views, countdowns, and organizer settings.
  • Generate calendar files and send transactional messages and reminders.
  • Process profile images and show the identity chosen by an organizer.
  • Provide support, diagnose failures, prevent abuse, and protect users and infrastructure.
  • Understand use of public informational pages and improve navigation and content.
  • Comply with law, enforce our Terms of Service, and establish or defend legal claims.

Where privacy law requires a legal basis, we rely on performance of the service requested by you, our legitimate interests in operating and securing the service, consent where required, and compliance with legal obligations. You may object to processing based on legitimate interests where applicable.

5. Google sign-in and Google user data

Meetin.gs requests only the Google OAuth scopes openid, email, and profile. We use the resulting Google account identifier, name, email address, and profile picture URL to authenticate you, create or find your account, display your identity, and protect account access.

Meetin.gs does not use Google sign-in to read or change Google Calendar, Gmail, Google Drive, Google Contacts, or any other Google service, and we never receive your Google password. You can revoke Meetin.gs access through your Google Account permissions. Revocation stops future Google sign-in but does not by itself erase data already stored in Meetin.gs; use the contact form to request deletion.

Our use and transfer of information received from Google APIs follows the Google API Services User Data Policy, including its Limited Use requirements.

6. Public scheduling pages and private controls

Information visible through a share link

A personal scheduling page is meant to be shared. Anyone who receives or discovers its URL can view the organizer's chosen name, page text, profile media, meeting details, available dates and times, time zone information, and booking questions. These pages carry search-engine noindex controls, but noindex is not access control and cannot make a shared URL secret. Do not publish confidential information on a scheduling page.

Information kept away from invitees

Dashboard pages, internal organizer notes, account settings, management tokens, and private action links are not intended for public access. Keep private links secure and tell us promptly if you believe one has been exposed.

7. Cookies, local storage, and analytics

Essential browser storage

Meetin.gs uses a signed, HTTP-only session cookie to keep an account signed in, protect OAuth and form flows, and temporarily associate an anonymous organizer with a meeting created in the same browser. Clearing or blocking essential cookies can sign you out or remove temporary access to an unsaved meeting.

Local browser storage may remember the light or dark theme, dashboard tutorial status, and browser alarm settings. You can clear this information in your browser. Clearing an alarm from one browser does not cancel the meeting or an email reminder.

Public-page measurement

Public informational pages may use self-hosted Matomo at tracking.meetin.gs and Clicky site analytics (site ID 101465086). Depending on browser and provider settings, analytics may process the visited page, referrer, approximate location derived from an IP address, device or browser information, and visit timestamps. Meetin.gs excludes account, dashboard, event-management, booking, embed, and authentication routes from these analytics scripts.

Browser controls and content blockers can limit non-essential analytics. We do not use scheduling responses or private meeting content to build advertising profiles.

8. When information is disclosed

We disclose information only as needed for the purposes described here:

  • Other meeting participants. Organizers and participants receive the details needed to coordinate the meeting and understand its status.
  • Google. Google processes the sign-in request under its own terms and privacy policy.
  • Resend. When email delivery is configured, Resend processes recipient addresses, message content, message metadata, and delivery status to send transactional email. See the Resend Privacy Policy.
  • Hosting, database, storage, security, and analytics providers. These providers process the limited information needed to run their service for us.
  • Legal and safety recipients. We may disclose information when reasonably necessary to comply with law, respond to lawful process, protect rights or safety, investigate abuse, or defend a legal claim.
  • A business successor. Information may transfer as part of a merger, financing, reorganization, or sale of all or part of the service, subject to appropriate notice and protection.

Email open detection and inbox protection

Service emails can contain a unique one-pixel image served by Meetin.gs. When an email client loads it, we record the open time and count. We use this limited engagement record to prevent unwanted volume: after three consecutive tracked emails are not opened, optional welcome messages, six-hour reminders, and poll digests are deprecated, meaning paused. Opening a recent tracked message restores optional delivery. Booking confirmations and cancellations remain operational and continue because they contain requested meeting details.

Open detection is approximate. Image blocking can prevent an open from being recorded, while privacy proxies and automatic image loading can record an open without a person reading the message. The signed-in dashboard displays the current state and this limitation.

Meetin.gs does not sell or rent personal information, and we do not share it for cross-context behavioral advertising.

9. Retention and deletion

We keep account and scheduling information while the account, scheduling page, or meeting record remains active and for as long as reasonably needed to provide history, resolve disputes, prevent fraud, enforce agreements, and meet legal obligations. Support, security, and email-delivery records are kept only while they remain useful for those purposes. Backups may retain a protected copy for a limited recovery cycle before it is overwritten.

Retention depends on the type of record, its current purpose, user choices, security needs, and legal requirements. When information is no longer needed, we delete it or de-identify it. An organizer may also have a separate copy of participant or meeting information outside Meetin.gs.

10. International processing

Organizers, participants, and service providers may be in different countries. As a result, information can be processed outside the country where it was collected. Where required, we use contractual or other recognized safeguards for international transfers and preserve mandatory local rights.

11. Security

We use administrative, technical, and organizational safeguards designed to protect personal information. These include protected sessions, CSRF controls, restricted private routes, limited OAuth scopes, validation of uploads, removal of image metadata, and access controls around organizer actions. No internet service can promise absolute security. Protect share-management links and sign out of shared devices.

12. Your privacy choices and rights

Depending on where you live, you may have the right to request access, correction, deletion, or a portable copy of personal information; restrict or object to processing; withdraw consent; and complain to a privacy regulator. California residents may also have rights to know, correct, delete, and receive equal service, and to opt out of a sale or sharing where those activities occur. Meetin.gs does not sell personal information or share it for cross-context behavioral advertising.

Submit a request through the contact form. Include the email address and limited meeting context needed to find the record. We may verify identity or authority before acting, and an authorized agent may be asked for proof of authorization. Some information may be retained when law, security, fraud prevention, or the rights of another person require it.

13. Children

Meetin.gs is not directed to children under 13, and children under 13 may not create an account. Organizers must not use the service to collect children's personal information without the consent and safeguards required by law.

14. Changes and contact

We may update this policy when the service, providers, or legal requirements change. We will change the date at the top and provide additional notice when a change materially affects how personal information is used. Questions and privacy requests can be sent through the Meetin.gs contact page.

Privacy questions

Does Meetin.gs read my Google Calendar?

No. Google sign-in supplies only your basic identity profile. Meetin.gs does not request Google Calendar, Gmail, Drive, Contacts, or password access.

Is my personal scheduling page private?

No. It is a public share page for anyone with its URL. Search engines receive noindex instructions, but you should still treat the URL and all visible page content as public.

Does Meetin.gs sell personal information?

No. Meetin.gs does not sell or rent personal information and does not share it for cross-context behavioral advertising.

How do I request a copy, correction, or deletion?

Use the contact form with the account email and only enough context to locate the record. Identity verification and limited legal or security retention may apply.