How feature terms work
- A team owner or admin who turns a feature on, in the Console or through the API, accepts its terms for the team.
- Where the Console or API asks for acceptance first, we record who accepted, when, and which version. Each version has a key, such as hms-v1, shown in its section below.
- Each set of terms applies to the scope shown in its section: the team, a project, a customer or a number, in some cases with project or team defaults.
- If we change the terms in a way that affects what you accepted, we ask you to accept the new version, where we record acceptance, before the feature stays on for new work.
- Turning a feature off needs no acceptance. Each section says what happens when you turn it off.
- For the feature they cover, these terms win over the Terms of Service if the two conflict. A signed order form and, for personal data, the DPA still come first.
The features with their own terms are:
Ban Credit waiver
Some features waive Ban Credit for the numbers that use them. Their sections say so. For those features this rule applies:
While the feature is on, and for 30 days after you turn it off, a ban on an affected number is not covered by Ban Credit. A claim for that ban opens as denied with the reason. Other refunds under the Refund Policy are unaffected.
The 30 days are the lookback used for Ban Credit coverage and calculation, not a deadline for reporting a ban. Where a feature counts the 30 days from a send instead of from turning it off, its section says so.
Hosted message storage
- Version
hms-v1- Applies to
- Team, project, customer or number
- Ban Credit waiver
- No
When hosted message storage is on, Polymorfa stores the messages your numbers send and receive from that moment on, with their media and conversation details. Older messages are not added. Data is stored in the data region you choose and kept for the retention period you set: 30 days unless you change it, and at most 7 years. Media follows its own retention period.
Your team members with access to the numbers can read stored conversations in the Console and through the API. Polymorfa support can view selected stored messages only through a logged support process. You are the controller of this data, or a processor for another controller. You confirm you have a lawful basis to store these conversations and that your privacy notice tells your contacts.
Stored data counts toward your WhatsApp data usage and is billed per GB-month above your allowance.
Turning it off stops new storage at once. Messages already stored keep their retention period and are then deleted, unless you delete them sooner. Deleting a number deletes its stored messages.
Regional Contacts
- Version
regional-contacts-v1- Applies to
- Team, project, customer or number
- Ban Credit waiver
- No
When Regional Contacts is on, Polymorfa keeps a directory of the contact profiles your numbers see on WhatsApp: names, profile details and the phone number or WhatsApp ID. Your team can also edit them. The directory is stored in the data region you choose. It is kept until you delete it, or for the number of days you set.
Team members with access to the numbers can read and edit profiles in the Console and through the API. You are the controller of this data, or a processor for another controller, and confirm you have a lawful basis to keep it.
Turning it off stops new capture. Stored profiles keep their retention period and are erased with their number.
Full history delivery
- Version
history-delivery-v1- Applies to
- Number, with project and team defaults
- Ban Credit waiver
- No
When full history delivery is on, a number sends you the chat history WhatsApp shares with a newly linked device. Polymorfa passes it to your webhooks as it arrives. WhatsApp decides how much history it shares. When a full request is set, Polymorfa asks WhatsApp, as the device is linked, for up to 30 days and 64 MB of history. These are the limits of the request, not a promise of what WhatsApp sends.
Polymorfa does not keep message content from history. It keeps message IDs and routing details for as long as the number exists, and delivery records for 30 days after delivery completes or expires, or 90 days after their last update when delivery fails or is never confirmed. A cleanup that runs every few hours then deletes them. Once history reaches your systems, you are responsible for storing and protecting it.
The person who links the phone can see and refuse history sharing on the pairing page. Turning this off returns to metadata-only processing for new history. It does not recall history already delivered.
Ban Credit device evidence
- Version
ban-credit-evidence-v1- Applies to
- Project
- Ban Credit waiver
- No. This feature supports claims.
When device evidence is on, Polymorfa measures the other devices linked to each number in this project: the phone, browsers and other tools. It keeps hourly counts only: messages sent, people reached, first-contact messages, peak sending rates, active hours, and the device class. It never records messages, recipients, phone numbers, or device names from those devices.
Polymorfa uses this only to decide Ban Credit claims. It does not affect health scores or findings. Evidence is kept as long as the safety measurements it arrives with. Your team and Polymorfa reviewers can see the summary on a claim.
Without evidence, a claim can still be filed but its verdict is inconclusive.
Turning it off deletes the stored measurements for the project at once. Claims already filed keep their evidence summary.
Simultaneous calls
- Version
simultaneous-calls-v1- Applies to
- Number
- Ban Credit waiver
- Yes, while on and for 30 days after you turn it off. See the Ban Credit waiver.
Simultaneous calls lets this number hold any number of calls at once, incoming, placed and from campaigns. WhatsApp's own apps hold one call at a time, so this is unusual behavior for a WhatsApp account and can raise the risk of a ban. Turning the setting on is when you accept this.
Ban Credit does not cover this number while the setting is on, or for 30 days after you turn it off. A claim for a ban in that time opens as denied. Other refunds under the Refund Policy are unaffected.
Each call is billed and rate limited as it would be on its own. Polymorfa support can turn the setting off if it causes harm. Turning it off applies to new calls within about a minute and does not end calls in progress.
Interactive messages on linked devices
- Version
ld-interactive-v1- Applies to
- Project, with a number override
- Ban Credit waiver
- Yes, for 30 days after the last interactive send. See the Ban Credit waiver.
This lets linked-device numbers send buttons, lists, product messages, Flows and other interactive messages. Polymorfa treats interactive messages from a linked device as higher-risk sending.
Ban Credit does not cover a number that sends an interactive message, for 30 days after its last interactive send. A claim for a ban in that time opens as denied. Other refunds under the Refund Policy are unaffected.
Official API numbers are not affected. BanSafe still counts these sends toward the number's daily allowance.
Turning it off refuses new interactive sends from the API, campaigns and the Console. The 30-day period still runs from the last send.
Presence and typing observation
- Version
presence-observation-v1- Applies to
- Project, with a number override
- Ban Credit waiver
- No
Presence observation lets your numbers receive when contacts come online, go offline, and start or stop typing, after you subscribe to a contact. In events mode Polymorfa passes each change to your webhooks. In cache mode it also keeps the latest state in memory for lookups. Label project mode keeps a stored copy of the number's chat labels.
Presence and typing reveal personal behavior. Use them only to run your service for people who are in conversation with you, never to monitor or profile them. You are the controller of this data, or a processor for another controller, and responsible for your webhook copies.
Turning it off stops new events and clears cached presence and typing state.
Campaign link tracking
- Version
link-tracking-v2- Applies to
- Team
- Ban Credit waiver
- No
Link tracking replaces links in campaign messages from linked-device numbers with a Polymorfa short link per recipient. Polymorfa counts opens per link and recipient. A link preview can count as an open, so counts are an estimate.
Open counts are kept for 400 days after a recipient's first open. Each recipient's link stops working 90 days after Polymorfa creates it, when the message is prepared for sending, not when it is delivered. Your team sees counts in the Console and through the API.
Your privacy notice must tell recipients you measure link opens, where the law requires it.
Turning it off stops tracked-link edits, new launches with tracked links and link reports. Links already sent keep redirecting until they expire.
Call media to your systems
- Version
call-media-v1- Applies to
- Project
- Ban Credit waiver
- No
This sends call audio and video between WhatsApp and the systems you connect: your app, a voice agent, or a SIP trunk to your phone system. Polymorfa does not record call audio or video. Your systems receive the full media, so any recording, transcription or AI processing happens there and is your responsibility.
You must tell callers, and get consent where the law requires it, before you record, transcribe or let an automated agent answer. A SIP trunk is your own system. It cannot reach emergency services through Polymorfa.
Polymorfa keeps call records and events for your call data retention period.
Turning it off stops new media connections. Calls in progress continue until they end.
Voice Automation provider keys
- Version
voice-automation-v2- Applies to
- Team
- Ban Credit waiver
- No
Voice Automation stores an audio library and generates speech through the provider you choose, OpenAI or ElevenLabs, using your own provider key. The text you submit goes to that provider under your contract with it. Polymorfa stores your key encrypted and shows only its fingerprint.
Uploaded and generated audio stays in your library until you delete it, or until the optional retention period you set for it ends, from 1 to 3,650 days after it was added. You cannot delete audio while a campaign or flow uses it, and expired audio is deleted only once nothing uses it. Your team can play and manage it in the Console and through the API.
You must have the rights to any voice and audio you use. Do not clone or imitate a person's voice without their consent.
Turning it off refuses new uploads, speech and key changes. Existing audio and keys stay available for review and deletion.
Referral group sends
- Version
referral-group-send-v2- Applies to
- Number, accepted once in the Console
- Ban Credit waiver
- No
This posts your referral message to up to 50 WhatsApp groups from a number you choose. Each post is a normal message from that number and counts toward its daily allowance. Polymorfa does not store the group list.
Posting the same promotional message to many groups can lead members to report the number. Send only to groups where this message is welcome.