Privacy Policy

Metter helps organizations create and publish mobile newsletters and, where enabled, send related email and SMS / text messages through automated workflows. This Privacy Policy explains what we store, why, how long we keep it, and how you can export or delete account data. By creating an account and agreeing to our Terms of Service, you authorize us to process your data as described here and in those Terms—to the fullest extent permitted by law.

Roles. If you are a Metter account holder or organization user, Metter is the business that provides the Service to you. If you receive an email or text from an organization that uses Metter, that organization is typically the sender and controller of your contact information; Metter processes delivery and related logs on that organization’s instructions. For texts you received from an organization, contact that organization or use the opt-out methods described in the message (including Reply STOP). See SMS and text messaging below.

How we use data

We use account, organization, content, contact lists, messaging delivery data, billing, analytics, security, support, and related service data to: operate and improve the Service; deliver messages you (or your organization) instruct us to send; communicate with you about the Service; prevent fraud and abuse; enforce our Terms; comply with law (including carrier and messaging-platform requirements); and establish, exercise, or defend legal claims. We may share data with subprocessors and professional advisors as needed for those purposes, and with authorities when legally required. We may create aggregated or de-identified data and use it for lawful product and business purposes. See the Terms (Section 5) for the authorization you grant at signup.

What we store

• Account: email, password hash (managed by our auth provider), optional name fields, sign-in sessions, and records of Terms/Privacy acceptance (version and timestamp).
• Organization: workspace name, membership roles, plan status, optional custom domain settings, optional postal mailing address used in commercial email footers, and SMS setup / registration checklist status when text messaging is used.
• Email and SMS lists: contact emails, phone numbers (when provided), names, consent or attestation timestamps your organization records, suppression and opt-out records (including SMS STOP), custom fields you define, and engagement events for messages you send through Metter (for example email opens/clicks and SMS delivery status).
• Newsletter and message content: drafts, published snapshots, workflow message templates (including SMS body text you author), and a short history of recent publishes. Content you upload (text, images, links, payment embeds) may include personal data — you control what you put in a newsletter or text.
• SMS delivery records: when SMS is enabled, outbound job metadata such as destination phone number, truncated message body, send status, attempt counts, error codes, provider message identifiers, and timestamps needed to deliver, troubleshoot, bill, and honor opt-outs.
• Analytics: pseudonymous engagement events for public links (ephemeral session id, page index, duration, clicks). Metrics are estimates and may be incomplete (for example when scripts are blocked). In our analytics event records we aim not to persist IP addresses, user-agent strings, or referrers; hosting or CDN providers may still process request metadata (such as IP) in operational logs under their policies.
• Product feedback: messages you submit through in-product feedback, which may include technical context such as a user-agent string to help diagnose issues.
• Support: Support Chat threads and error reports you submit (subject, message text, plan context). Human support is routed to [email protected]. Ask Metter (Help AI) answers are generated from Help knowledge and operator-managed documents; chat transcripts are ephemeral unless you escalate into Support Chat. Model inference may be processed by our AI infrastructure subprocessors under our instructions.
• Conversion tips: Growth+ rule-based layout and subject tips run on structured block summaries (ids, types, geometry). We do not store tip transcripts, and tips are not sent to generative model providers.
• Open API keys: hashed organization API keys and last-used timestamps for integrations that call /api/v1. Full secrets are shown once at creation and are not stored in plaintext.
• Operational backups: private, access-controlled daily organization backups used for disaster recovery. Storage providers may apply encryption at rest.
• Device drafts: the editor may keep a local copy in your browser (IndexedDB / localStorage) for resilience.

SMS and text messaging

This section applies when an organization uses Metter’s SMS / text messaging features (for example workflow texts). It is intended to meet common U.S. carrier, CTIA Messaging Principles, and TCPA-style disclosure expectations for programs that send SMS. Message and data rates may apply to texts you send or receive.

Who texts whom. Organizations that use Metter author message content, choose recipients from their own contact lists, and instruct Metter to transmit those texts. Metter provides the software and routes messages through a messaging provider (currently Twilio or a similar provider) and wireless carriers. Metter is not the “sender” of your organization’s marketing or informational texts to end recipients in the ordinary sense of TCPA / carrier programs—your organization is. Metter does not sell, rent, or share mobile phone numbers with third parties for those third parties’ own marketing.

Information used for SMS. To send and manage texts we (and our messaging subprocessors) process: mobile phone numbers; message content you provide; delivery and engagement metadata (status, timestamps, provider ids, error codes); opt-out / suppression records; and related organization identifiers. Inbound keywords (such as STOP) and limited webhook payload details may be logged so we can honor opt-outs and troubleshoot delivery.

Types of messages. Texts sent through Metter are typically organization-initiated messages related to newsletters, updates, reminders, or other content the organization configures in workflows. Message frequency varies by organization and workflow (for example, a sequence may send multiple texts over time). Metter does not control how often a particular organization chooses to message its list; organizations must disclose expected frequency in their own consent language where required.

Consent. Organizations—not Metter—are responsible for obtaining and documenting prior express consent (including prior express written consent where required for marketing texts) before adding a phone number to a list or sending SMS through Metter. Consent must be clear and conspicuous, identify the brand/organization, and disclose that message and data rates may apply, approximate frequency, and how to opt out. Do not reuse an email-only list for SMS without a separate SMS consent. Metter may require organizations to complete an in-product SMS registration checklist (including A2P 10DLC where applicable) and may suspend messaging for non-compliance, but Metter does not independently verify every end-user consent record.

