Privacy Policy

Last updated: 26-06-01

Status: Draft scaffold for structured privacy/compliance review. Do not treat this Privacy Policy as production-final until MODMOUNT LLC completes attorney review, Google OAuth/GBP policy review, final retention/deletion decisions, and final subprocessor confirmation.

MODMOUNT LLC (“ModMount,” “we,” “us,” or “our”) operates ModMount.io, a review automation service for gun shops.

This Privacy Policy explains the expected categories of information ModMount.io collects, uses, stores, shares, protects, retains, and deletes. It is a draft scaffold and must be reconciled with the final implementation before real customer or provider data is used in a pilot or launch.

1. Scope

This Privacy Policy applies to ModMount.io public pages, signup, onboarding, protected app pages, provider connections, review request workflows, review reply workflows, widgets, social assets, reports, support, and related operations.

ModMount.com optic milling services are separate and may be governed by separate privacy terms.

2. Business Identity And Roles

MODMOUNT LLC is the expected business operating ModMount.io.

For Client account data and end-customer data, ModMount generally acts as a service provider or processor for the Client, while the Client remains responsible for the lawful collection, disclosure, and use of its own customer/order data.

Some operational data, billing records, security records, support communications, and business analytics may be processed by ModMount for its own legitimate business operations, legal compliance, security, and service improvement.

3. Information We Expect To Collect

3.1 Account And User Information

We may collect:

  • Business name, slug, website, primary contact, timezone, report recipient, and billing status.
  • User names, email addresses, roles, location access, authentication identifiers, and login/session data.
  • Team invitations, role changes, location assignments, and account-support history.

3.2 Google Business Profile Data

If a Client connects GBP, we may access, receive, or store:

  • Google account and authorization metadata needed to connect the service.
  • GBP account, location, and resource identifiers.
  • Location names, addresses, profile state, and selected paid locations.
  • Google reviews, review IDs, reviewer display names, ratings, review text, review timestamps, reply state, moderation state, rejection reasons, and related review metadata.
  • GBP performance metrics, notification settings, and API sync status where available.

3.3 Contact, Customer, And Order Data

We may process customer and order information from Clients, intake providers, webhooks, CSV imports, or manual entry, including:

  • Contact names, email addresses, phone numbers, source identifiers, and suppression status.
  • Order numbers, external order IDs, purchase timestamps, location, order status, amount/currency where provided, and raw intake payloads where needed for diagnostics.
  • Review Reactivation import rows, validation results, failure reasons, campaign links, and eligibility state.

3.4 Email Event And Suppression Data

We may process:

  • Review request subjects, recipients, touchpoints, statuses, send/delivery/delay/failure timestamps, click timestamps, bounce events, complaint events, opt-outs, provider suppression data, and manual Do Not Contact records.
  • ModMount-tracked review-link click data for reporting and lifecycle state.

Current intended scope disables Resend open tracking.

3.5 Reviews, Replies, Widgets, Assets, And Reports

We may process:

  • Matched and unmatched review lifecycle records.
  • AI-drafted replies, edited replies, approvals, denials, publish attempts, Google moderation state, and audit history.
  • Widget configuration, selected review IDs, visibility overrides, embed tokens, preview state, and public render state.
  • Review-to-social assets, captions, file metadata, report snapshots, weekly report delivery status, Drive links where configured, and report errors.

3.6 Brand, Files, And Support Data

We may process:

  • Logos, colors, fonts, brand voice, content style, templates, widget styles, and social/report settings.
  • Uploaded files, generated assets, storage paths, signed-link metadata, and internal file lifecycle state.
  • Support messages, setup notes, troubleshooting records, and operator audit events.

3.7 Billing And Checkout Data

Subscription checkout and manage-plan workflows are expected to run through ThriveCart or another approved payment provider.

We may receive billing identifiers, plan state, location count, payment status, subscription status, cancellation state, and related webhook events. We do not intend to receive or store complete payment card numbers.

3.8 Device, Usage, Security, And Operational Logs

We may collect IP address, browser/device data, route usage, event logs, API logs, webhook logs, error logs, authentication events, security events, audit entries, and diagnostic metadata.

4. Sources Of Information

We may collect information from:

  • Clients and Authorized Users.
  • Customer/order intake providers such as SyncSpider, webhooks, CSV imports, Zapier-style workflows, Shopify, WooCommerce, or manual entry where configured.
  • Google Business Profile and Google OAuth.
  • Email providers such as Resend.
  • Activation providers such as Encharge.
  • Billing providers such as ThriveCart.
  • AI providers such as OpenAI.
  • Hosting, database, storage, analytics, support, rendering, and operational providers.
  • Public route interactions, widgets, opt-out links, and support channels.

5. How We Use Information

We use information to:

  • Create, authenticate, secure, and support accounts.
  • Configure Client onboarding, provider connections, sender domains, locations, roles, and service readiness.
  • Receive and validate customer/order data.
  • Determine review-request eligibility and suppression state.
  • Send transactional review request emails and one configurable follow-up.
  • Sync Google reviews, draft replies, support approvals, publish approved replies, and track Google state.
  • Generate widgets, social assets, captions, and reports.
  • Provide support, troubleshooting, operator assistance, and account recovery.
  • Enforce plan, payment, role, location, and security gates.
  • Detect abuse, prevent unauthorized access, debug failures, audit actions, comply with law, and enforce terms.
  • Improve service reliability, usability, security, and performance.

6. Google User Data And GBP Data

ModMount.io must comply with the Google API Services User Data Policy and applicable Google Business Profile API policies.

