Privacy Policy

1. BuildMint website

The website is a collection of HTML, CSS, local JavaScript, images, and video with a serverless endpoint for contact-form submissions. The inspected site code does not include an analytics platform, advertising tracker, or account system. It does not set a BuildMint analytics cookie.

The company cannot describe hosting-provider access logs or infrastructure retention from the repository alone. A hosting provider may process ordinary request information under its own configuration and policies.

2. Project and support enquiries

The Contact page collects the information you choose to provide, including your name, email address, company, phone number, service of interest, project or support details, budget range, target timeline, and consent to be contacted. The form sends this information through a Cloudflare serverless endpoint to BuildMint's designated email inbox. The site implementation does not store submissions in an application database.

Enquiries may remain in BuildMint's email systems according to the applicable mailbox and business-retention settings. You may request deletion of an enquiry through the Contact page, subject to information that may need to be retained for an active transaction, dispute, or other legitimate purpose.

Do not send passwords, payment-card details, or unnecessary sensitive information in an enquiry.

3. External content, security, payments, and links

• Cloudflare: Cloudflare hosts the site infrastructure, processes and validates contact submissions, and provides Turnstile abuse protection. Turnstile receives technical request information needed to assess whether a submission is legitimate.
• Google Workspace and Apps Script: after a contact submission passes validation, BuildMint's server sends the enquiry to a private Google Apps Script relay for delivery to the designated Google Workspace inbox.
• Google Fonts: company pages request the Manrope font from Google-hosted font domains, which means the browser connects to Google when those pages load.
• Product video: the current demonstration video is hosted as a local BuildMint site file rather than embedded from a third-party video platform.
• Lemon Squeezy: Facebook Auto Poster checkout, payment, taxes, receipts, ZIP delivery, and approved refunds are handled by Lemon Squeezy. BuildMint does not receive or store full payment-card details through the site or extension implementation.
• External links: when you follow an external link, the destination service applies its own privacy practices.

5. Extension permissions

storage

Stores group settings, campaigns, schedules, pacing, cooldowns, run state, and history in Chrome extension storage.

alarms

Registers campaign schedules and delayed posting steps while Chrome is running.

notifications

Allows the extension to show status notifications for the user-configured workflow.

https://www.facebook.com/* host access

Allows the content script to run on Facebook pages and lets the extension open and communicate with relevant Facebook group tabs.

The manifest does not request broad access to every website, Chrome browsing history, cookies, or identity permissions.

6. Information stored in Chrome

The current data model stores the following in Chrome local extension storage on the device:

• Facebook group URLs, labels, and descriptions
• Campaign names, enabled status, and selected groups
• Facebook Page post URLs and optional post text, including formatted text data
• Schedules and local-time configuration
• Minimum and maximum pacing values
• Campaign and group cooldown values
• Campaign run state and group posting history

An older extension version used Chrome sync storage for groups, post URLs, text, and schedules. The current implementation can read that legacy sync data during migration into the local data model. If Chrome Sync handled older data, Google’s policies and the user’s Chrome configuration apply to that syncing.

7. Information transmitted externally

The inspected extension source contains no external fetch, XMLHttpRequest, WebSocket, analytics, error-reporting, BuildMint API, Cloudflare entitlement, licence-validation, or subscription-check request.

Campaign information is used locally to drive the configured workflow on facebook.com. This necessarily places the configured post URL or text into Facebook’s interface when a posting action runs, where Meta’s terms and privacy practices apply. The implementation does not transmit that campaign content to a BuildMint server.

The extension has no direct payment functionality and receives no full card details. Purchase and download delivery occur on Lemon Squeezy outside the extension.

8. Authentication and Facebook access

The extension does not provide a separate Facebook login or authentication service. The user stays logged in through the normal Facebook session in Chrome. The extension interacts with pages that session can access. It does not bypass Facebook access controls.

9. Retention, deletion, and user choices

Current extension information remains in Chrome extension storage until it is changed, cleared, removed with the extension data, or otherwise handled by Chrome. Individual group and campaign records can be managed through the extension interface.

Uninstall behavior is controlled by Chrome. Chrome normally removes an extension’s local storage when the extension is uninstalled, but BuildMint cannot guarantee browser behavior or recovery. If legacy information was synced by Chrome, manage it through the relevant Chrome/Google settings.

Because the current extension sends no campaign or licence data to a BuildMint service, there is no corresponding BuildMint product-account database to delete. Purchase records and payment-related requests are handled through Lemon Squeezy and may also be reflected in support email.

10. Information security

BuildMint limits the current extension to the Chrome permissions and Facebook host access described above and does not include a remote licence or analytics service. No system can be promised completely secure. Keep Chrome updated, protect access to your device and Facebook account, and do not share credentials with support.

11. Children’s privacy

The BuildMint website and Facebook Auto Poster are not directed to children. BuildMint does not knowingly design the product to collect information from children.

12. Changes to this Policy

This Policy may be updated when the website, extension, purchase flow, or verified data practices change. The date above will identify the latest published revision.

13. Contact and questions

For privacy questions or a request concerning information sent to BuildMint, email hello@getbuildmint.com.

See the BuildMint Software Terms of Use and the Facebook Auto Poster product page.