Privacy Policy.

Short version: Hosted Proof helps you post your own job-site photos to your own Google Business Profile, Facebook, and Instagram. We access only what’s required to do that, only on your behalf, and only with your explicit consent via OAuth. We never sell your data, never use it for advertising, and never use Google or Meta user data to train AI models. The long version below covers exactly what we access, why, how we store it, and how to revoke it.

1. Who we are

Hosted Brands LLC (“Hosted Brands,” “we,” “us”) operates Hosted Proof at hostedproof.com (this marketing site) and at app.hostedproof.com (the product application).

Contact: [email protected]

2. Scope of this policy

This Privacy Policy covers both the marketing site (hostedproof.com) and the Hosted Proof application (app.hostedproof.com). The product application is what handles your photos, social-account connections, and post content; the marketing site collects only newsletter emails and server logs. Sections 5 and 6 below — covering Google and Meta user data — apply to the application.

3. What we collect on the marketing site

• Newsletter / contact form submissions. If you submit your email through the newsletter or contact form, we store your email address (and message, if applicable) to follow up.
• Server logs. Standard logs — IP address, user agent, request path, timestamp. Retained 30 days for debugging and abuse prevention.
• Cookies. A first-party session cookie if you log in. No third-party advertising cookies.

4. What we collect in the Hosted Proof application

• Account data. Your name, email, business name, password (hashed via bcrypt), and billing information (processed by Stripe; we never store full card numbers).
• Photos you upload. The before/after images you or your technicians submit. Stored on Cloudinary; you own them.
• Post content you create. The captions, hashtags, and scheduling metadata you build inside Hosted Proof.
• OAuth tokens. Refresh tokens for the social platforms you connect (Google Business Profile, Facebook, Instagram). Stored encrypted at rest.
• Operational metadata. Which platforms you’ve connected, which locations/pages you’ve authorized, which posts have been published.

5. Google User Data — Limited Use disclosure

Hosted Proof’s use and transfer of information received from Google APIs to any other app will adhere to the Google API Services User Data Policy, including the Limited Use requirements.

5.1 Which Google APIs and OAuth scopes we request

When you connect a Google account to Hosted Proof, we request the following OAuth scope:

• https://www.googleapis.com/auth/business.manage — required to read your verified Google Business Profile locations and to publish local posts on listings you manage.

We do not request any other Google OAuth scope. We do not request access to your Gmail, Google Drive, Google Contacts, Google Calendar, YouTube, or any other Google service.

5.2 What Google user data we access

Using the scope above, we access:

• The list of Google Business Profile accounts you own or manage (account name and ID).
• The list of verified business locations within those accounts (location name, address, location ID).
• The ability to create local posts on the locations you explicitly select inside Hosted Proof.

We never request, fetch, or store: your Google account password; reviews on your listings; insights / analytics data beyond what’s required to confirm a post succeeded; data from any Google service other than Business Profile.

5.3 How we use Google user data

Google user data is used only for the following purposes, all of which are user-facing features of Hosted Proof:

• To display the list of your verified GBP locations so you can choose which location(s) a given post should publish to.
• To publish, on your behalf and at your explicit direction, the local posts you create and approve inside Hosted Proof — to the specific location(s) you have selected.
• To confirm a post succeeded and surface that status in your Hosted Proof dashboard.

We do not use Google user data for any other purpose. Specifically, we do not use it for advertising, profiling, lead generation, content recommendations to third parties, or any purpose unrelated to the user-facing publishing feature you signed up for.

5.4 How we store Google user data

• OAuth refresh tokens are encrypted at rest in our database (AES-256) and only decrypted in memory at the moment a publish action runs.
• Location IDs and account IDs are stored so we can show you the right list of locations on your next session.
• Post content you create (caption, image references, scheduling metadata) is stored so your queue and history are visible in the app.
• We do not cache or duplicate Google-side reviews, insights, or any other listing data beyond what’s required for the publishing flow.

5.5 How we share Google user data

We do not sell, rent, trade, or otherwise transfer Google user data to any third party. The only sub-processors that touch any Google-derived data are infrastructure providers strictly necessary to operate the service:

• Railway — hosts our application servers and database (where encrypted refresh tokens live).
• Cloudinary — stores the photos you publish (Cloudinary never receives Google OAuth tokens).
• Stripe — processes billing (Stripe never receives Google OAuth tokens or any Google user data).

None of these sub-processors are permitted to use Google user data for any purpose other than providing infrastructure to Hosted Proof.

5.6 What we never do with Google user data

• We never sell Google user data.
• We never share Google user data with third parties for advertising or marketing.
• We never use Google user data for profiling, personalization, or behavioral analysis outside the publishing feature.
• We never transfer Google user data to AI or machine-learning models for training. Google user data is not used to train, fine-tune, or improve any generative AI model.
• We never post to GBP locations you have not explicitly authorized inside Hosted Proof.
• We never engage in mass posting, automated review solicitation, fake review generation, or any other behavior that would violate Google’s content policies or terms of service.
• We never allow humans on our team to read Google user data except (a) with your explicit consent for support, (b) when required by law, or (c) for narrow security investigations (abuse, fraud).