Expected handling:

  • We request only permissions needed for prominent user-facing ModMount.io features.
  • We use Google data only to provide or improve those features, such as location selection, review sync, reply management, widgets, social assets, reports, support, and security.
  • We do not sell Google user data.
  • We do not use Google user data for ads, retargeting, interest-based advertising, credit decisions, unrelated surveillance, or unrelated data resale.
  • We share Google data with subprocessors only as needed to provide, secure, support, or improve visible service features, comply with law, or protect the service.
  • Human access to Google user data should be limited to Client-authorized support, security, legal, abuse, debugging, or aggregated internal operations.
  • Google review display content and raw Google payloads are intended to be cached temporarily and redacted or pruned no later than 30 calendar days after fetch.
  • Durable records may retain provider IDs, resource names, contact/location linkage, timestamps, provider status, match state, reply state, widget override state, aggregated metrics, and audit metadata.

Final implementation wording for Google API Content caching, redaction, widget display, and social reuse requires Google policy review and attorney review.

7. AI Processing

ModMount.io may send review text, star rating, brand voice, business context, location context, reply instructions, and related non-secret context to OpenAI or another approved AI provider to draft replies, captions, or structured outputs.

AI outputs may be stored with generation metadata, prompt version, model, usage, status, risk flags, redacted input/output, and audit records where needed.

Clients remain responsible for reviewing, approving, editing, publishing, or disabling AI-generated content according to account settings and these Terms.

8. Information Sharing And Subprocessors

We may share information with service providers and subprocessors as needed to provide, secure, support, improve, or operate ModMount.io.

Expected providers include:

  • Supabase: Database, Auth, Storage, Edge Functions, Row Level Security, and service backend.
  • Google / Google Business Profile: OAuth, GBP account/location/review/reply/performance data, Google Workspace, Gmail, Drive, and Apps Script reporting workflows where configured.
  • Resend: Transactional review request email delivery and email events.
  • Encharge: Review Reactivation activation delivery and event sync where configured.
  • OpenAI: AI reply and caption drafting.
  • SyncSpider: Managed order/customer intake where configured.
  • ThriveCart: Subscription checkout, manage-plan links, billing state, and affiliate billing events where configured.
  • Canva: Operational social asset production override where used.
  • Cloudflare: Hosting, Workers runtime, edge delivery, DNS/proxy/security services, and public routes.
  • Intercom: Help center, in-app/customer messaging, and support workflows where configured.

We may also share information with professional advisors, legal authorities, successors, or counterparties where required by law, business transfer, dispute, security, or rights-protection needs.

Final subprocessor list and data processing terms must be confirmed before real customer/provider data pilot.

9. Cookies And Similar Technologies

ModMount.io may use cookies, local storage, session storage, pixels, or similar technologies to:

  • Keep users signed in.
  • Secure sessions.
  • Remember theme or interface preferences.
  • Route signup, checkout, setup, provider callback, widget, and opt-out flows.
  • Measure usage and diagnose errors.
  • Support Intercom or similar support tools where configured.

Some features may not work if required cookies or storage are disabled.

10. Security

ModMount intends to use reasonable safeguards appropriate to the service, including:

  • HTTPS/TLS for data in transit.
  • Provider-side encryption where available.
  • Server-side token handling.
  • Private storage and signed links where appropriate.
  • Supabase Row Level Security and role/location-aware access controls.
  • Backend enforcement for privileged actions.
  • Secret handling through provider dashboards or secret stores.
  • Audit logging for sensitive actions.
  • Operator access controls for support workflows.

No security program can guarantee that unauthorized access, loss, misuse, or disclosure will never occur.

11. Retention, Deletion, And Disconnect

ModMount.io’s product default is archive-preserve for operational records. Visible delete actions may archive or hide data from the frontend rather than immediately hard-delete backend records.

Expected retention principles:

  • Do Not Contact, opt-out, hard bounce, complaint, and suppression records may persist to prevent unwanted future contact.
  • Contact, order, review lifecycle, reply, widget, asset, report, billing, audit, and support records may be retained as needed for service operation, compliance, security, billing, dispute handling, reporting, and suppression.
  • Google review display content and raw Google payloads are intended to be temporary and redacted or pruned no later than 30 calendar days after fetch.
  • Durable Google-related metadata may remain where needed for sync, audit, matching, reporting, and lifecycle state.

Clients must have a process to disconnect Google Business Profile access and stop use of the GBP integration. Final disconnect, disassociation, token revocation, export, deletion, and hard-delete procedures require legal/product approval before launch.

12. Client And Contact Rights

Depending on applicable law and account role, Clients may request access, correction, export, deletion, disconnection, or account closure.

End customers of Clients should usually contact the Client first because the Client controls its customer relationship and customer/order data. ModMount may help Clients respond to valid requests where required by law or contract.

Final state-specific privacy rights, verification process, response timelines, appeal rights, and authorized-agent process require attorney review.

13. Children

ModMount.io is intended for business use and is not directed to children. We do not knowingly collect personal information from children under 13.

14. International Transfers

ModMount.io is intended for business use by ModMount-approved Clients. Providers may process data in the United States or other jurisdictions where they operate.

Final international transfer terms require legal review if ModMount.io expands beyond the United States.

15. Policy Updates

We may update this Privacy Policy as the service, providers, laws, or data practices change.

Material changes should be posted with a revised “Last updated” date and, where appropriate, communicated through email, in-app notice, or another reasonable channel.

If Google data practices change materially, users may need to accept updated disclosures before the changed use begins.

16. Contact

For privacy questions, requests, or concerns, contact ModMount through the portal support channel or email help@modmount.com until a dedicated ModMount.io privacy/support inbox is finalized.

Copyright 2026 MODMOUNT LLC. All rights reserved.