Opt-out (STOP). End recipients may opt out of further SMS from an organization by replying STOP, STOPALL, UNSUBSCRIBE, CANCEL, END, or QUIT (or similar supported keywords) to the number that texted them. When Metter’s inbound webhook is configured, we process those keywords and place the number on an organization-level SMS suppression list so future Metter-routed texts from that organization are blocked. Opt-out is processed as promptly as practicable and in any event in line with applicable law and carrier rules. Organizations must also honor opt-outs they receive outside Metter and must include clear STOP / HELP language in program messages as required. Reply HELP (or contact the organization named in the text) for assistance with that organization’s program; Metter account holders may also email [email protected].

Example consent language organizations may adapt (not legal advice): “I agree to receive recurring automated text messages from [Organization] about news and updates. Msg frequency varies. Msg & data rates may apply. Reply STOP to opt out, HELP for help. Consent is not a condition of purchase.”

No mobile information sale / sharing for third-party ads. We do not sell mobile information. We do not share mobile information with third parties or affiliates for those parties’ own promotional or marketing purposes. We share phone numbers and message content with messaging providers and carriers solely to deliver texts, prevent abuse, honor opt-outs, bill usage, and comply with law and platform rules.

Children. The Service is for business and organizational use by adults. Organizations must not use Metter SMS to knowingly text children in violation of applicable law.

If you received a text. Contact the organization identified in the message, reply STOP to opt out of that organization’s texts through Metter, or email [email protected] and we will help route your request where appropriate. Metter may not be able to identify every sender without the phone number, approximate time, and message content.

What we do not store

Metter does not store payment card numbers. Organization billing uses Stripe Checkout; newsletter payment embeds open the processor you choose (for example Stripe Payment Links) in an iframe. Card details stay with that processor.

How links work

Public publish links show only the edition you intentionally freeze. Password-protected or secret preview links are capability URLs — anyone with the link (and password, if set) can open that preview. They are not a guarantee of confidentiality. Drafts otherwise stay inside your organization. We may disable links when required under our Terms or law.

Third-party services on marketing pages

Our marketing site may load fonts or scripts from third-party CDNs (for example Google Fonts or similar). Those providers may receive technical request data such as IP address. We do not use marketing-site cookies for advertising analytics today; if that changes, we will update this Policy.

Retention

• Recently deleted newsletters: restorable for 3 days, then purged.
• Operational org backups: kept for about 14 days.
• Raw analytics events: kept for about 90 days.
• SMS delivery jobs and related logs: retained as needed to operate messaging, billing, abuse prevention, and opt-out compliance, then deleted or aggregated under ordinary retention practices.
• SMS suppressions (STOP): retained so we can continue to honor opt-outs, and may be kept after other contact data is removed where needed for compliance.
• Active account, org, and newsletter data: until you delete them.
• Limited records may be retained longer where needed for legal compliance, disputes, security, fraud prevention, tax/accounting, carrier audits, or proof of Terms acceptance.

Subprocessors

We use carefully selected third-party processors for hosting and CDN, authentication and databases, transactional email (such as welcome and password-reset messages), campaign email delivery when Metter Email is enabled for your organization (via Amazon SES or a similar provider), and subscription checkout. Checkout for paid plans is processed by Stripe. When SMS / text messaging is enabled, delivery involves a messaging provider (such as Twilio) and wireless carriers; those parties receive phone numbers and message content as needed to route texts. SMS plans are billed separately from Metter subscriptions and may change at any time under our Terms. When you embed YouTube or other third-party links, those services receive viewer requests directly. For a current list of infrastructure subprocessors, email [email protected].

Legal acceptance

When you create an account, we record that you agreed to our Terms of Service and this Privacy Policy (including the terms version and acceptance time stored with your account metadata).

Your rights

In Dashboard → Settings you can export account data (profile, organization membership, and newsletter metadata; media files and full newsletter bodies may be omitted) or delete your account. Deletion removes your Metter account and, when you are the sole owner of a workspace, that workspace’s newsletters, analytics, and org backups from active systems. Your Support Chat threads are purged with the account. Stripe may retain payment records under its own policy. Messaging providers and carriers may retain transmission logs under their policies. We may retain limited records where required for legal compliance, dispute resolution, opt-out enforcement, or security (for example fraud prevention or proof of terms acceptance), as described above.

Where privacy laws grant you rights to access, correct, delete, or opt out of certain processing, contact us and we will respond as required by applicable law. Exercising some rights may limit or end your ability to use the Service. For SMS opt-out by end recipients, Reply STOP as described above, or contact the sending organization.

First-party Metter text program

Metter is a product of Stakkivation LLC. First-party program texts are sent as Metter: and may include Metter account, trial, billing, product updates, and occasional review or product messages. This is separate from newsletters a customer organization sends to its own list. Opt in at https://www.metter.pro/sms. Message frequency varies. Message and data rates may apply. Reply STOP to opt out. You must be 18 or older to opt in. Consent is not required to buy or use this website.

No mobile information will be shared with third parties/affiliates for marketing/promotional purposes. Information sharing to subcontractors in support services, such as customer service, is permitted. All other use case categories exclude text messaging originator opt-in data and consent; this information will not be shared with any third parties.

Contact

Privacy questions: [email protected]. Product support: [email protected]. Legal questions: [email protected]. For a newsletter or text you received, contact the organization that sent it (or Reply STOP for SMS). Inbound delivery depends on DNS/MX (see ops notes); mailto links alone do not prove mailboxes are monitored.

This Policy describes Metter’s practices and is not legal advice to organizations about their own TCPA, CTIA, state, or carrier compliance programs. Organizations that send SMS remain responsible for their consent, content, and disclosures.