Swipe10 Privacy Policy

Information you provide

We collect information you choose to share in the app.

• Account details such as username, email, profile photo, profile text, and account settings.
• Photos, videos, captions, ratings, comments, reports, menu uploads, storefront uploads, and other content you submit.
• Optional check-ins, location tags, place details, price details, dish, drink, menu, and storefront notes.
• Taste profile settings, including cuisines, favorites, foods or drinks to avoid, dietary preferences, and recommendation signals.
• Client Health information when you use that feature, such as provider connections, client intake, goals, allergies or avoidances, meal logs, nutrition notes, recommendations, activity entries, and provider review notes.
• Business, provider, billing, compliance, license, workspace, and support information when you request or manage dashboard access.

Information we collect automatically

• Device and app usage data for performance and safety.
• Approximate or precise location if you enable location services, check-ins, nearby discovery, or map features.
• Technical logs that help us prevent abuse.
• App installation, browser, device, network, and diagnostic information.
• Activity summaries from supported device integrations only when you grant permission in an installed app. The website cannot read Apple Health or Health Connect directly.

Website analytics and browser storage

Public pages use Vercel Web Analytics and Speed Insights to measure aggregate page usage and performance. Swipe10 does not send account email, username, or precise browser location as custom analytics properties. Optional product analytics inside the signed-in web app are off by default and can be enabled or disabled in Settings.

• Swipe10 also counts a fixed set of adoption steps, such as starting or completing Swipe10, opening a shared Group Swipe, selecting a result action, or choosing signup. These are stored only as daily totals with fixed coarse categories. This counter does not store account, session, or device identifiers, network addresses, coordinates, URLs, search text, room tokens, or raw errors.
• Network addresses may be used transiently in memory to limit abuse of the aggregate counter, but the counter does not persist or log them. Hosting and security providers may separately process technical access logs under their configured retention policies.
• Nearby discovery sends coordinates to Swipe10 only after you choose to share browser location.
• The landing page may keep a recent browser location, anonymous browser identifier, cached public results, and rating state in local browser storage so repeat visits can load faster.
• You can remove this local data through your browser's site-data controls. Blocking or clearing it may reset nearby results and anonymous rating state.

How we use your data

• Provide ratings, rankings, and personalized feeds.
• Personalize menus, Dish Radar, search, alerts, and recommendations based on your taste profile and settings.
• Operate Client Health provider/client workflows, including consent, intake, meal review, macro estimates, activity summaries, recommendations, and dashboard access.
• Generate or improve AI-assisted classification, menu matching, calorie and macro estimates, safety checks, and moderation workflows.
• Moderate reports and keep the community safe.
• Improve features, reliability, and customer support.
• Manage subscriptions, checkout, billing portals, workspace limits, and access requests.

Sharing and disclosures

We share information only as needed to operate, secure, support, and improve Swipe10, or when you direct us to share it. We do not sell personal data. We may disclose data to comply with law or protect users.

• Public uploads, ratings, profile details, and check-ins may be visible in Swipe10 depending on your settings and the feature used.
• Client Health data is shared with a provider workspace only after the client accepts the provider connection or otherwise authorizes sharing.
• We use service providers for hosting, storage, analytics, notifications, payments, AI processing, security, and support.
• Business sponsors, providers, Menu Scouts, and admins may see information needed for their dashboard role and permissions.

Health, provider, and activity data

Client Health may involve sensitive information. Depending on the provider relationship, HIPAA, business associate agreements, state health privacy laws, the FTC Health Breach Notification Rule, or other obligations may apply. Swipe10 requires providers to complete setup and outside review before launch, but this policy does not replace legal advice.

• Do not submit emergency medical information through Swipe10.
• Calories, macros, ingredients, activity, and recommendation outputs can be estimates and may be incomplete.
• If a covered provider or business associate uses Swipe10, they are responsible for their own HIPAA, BAA, consent, retention, and payer documentation obligations.

Your choices

• Toggle location and map visibility at any time.
• Edit or remove your uploads from your profile.
• Control notification settings, discovery alerts, taste profile settings, and content visibility where available.
• Pause or end Client Health sharing with a provider from the Client Health dashboard.
• Revoke device health permissions from your phone operating system when using supported installed apps.
• Use in-app tools to request account changes.

Security

We use reasonable safeguards to protect your data. No system is perfectly secure, so keep your credentials private and report any suspicious activity.

Retention, deletion, and children

We keep information as long as needed to provide the service, comply with legal obligations, resolve disputes, enforce agreements, support safety, and maintain records. Some information may remain in backups, audit logs, legal records, or provider records when required. Swipe10 is not intended for children under 13.

Contact and requests

Use Support in the app or email matthew.clockel@swipe10.com for privacy, account, deletion, or security requests. We may need to verify your identity before acting on a request.