Clear about data. Clear about limits.
This is the shared privacy page for SendForge products. Use the product links below to jump to the policy section that applies to the product you are using.
January 16, 2026
Contact: privacy@sendforge.app • support@sendforge.app
Our products
SendForge is the umbrella brand. Different products may handle different categories of data depending on what the product does.
SendForge Messaging
The following section applies to SendForge Messaging and preserves the existing policy substance already live on this page.
Information we collect
- Account details such as name, email, and company.
- Billing metadata from payment processors.
- Messaging data required to deliver messages and track status.
- Technical usage data such as IP, browser, and device analytics.
How we use it
- Operate and improve the service.
- Deliver SMS and email messages.
- Enforce usage limits and prevent abuse.
- Comply with telecom, provider, and legal requirements.
Compliance safeguards
We may monitor complaint rates, opt-out activity, unusual sending behavior, and carrier requirements to protect the platform. We do not sell message content or use it for advertising.
Retention and sharing
We retain data only as long as necessary for service delivery and compliance. We may share data with hosting, telecom, email, payment, and legal service providers as needed to operate the platform.
TabForge
This section applies specifically to the TabForge browser extension and related TabForge product surfaces.
What TabForge stores
- Shortcut layout, pages, packs, and the current workspace are stored locally in the browser.
- If the user chooses to save a named configuration, that saved configuration may be stored with the user’s SendForge account so it can be loaded later.
- Authentication state and token if the user signs in.
- Basic account linkage needed to verify purchased features.
How TabForge uses it
- Persist the user’s new-tab workspace across browser sessions.
- Restore shortcut pages, saved layouts, and purchased pack access.
- Verify account access and entitlements through the SendForge backend when the user signs in.
What TabForge does not do
- Does not collect browsing history.
- Does not read page content from arbitrary websites.
- Does not track keystrokes.
- Does not sell user data.
- Does not load or execute remote hosted code.
Extension-specific handling
TabForge uses chrome.storage.local to store the current workspace configuration locally. If a user signs in,
login credentials are sent securely to the SendForge backend and a token is stored locally so the extension can
verify account access and purchased features. If the user manually saves a named configuration, that saved
configuration is sent to the SendForge backend and associated with the user’s account for later manual loading.
Remote code and permissions
TabForge does not download and execute remote code. Executable extension logic is packaged with the extension. Network requests are used only for account authentication, entitlement verification, and user-initiated saving or loading of named configurations.
Sharing and retention
TabForge workspace data is primarily stored locally in the user’s browser. Account and entitlement checks are handled through SendForge systems only as needed to provide sign-in and paid feature access.