Privacy Policy

Overview

This Privacy Policy describes how XTRNL, LLC ("getSm," "we") collects, uses, and protects information when you use getsm.net. By using getSm you agree to the practices described here. Effective date: August 11, 2026.

getSm is not built on surveillance advertising or selling your feed for behavioral ad profiling.

Information we collect

We collect information necessary to operate a video-first dating and safety-focused social platform, including:

• Account and profile information you provide (such as email, display name, and profile settings)
• Videos you post publicly and private video messages sent after mutual hits
• Interaction data needed to operate hits, blocks, flags, gifts, and geofencing
• Payment-related metadata for Zoomies and Pop Block processed by Stripe (we do not store full card numbers on getSm servers)
• Technical data such as device type, browser, IP address, logs, and security signals needed to run and protect the service

How we use information

We use collected information to:

• Provide the mingle board, hits, private messaging, gifts, and account features
• Validate public posts (including front-camera and face-in-frame checks where implemented)
• Enforce platform rules through automated safety systems
• Process optional payments through Stripe
• Respond to support requests and legal obligations
• Maintain security, prevent abuse, and improve reliability

What we do not do

getSm does not sell your personal information, build behavioral advertising profiles from your feed, or use private messages for ad targeting. We do not track you across unrelated websites for advertising purposes.

Public vs private content

Public mingle-board videos are visible to other members by design. Private video messages are available only after a mutual hit and are used to deliver the messaging feature—not for advertising or engagement manipulation.

Subprocessors

We use the following categories of subprocessors to operate getSm. Each processes personal data only to provide the service on our behalf, under contractual confidentiality and security obligations. We do not authorize subprocessors to use member data for their own advertising or unrelated purposes.

• Cloudflare, Inc. — website and application hosting (Cloudflare Pages), content delivery, edge security, and object storage (R2) for member videos and media. Data processed may include IP addresses, request logs, and stored media files. Primary processing in the United States with global edge delivery.
• Supabase, Inc. — database, authentication, serverless backend functions, and related infrastructure for accounts, posts, hits, messages, safety signals, notifications, and operational logs. Data processed may include account credentials, profile and content data, interaction metadata, and push subscription endpoints. Processing location follows our Supabase project region (United States).
• Stripe, Inc. — payment processing for Zoomies packs and Pop Block subscriptions at Stripe Checkout. Data processed may include name, email, billing address where provided, payment method metadata, and transaction records. getSm does not store full card numbers on getSm servers. Stripe may process data in the United States and other regions where Stripe operates.
• Google LLC (Google Fonts) — typography delivery for the web interface. When fonts load, Google may receive your IP address, browser user-agent, and referrer. Used for presentation only; not used by getSm for advertising.
• OpenStreetMap Foundation (Nominatim geocoding) — address and coordinate lookup when you use location or geofencing features. Queries you submit may be logged under OpenStreetMap usage policies. Requests may be processed in the EU and other regions where community infrastructure operates.

When you enable browser push notifications, delivery uses your device’s push service (for example Apple Push Notification service or Google’s Web Push infrastructure for Chrome). getSm stores push subscription endpoints in Supabase and sends notifications through standard Web Push protocols; we do not use a separate third-party marketing push vendor.

We may add or replace subprocessors as the service evolves. Material changes to this list will be reflected on this page with an updated effective date.

Retention schedules

We retain information only as long as needed for the purposes described in this policy, unless a longer period is required by law or legitimate safety, fraud-prevention, or dispute-resolution needs. Approximate schedules:

• Active account and profile data — retained while your account is active and as needed to provide the service.
• Public mingle-board posts — retained while the post is your current public post, until you replace or remove it, until it expires under the configured feed duration, or until account deletion is completed.
• Private video messages — retained while the mutual hit conversation exists and your account is active, subject to in-app deletion and safety enforcement.
• Hits, blocks, flags, gifts, and interaction metadata — retained while needed to operate features, enforce rules, and maintain conversation history; some enforcement-related records may be retained after account deletion where permitted by law.
• Account deletion — when you request deletion, a thirty (30) day cooldown applies during which you may reactivate. After that period, account data is scheduled for purge unless we must retain specific records for legal, safety, or billing obligations.
• Payment and subscription records — retained by Stripe and getSm as needed for accounting, tax, fraud prevention, chargebacks, subscription lifecycle, and enforcement, typically for the period required by applicable financial and tax law.
• Support correspondence — retained as needed to resolve your request and maintain a record of communications.
• Server, security, and access logs — retained for a limited period for troubleshooting, abuse detection, and security, generally not longer than necessary for those purposes.
• Push notification subscription endpoints — retained until you disable notifications, unsubscribe, or your account is deleted.

Backups and cached copies may persist for a short period after deletion before being overwritten. Residual data may also remain where deletion is technically impracticable or where retention is required by law.

Cookies, local storage, and analytics

getSm is a web application. We do not use third-party advertising cookies or cross-site behavioral tracking for ad profiling.

Technologies we use:

• Authentication session storage — Supabase Auth stores session tokens in your browser (typically local storage) so you remain signed in between visits. These are essential to operate your account.
• Application local storage and session storage — used for in-app preferences, boot state, campaign asset caching, and similar product functionality. These are first-party and not shared with advertisers.
• Service worker / PWA storage — if you install or use getSm as a progressive web app, the browser may cache application assets locally for performance.
• Push notification permissions — if you opt in, your browser stores a push subscription endpoint so getSm can deliver notifications you requested. You can revoke this in browser or device settings.

Analytics and measurement: getSm does not currently use third-party analytics platforms (such as Google Analytics, Meta Pixel, or similar advertising analytics SDKs). We collect first-party operational data— including server logs, security signals, error diagnostics, and aggregated purchase records from Stripe — to run, secure, and improve the service. That data is used for reliability and fraud prevention, not to build advertising profiles or sell your information.

You can clear site data through your browser settings, which will sign you out and remove locally stored preferences. Essential cookies or storage required for security and authentication may be re-created when you use getSm again.

Your choices

You can block members, use geofencing, hide posts or your account from discovery, and request account deletion through in-app settings or by emailing support [at] getsm.net.

Children

getSm is not directed to anyone under 18. We do not knowingly collect information from minors. If you believe a minor is using the service, contact support [at] getsm.net.

International users

getSm is operated from the United States. If you access the service from other regions, you understand that information may be processed in the United States and other locations where our providers operate.

Changes

We may update this Privacy Policy as the service evolves. Material changes will be posted on this page with an updated effective date. Continued use after changes are posted constitutes acceptance of the updated policy.

Contact

XTRNL, LLC Privacy and account questions: support [at] getsm.net Law enforcement: see our Law Enforcement Guidelines. Authorized requests only: legaldept [at] getsm.net