Acceptable Use Policy

Purpose

This Acceptable Use Policy protects Formerie, customers, public form submitters, delivery providers, and the broader internet from abusive, unlawful, deceptive, or unsafe activity.

It applies to Formerie websites, customer applications, APIs, SDKs, hosted forms, embedded forms, delivery channels, integrations, support channels, and any content or traffic processed through the service.

Prohibited content and activity

Do not use Formerie to create, collect, transmit, store, deliver, or facilitate:

• Spam, unsolicited bulk messaging, list bombing, or mail abuse.
• Phishing, credential theft, impersonation, deceptive login flows, or brand misuse.
• Malware, exploit payloads, command-and-control traffic, or malicious links.
• Harassment, threats, hate, targeted abuse, doxing, stalking, or intimidation.
• Fraud, scams, deceptive business practices, or misleading submissions.
• Illegal goods, services, content, or instructions.
• Content that infringes intellectual property, privacy, publicity, or other rights.
• Sexual exploitation, non-consensual intimate content, or abuse of minors.
• Collection of highly sensitive data without Formerie’s written approval and appropriate safeguards.
• Activity that violates applicable laws, regulations, provider rules, or Formerie policies.

Platform abuse

Do not attempt to:

• Bypass rate limits, origin checks, CAPTCHA or challenge systems, authentication, authorization, plan limits, or tenant boundaries.
• Probe, scan, overload, attack, scrape, reverse engineer, or interfere with Formerie systems.
• Use stolen, leaked, shared, or unauthorized credentials, tokens, API keys, domains, or provider accounts.
• Hide, falsify, or manipulate headers, domains, sender identities, metadata, logs, or attribution.
• Use Formerie as an open relay, spam relay, credential drop, malware drop, or abuse reporting evasion tool.
• Degrade Formerie deliverability, provider reputation, availability, or security posture.

Sensitive data restrictions

Do not collect highly sensitive information through Formerie unless Formerie has explicitly agreed to the use case in writing and appropriate contractual, legal, and technical controls are in place.

Examples may include:

• Payment card numbers or bank credentials.
• Government identifiers.
• Health, genetic, biometric, or precise location information.
• Criminal records or background-check information.
• Authentication secrets, passwords, private keys, or recovery codes.
• Children’s information.
• Other sensitive categories under applicable law.

Email and delivery abuse

Delivery channels must be configured for legitimate transactional purposes.

Do not use Formerie delivery workflows to send marketing campaigns, purchased-list messages, deceptive confirmations, unwanted notifications, or messages to recipients who should not receive them.

Customers are responsible for recipient configuration, reply-to behavior, webhook endpoints, templates, and provider compliance.

Domain and brand use

Do not connect domains, forms, templates, or content that impersonate another organization, mislead submitters, hide the identity of the form operator, or violate third-party rights.

Custom domains must be controlled by the customer and must comply with Formerie verification and routing requirements.

Enforcement

Formerie may throttle, reject, quarantine, suspend, disable, remove, or investigate activity that appears abusive, risky, unlawful, harmful, or inconsistent with this policy.

Formerie may also preserve records, notify affected parties, contact providers, cooperate with law enforcement or regulators, or terminate access where appropriate.

Where practical and safe, Formerie may provide notice and an opportunity to remediate. Immediate action may be taken without notice when necessary to protect people, systems, data, deliverability, or legal obligations.

Reporting abuse

Abuse reports can be sent to hello@formerie.com until a dedicated abuse contact is published.

Useful reports include the relevant domain, form URL, timestamp, request headers where appropriate, message samples, screenshots, and a description of the concern.