Cookie Policy
How Midpoint uses cookies and browser storage. Last updated: August 3, 2026. Manage cookie settings.
This Cookie Policy explains how midpoint (“Company,” “we,” “us”) uses cookies and similar technologies on midpoint.to. It should be read with our Privacy Policy.
This Policy is based on Midpoint’s current codebase. We do not invent trackers. If we add analytics or advertising tools later, we will update this Policy and the consent controls first.
1. What are cookies?
Cookies are small text files stored on your device when you visit a website. Similar technologies include browser localStorage, session cookies, and pixels. Cookies may be session (deleted when you close the browser) or persistent (kept until they expire or you delete them).
2. Why we use cookies and storage
- Operate secure forms (CSRF protection) and sessions.
- Authenticate administrators.
- Run human-verification challenges where enabled.
- Remember optional preferences (theme) and private-poll draft UI state when you allow Functional storage.
- Record your cookie consent choice so we do not ask on every page load.
We currently do not use cookies for advertising, retargeting, social plugins, or product analytics suites.
3. Cookie categories
- Strictly necessary — required for security and core operation. Always on.
- Functional — optional browser storage for theme and poll draft convenience.
- Analytics / Performance / Personalization / Marketing / Social / Advertising — not used by Midpoint today. Controls exist so we can enable them only after disclosure and consent if we add those tools later.
4. First-party cookies we set
| Name | Provider | Purpose | Category | Duration | Essential |
|---|---|---|---|---|---|
PHPSESSID (default PHP session name) |
Midpoint (first-party) | Session identifier for CSRF tokens, form flows, flash messages, human-verification state, and admin authentication when those features are used | Strictly necessary | Session cookie (ends when the browser session ends; server-side session lifetime follows PHP session configuration) | Yes |
The session cookie is only created when a page or API needs a session (for example creating a poll, contacting us, or logging into admin). Many anonymous public pages intentionally avoid creating a session cookie.
Cookie attributes when set: HttpOnly, Secure on HTTPS, SameSite=Lax.
5. Browser storage (not cookies)
| Key | Provider | Purpose | Category | Duration | Essential |
|---|---|---|---|---|---|
midpoint-cookie-consent |
Midpoint | Stores consent version, categories, timestamp, and expiry | Strictly necessary (consent record) | Until expiry (about 180 days) or you clear site data | Yes |
letsmeet-theme |
Midpoint | Light/dark theme preference | Functional | Until cleared or Functional consent withdrawn | No |
letsmeet-{eventSlug} |
Midpoint | Private-poll draft UI state (display name, selected slots, optional location flags) on that device | Functional | Until cleared or Functional consent withdrawn | No |
We do not currently use sessionStorage or IndexedDB.
6. Third-party cookies and requests
Midpoint does not set third-party advertising cookies. Some pages load assets from third-party CDNs or services (for example Bootstrap/icons via jsDelivr, Google Fonts, Leaflet, and OpenStreetMap tiles / Nominatim lookups on map features). Those providers may process technical request data such as IP address under their own policies. Midpoint does not control whether those providers set their own cookies.
We do not embed Meta Pixel, Google Analytics, Google Tag Manager, Hotjar, Mixpanel, or similar trackers.
7. Payments, AI, authentication
- Payments: Midpoint does not currently process payments or set payment-provider cookies.
- AI product APIs: Midpoint does not send your content to generative AI providers as a product feature.
- End-user OAuth: Not used. Admin login uses first-party session cookies only.
8. How to manage cookies and withdraw consent
- Use Cookie settings in the site footer (or the banner) to Accept all, Reject non-essential, or Customize.
- Rejecting non-essential keeps strictly necessary cookies only and clears Functional
localStoragekeys we manage. - You can also delete cookies and site data in your browser settings. Blocking strictly necessary cookies may break forms and login.
Common browser help pages: Chrome, Firefox, Safari, and Edge settings under Privacy / Cookies (paths vary by version).
9. Consent records
Your choice is stored in localStorage with a consent version (v=2), timestamp, category flags, and an expiry of about 180 days. When the version changes or consent expires, we will ask again. Consent is not sold and is not used for advertising.
10. Changes
We may update this Cookie Policy when our practices change. The last-updated date on this page will change when we do.
11. Contact
- Email: support@midpoint.to
- Contact form: https://midpoint.to/contact
- Legal entity: [COMPANY LEGAL NAME], [STATE], [COUNTRY]