5.7 How to revoke Hosted Proof’s access to your Google account

You can revoke Hosted Proof’s access to your Google data at any time, two ways:

• From inside Hosted Proof: go to Settings → Connected Accounts → Google → Disconnect. We delete your stored OAuth refresh token immediately.
• From Google directly: visit myaccount.google.com/permissions, find “Hosted Proof,” and click Remove Access. Google will invalidate the refresh token; on our next attempted publish we will see the failure and clear our copy.

Revoking access does not delete any Hosted Proof posts that have already been published to your GBP locations; you can delete those individually from your Google Business Profile dashboard.

6. Meta User Data (Facebook + Instagram)

The same Limited Use principles apply to data received via Meta’s APIs. This section mirrors §5 for clarity.

6.1 Which Meta APIs and OAuth scopes we request

When you connect a Facebook account to Hosted Proof, we request the following permissions via Facebook Login:

• pages_show_list — to display the list of Facebook Pages you manage so you can select which Page to post to.
• pages_manage_posts — to publish posts to the Facebook Pages you have explicitly selected inside Hosted Proof.
• pages_read_engagement — to confirm a post was published and surface basic post status in your dashboard.
• instagram_basic + instagram_content_publish — to read your Instagram Business account information and publish posts to the Instagram Business account(s) linked to the Facebook Pages you have authorized.

We do not request any other Facebook or Instagram permission. We do not access your personal Facebook profile, your friends list, your private messages, your photos outside the Pages/Instagram accounts you have explicitly connected, or any other Meta service.

6.2 What Meta user data we access, use, store, and never do

Everything in §5.2–5.6 applies equally to Meta user data, with the substitutions: “Google Business Profile location” → “Facebook Page / Instagram Business account”; “Google API Services User Data Policy” → Facebook Platform Terms and Developer Policies. Specifically, we:

• Access only the Pages, Instagram accounts, and Page tokens needed to publish on your behalf.
• Use Meta user data only to publish content you create and approve inside Hosted Proof, to accounts you explicitly select.
• Store Page access tokens encrypted at rest, alongside the IDs of the Pages and Instagram accounts you authorized.
• Never sell Meta user data, share it with advertisers, use it for profiling, transfer it to AI training, post to Pages or Instagram accounts you have not authorized, mass-post, generate fake engagement, or otherwise violate Meta’s platform policies.

6.3 How to revoke Hosted Proof’s access to your Meta accounts

• From inside Hosted Proof: Settings → Connected Accounts → Facebook → Disconnect.
• From Facebook directly: visit facebook.com/settings → Business Integrations, find “Hosted Proof,” and click Remove. This invalidates our access tokens; on next attempted publish we detect the failure and clear our copy.

7. Third-party processors (full list)

We use the minimum vendors needed to run the service:

• Railway — hosts the web servers and Postgres database.
• Cloudinary — stores and transforms your uploaded photos.
• Stripe — processes subscription billing.
• OpenAI / Anthropic — generates caption drafts. We pass only the metadata you provide (e.g., service type, photo description). We do not send Google or Meta user data, personal data, or anything beyond what’s required to draft a caption. We do not allow these providers to use submitted content to train models (zero data-retention API endpoints where available).
• Resend / Postmark — transactional email (password resets, receipts).

8. Your rights

• Access: Email [email protected] with the subject “data access” — we’ll provide a copy of your data within 30 days.
• Deletion: Cancel your account in the app, or email “delete my data” — we remove your account, photos, post history, and OAuth tokens within 30 days. Encrypted backups age out within 90 days.
• Correction: Update profile fields in the app, or email us.
• GDPR / CCPA: EU/UK/California residents have access, correction, deletion, and portability rights — same email, same 30-day window.

9. Data retention

• Account data: Retained while your account is active, plus 30 days after deletion.
• OAuth tokens: Retained while you have an active connection; deleted within minutes of disconnecting.
• Photos and post content: Retained while your account is active; deleted within 30 days after account deletion.
• Server logs: 30 days.
• Billing records: Retained per US tax law (typically 7 years).

10. Security

OAuth tokens encrypted at rest (AES-256). TLS for all traffic. Passwords hashed with bcrypt. Database access restricted to application servers. Regular dependency security audits. We are not SOC 2 certified at this stage; we are a small, dogfooded product, and we are transparent about that.

11. Children

Hosted Proof is for business owners and their authorized employees. We do not knowingly collect data from anyone under 18.

12. International users

Hosted Proof is operated from the United States. By using the service you consent to the transfer of your data to the US. We do not currently offer EU/UK data residency.

13. Changes to this policy

Material changes will be announced via email to active users at least 14 days before they take effect. The “last updated” date at the top of this page is always current.

14. Contact & data protection inquiries

For any privacy, data, Google API, or Meta API related question:

• Email: [email protected]
• Mailing address: Hosted Brands LLC, Grand Rapids, Michigan, USA