Privacy Policy

Owner and operator

Huddl is owned and operated by The Scheduling Company LLC.

This marketing website

The public website uses Vercel Analytics and Speed Insights to measure website usage and performance. It does not require an account, display advertising units, or load ad-serving scripts. The published seller files and AdSense account meta tag support ownership verification. The product app has its own sign-in and advertising behavior described below.

For website privacy questions, email support@huddl.ing.

Information We Collect

huddl collects the information needed to create and manage your profile, including your display name, profile icon color, sign-in method, and account identifiers from connected social providers. We also collect content you add to huddls, including activities, availability, locations, logistics, messages, and choices, plus technical information such as cookies, session identifiers, device details, and browser data.

How We Use Information

We use this information to provide huddl, keep you signed in, personalize your profile, support social sign-in, maintain security, improve the service, and communicate with you about your account or huddls.

Google Sign-In Data

Google sign-in is optional. If you connect Google, huddl accesses the basic account information Google authorizes for sign-in: your name, email address, email verification status, and Google account identifier. We use this information only to create, identify, secure, link, and sign you in to your huddl account. We store the account information and connection metadata needed to maintain that account connection.

huddl does not request access to your Google Drive, Calendar, contacts, or other Google content. We do not sell Google user data or use it for advertising. We share it only with service providers that operate huddl, when required by law, or as otherwise described in this policy.

Cookies

huddl uses cookies and similar technologies for authentication, anonymous sessions, preferences, security, and service functionality. huddl also stores your analytics preference in a cookie so it can apply your choice before optional analytics events are sent.

Analytics

With your applicable choices, huddl measures product paths across the website, installed web app, Android app, and iOS app. Events may describe platform, session state, age range, country, screen, component, component state, action, outcome, broad domain, result counts, and duration buckets. This helps us understand paths through Home, Profile, browsers, editors, huddl stories, cards, searches, chats, tasks, choices, sentiments, and RSVPs.

MongoDB stores validated events under a random analytics subject ID separate from the database account ID. Identifiable events expire after 13 months; de-identified daily totals may be kept longer. No-session activity uses only an unlinked, short-lived journey ID. Firebase may receive the random subject ID for consented anonymous and linked sessions plus approved low-cardinality fields. Vercel receives aggregate route, performance, platform, session-state, age-band, surface, component, state, action, and outcome fields, but no huddl account or analytics subject ID.

Firebase and Vercel never receive exact search text, titles, messages, schedules, locations, invite data, social-graph data, or content IDs. huddl does not use keylogging, session replay, per-keystroke analytics, raw scroll coordinates, or arbitrary DOM capture.

Search History

huddl saves exact in-app search terms in its own MongoDB records for up to 13 months. Firebase and Vercel receive only search-length and result-count buckets, result type, outcome, and an approved broad category—not the search text. Delete my data removes saved history and identifiable analytics.

Advertising

Where huddl displays advertising, the website uses Google Ad Manager exclusively. Native apps use Google AdMob for the pinned app banner on Home and selected huddl pages, Story cards, Story-completion interstitials, and app-open ads, and use Google Ad Manager for pinned native or anchored-adaptive ads above Where and When lists and searches. RevenueCat receives AdMob ad load, display, click, failure, and impression-level revenue events for reporting. Web ad delivery and revenue are reported by Google Ad Manager and are not sent to RevenueCat. RevenueCat's separate Google Analytics integration reports subscription lifecycle events and is not part of the native AdMob event adapter. Unknown-age and adult profiles are eligible for personalized advertising only when the Profile choice, applicable Google consent platform, regional requirements, privacy signals, and iOS tracking permission all allow it. Known users age 13–17 are never eligible for personalized advertising, and known under-13 users receive no optional analytics or advertising.

Google's User Messaging Platform manages native-app consent notices; Google Ad Manager Privacy & Messaging manages applicable website notices and privacy options. On iOS, eligible adult and unknown-age users may also see Apple's tracking permission after a neutral huddl explanation. Google may process device or browser, ad interaction, consent, and ad revenue data under its policies. RevenueCat's native identifier is the huddl account identifier. huddl does not send Google advertising services or RevenueCat your birthday, exact searches, huddl or Plan identifiers, option or venue display names, precise coordinates or addresses, invitations, messages, chats, tasks, member identities, or individual RSVP data for ad targeting. You can change analytics, advertising measurement, personalization, and California do-not-sell/share choices in Profile; a change discards cached personalized ads.

You can change or withdraw consent previously given through Google's advertising consent message by selecting Google advertising privacy options below or in Profile. This reopens Google's privacy choices. huddl's Allow personalized ads setting is separate: turning it off restricts huddl's ad requests but does not replace Google's consent controls.

For standard Google ad units, huddl may enable Google's publisher control that allows a device's full IP address to be included in bid requests sent to Authorized Buyers, Open Bidding, SDK Bidding, and/or Google demand. This control does not apply to or govern partner bidding ad units. Google restricts full IP address sharing on non-personalized ads (NPA), limited ads (LTD), and restricted data processing (RDP) requests. For requests from the European Economic Area, United Kingdom, or Switzerland to which the GDPR applies, Google permits full IP addresses to be shared only on connected TV (CTV) inventory.

When you have explicitly allowed personalized ads and all applicable Google, age, regional, Global Privacy Control, do-not-sell/share, and iOS tracking choices permit it, huddl keeps a 90-day advertising-signal ledger. Eligible structured venue categories may be recorded when you view, open, select, create, or mark yourself going to a plan. Passive category/object views are counted at most once per 24 hours. Recent and stronger actions rank higher, current-huddl activity receives an additional boost, and huddl sends at most the primary and top three unexpired interests. Turning personalized ads off, requesting do-not-sell/share treatment, becoming age-ineligible, deleting your huddl data, or deleting your account deletes this ledger immediately.

Non-personalized requests use only the current structured activity or venue categories plus platform, placement, surface, and domain. Personalized requests may additionally use plan stage, time horizon, daypart, weekday/weekend, season, group-size bucket, coarse locality-to-country fallback, and the ranked interests described above. huddl rejects email addresses, URLs, identifiers, coordinates, street addresses, digit-heavy or oversized values, and sensitive category roots before an ad request. We do not derive ad targeting from free text, display names, messages, tasks, invitations, or individual RSVP records.

Age information

huddl requires a 13-or-older affirmation when you continue without an account and treats continuing with a social provider as the same affirmation. Providing an age range is optional. huddl stores your age group, not your birthday. If provided or derived, we store only an unknown, under-13, 13–17, or adult age group, the source of that classification, and when it was observed. You can select and save 13–17 or 18+ in Profile. A manual selection is not overwritten by provider information.

When you grant Google People birthday or Facebook birthday and age-range permissions during social sign-in, huddl may read that information once with the provider access token, derive an age group in memory, and discard the provider response. A complete Facebook birthday takes precedence over its age range. Missing, denied, incomplete, or unavailable provider data does not prevent sign-in and leaves the age range not provided. Provider-derived information fills only an unknown age range, except that a periodically refreshed provider-derived 13–17 range may transition to 18+. Provider information that indicates under 13 is ignored for a newly affirmed account; already stored under-13 profiles remain restricted. Discord, X, and Apple do not provide a usable age claim to huddl. Provider age data is not stored, exposed to clients, logged, sent to analytics, RevenueCat, AdMob, or Google Ad Manager, or used to overwrite a manual selection.

Children

huddl is not directed to, and we do not knowingly permit, children under 13 to use the service or create an account. If we learn that we have collected personal information from a child under 13, we will delete it. A parent or guardian who believes a child has provided information to huddl may contact us using the support contact in the app's store listing.

Families and Child Data

If huddl is made available to a child, content accessible to that child will be appropriate for children. We handle children's information in accordance with applicable children's privacy laws, including the US Children's Online Privacy Protection Act (COPPA) and the EU General Data Protection Regulation (GDPR). We do not use under-13 users' information for optional analytics. Known users age 13–17 receive analytics only where valid consent permits it and receive teen, non-personalized advertising treatment. huddl does not initialize or request advertising for a profile already classified as under 13.

huddl prohibits child sexual abuse and exploitation (CSAE) and child sexual abuse material (CSAM). Read huddl's Child Safety Standards for our prohibited-content and enforcement policies.

Your Choices

You may choose not to connect a social account and continue with an anonymous session. You may choose usage analytics, advertising measurement, and personalized advertising, request that huddl not sell or share your personal information where applicable, and request access, correction, or deletion of account information where required by applicable law.

You can also delete your profile settings, saved search history, and push subscriptions without deleting your account. See Delete your huddl data below for the exact steps, what is deleted, and what remains.

Delete your huddl data

You can delete private huddl data without deleting your account.

How to request deletion

1. Sign in to huddl and open your Profile.
2. Select Delete my data.
3. Press and hold the button for five seconds to confirm.

Data deleted immediately

huddl deletes your profile settings, saved in-app search history, identifiable MongoDB analytics across account aliases, the 90-day advertising-signal ledger, and push-notification subscriptions associated with your huddl account, including derived age group and advertising-consent records. huddl also revokes the analytics subject. This action is immediate and can safely be requested again if needed.

Data kept

Your sign-in account and connected sign-in providers remain so you can continue using huddl. Shared huddls, memberships, and historical shared-content snapshots are also kept for other participants. Use Delete account in Profile if you want to remove account access instead.

Operational and third-party data

huddl may retain de-identified aggregate analytics and short-lived security rate-limit counters. Vercel Web Analytics does not receive your huddl account identifier, search terms, locations, or shared content. Location lookups are processed by Geoapify under its own privacy and retention practices.

Contact huddl

For questions or reports about these policies, email support@huddl.ing. Contact instructions explain how to report an issue safely.