1. Who these Terms cover
"Polymorfa", "we" and "us" mean SOFTIUM Sàrl, Rue des Musées 58, 2300 La Chaux-de-Fonds, Switzerland, UID CHE-303.047.962. "You" means the business or organization that uses Polymorfa. The person who accepts these Terms confirms that they can bind that business.
Polymorfa is offered for business use, to businesses and developers, and not to consumers. By accepting these Terms, you confirm that you act for a business, trade or profession, including as a sole trader. Consumer-protection rules for private purchases therefore do not apply to the contract. These Terms do not remove any mandatory consumer right that the law still gives you.
These documents are part of the contract:
- the Acceptable Use Policy, which lists what you may not do with Polymorfa;
- the Data Processing Addendum ("DPA"), which applies whenever we process personal data on your behalf;
- the Refund Policy;
- the Feature terms for each feature your team turns on that has them, which add conditions for features that store more data or carry more risk;
- the subprocessor list;
- any order form or written agreement you sign with us, such as an Enterprise agreement.
If two documents conflict, the mandatory transfer clauses that the DPA incorporates, such as the EU standard contractual clauses and the ANPD clauses, prevail over everything else, including an order form. Otherwise a signed order form wins, then the DPA for anything about personal data, then the Feature terms for the feature they cover, then these Terms, then the policies. Our Privacy Policy explains how we handle personal data that we control, such as your account details.
2. Accounts, teams and credentials
- You must be at least 18 years old to create an account.
- Give accurate account, team and business-profile details and keep them current.
- A team is the customer account. Team owners and admins can invite members, create projects and API keys, and spend credits. Only owners can delete the team. We follow instructions from owners and admins as instructions from you.
- You are responsible for everything done with your accounts, API keys, project tokens and client credentials. Keep them secret, grant each key only the scopes it needs, and revoke keys you no longer use.
- Tell us at security@polymorfa.com as soon as you suspect a credential leak or unauthorized access. We may revoke a key that we find exposed, for example in a public repository.
- Keep more than one owner on your team, and keep each owner's contact details current.
- If access to a team is lost or someone disputes who may act for your organization, we may ask for evidence of the organization's identity and of the requester's authority, preserve relevant records and temporarily restrict disputed administrative actions. We do not decide ownership disputes. We may require a joint instruction from the people involved or a binding order before we act. This does not allow us to disclose data to someone whose authority is not established.
3. The Service
Polymorfa gives you an API, a web console, SDKs, a command-line tool and related features for connecting WhatsApp numbers and sending, receiving and managing WhatsApp messages and calls (the "Service"). The documentation at docs.polymorfa.com describes each feature and its limits.
Some features are marked beta, preview or early access. We provide them as they are, they may change or end without notice, and they are not covered by any service level. Parts of Polymorfa are in a closed beta. We decide who gets access.
Polymorfa connects WhatsApp calls only. It is not a telephone service, does not provide phone numbers and cannot call emergency services. A PBX or SIP trunk you connect is your own system, and its carrier is responsible for any emergency calling it supports. Make sure the people who use your service have another way to reach emergency services.
We change and improve the Service over time. If we remove a feature you pay for, we will give you at least 30 days' notice, except where a law, a security issue, or a change made by WhatsApp or Meta forces a faster change.
4. WhatsApp and Meta
Polymorfa is independent. We are not affiliated with, endorsed by, or sponsored by WhatsApp LLC or Meta Platforms, Inc. "WhatsApp" is their trademark.
Polymorfa can connect a number in two ways: as a linked device, using the same multi-device protocol that WhatsApp Web uses, or through Meta's WhatsApp Business Platform with your own Meta credentials. In both cases WhatsApp and Meta control the network, not us. They can change the protocol, limit features, or restrict or ban a number at any time and for reasons they do not share.
You choose the connection mode. You choose how each number connects and you accept the risks of that choice. WhatsApp or Meta may restrict linked-device connections, or business use of them, at any time. You are responsible for checking that your use of each connection mode fits the WhatsApp and Meta terms that apply to you.
You carry the risk of bans and restrictions. WhatsApp or Meta may act against your numbers or accounts. Examples are a restriction, ban or disconnection; rate or messaging limits; the loss of a number, or of its contacts and chat history; a disabled WhatsApp Business Account or Meta Business portfolio; lost verification; rejected templates; or a lower quality rating. You bear every consequence of such an action, including lost revenue and the cost of onboarding again or replacing numbers and accounts. This applies whatever caused the action, except where the law does not allow us to exclude our liability, such as for our own intent or gross negligence.
- You are responsible for complying with the WhatsApp and Meta terms and policies that apply to your numbers and accounts.
- Ban Credit is the only thing we give for a ban. It applies only to eligible numbers and only as its published terms describe. It returns Polymorfa credits, not money.
- BanSafe, Safe Mode, warm-up plans and health scores are estimates. They reduce risk but do not guarantee that a number will not be restricted or banned. Their results and recommendations do not move this risk to us.
- We do not defend, indemnify or reimburse you for any claim, demand, enforcement action, fee or penalty that WhatsApp or Meta brings against you, and we have no duty to take part in it. The only exception is any part that our intent or gross negligence caused.
- We may share information with WhatsApp or Meta about abuse of their network, as the Acceptable Use Policy says.
- When you message a WhatsApp user, WhatsApp and Meta process that message under their own terms and privacy policies. They are not our subprocessors.
5. Your data and your recipients
"Customer Data" means the content and data that you or your users send to the Service or that the Service receives for you: messages, media, contacts, call records, campaign lists, webhook payloads and similar data. You keep all rights in it. You give us permission to host, copy, transmit and otherwise process Customer Data only to run, secure and support the Service for you, and as the law requires.
For Customer Data, you are the controller (in India, the data fiduciary), or a processor acting for another controller, and we are your processor. The DPA applies automatically; you do not need to sign it separately.
You are responsible for:
- having a lawful basis, and where required the recipient's opt-in consent, for every message and call you send;
- having every notice, consent and permission the law requires to access, intercept, monitor, record, sync and store communications through the Service. This includes the other people in chats you sync and on calls you bridge, record or stream, and any WhatsApp account you link that is not your own. Our consent screens, safety tools and settings do not give you that permission or show that you have it;
- honoring opt-out requests promptly;
- the content of your messages and any instructions your systems give the API;
- telling the people you message how you use their data, in your own privacy notice;
- choosing where your data is stored. We store it in the European Union by default; numbers in our Brazil messaging region keep their WhatsApp data in Brazil, and Enterprise customers can agree Swiss storage in writing, as the Privacy Policy explains.
Unless you turn on hosted message storage for a number, we do not keep a history of the messages you send and receive. If you turn it on, we store that number's messages in the number's region for the retention period set for it. Message events waiting for delivery are deleted after 24 hours. Events that fail processing may be held for up to a further 24 hours for troubleshooting and are then deleted automatically. Media files you upload through the API to send later stay stored until you delete them.
We do not use the content of your communications for our own purposes. Content means message text, media, call audio and video, and the contents of synced chats. We process content only to provide the features you use, at your direction, for example to deliver it, store it, convert media formats or add the tracked links you set up. We do not sell it, and we share it only as those features require, such as with WhatsApp to deliver a message or with the subprocessors on our list. We do not use it to train AI models, for advertising or to build profiles. Our staff do not access content, except to answer a support request you make, to investigate a security incident, or when the law requires it.
Our safety and analytics features use measurements derived from your traffic, such as counts, timings, length ranges and error codes. These measurements contain no content or contact identities. We use them to run, secure and improve the Service.
6. Acceptable use
Use Polymorfa only as the Acceptable Use Policy allows. In short, no spam, no messaging without consent, no fraud or phishing, no illegal content, and no attempts to break, overload or get around the Service or its limits. We may suspend a number, key, project or team that breaks it, as described in section 10.
7. Prices, credits and payment
Payment processing. We use Stripe to process payments. Polymorfa manages your credit purchases, billing settings, invoices and refunds under these Terms and the Refund Policy. Earlier purchases retain the payment terms and original provider shown for those purchases.
- A team is either on Free or Pay-As-You-Go. Free includes the projects, numbers and usage listed on the pricing page at no charge. Enterprise terms are agreed in an order form.
- Pay-As-You-Go is prepaid. You buy credits in advance, and we deduct them for numbers and usage at the prices shown in the console and on the pricing page when the charge happens.
- Add-ons are separate monthly subscriptions. We charge them to your team's payment method in money, not credits, at the price shown before you subscribe.
- Credits are not money. They have no cash value, cannot be transferred to another team, and can only be used for Polymorfa. Promotional or bonus credits expire as stated when we grant them.
- Numbers are charged per 24-hour window. If your balance cannot fund the next window, we suspend that number and keep its pairing until you add credits.
- Add-ons renew each monthly billing period on the same payment method until you cancel. If a renewal payment fails, you get the recovery period shown in the console before the add-on ends.
- Prices exclude taxes. Applicable taxes are calculated and shown before you confirm your purchase.
- We may change prices. For an increase, we give Pay-As-You-Go teams at least 30 days' notice by email. Credits already bought keep their value in credits.
- If you open a chargeback or payment dispute, we may put the team on hold while we review it.
Refunds follow the Refund Policy.
8. Availability and support
We work to keep Polymorfa available and publish incidents at status.polymorfa.com. Unless you have an add-on or order form that includes a service level, we do not commit to an uptime percentage. Where a service level applies, its terms are provided with the add-on or order form that includes it, and its credits are your only remedy for missing it.
Support is available at support@polymorfa.com and in the console. Response times depend on your support add-on.
9. Your responsibilities for your integration
You are responsible for your own systems: the endpoints that receive our webhooks, how you store data you pull from the API, and the apps you build with our SDKs. Verify webhook signatures, handle retries and duplicate events, and keep backups of data you need to keep.
AI systems and agents. You can connect an AI system or agent to Polymorfa through our MCP server or the API. It acts with the credential you give it and only within that credential's scopes. Depending on those scopes, it can read messages, chats and events, send messages, and manage customers, campaigns, templates and webhooks. It cannot create Polymorfa credentials. When you connect one:
- you authorize what it does within the permissions you grant, and its actions count as yours;
- you choose its provider and control its instructions;
- you are responsible for reviewing its consequential actions, such as sending messages, launching campaigns or deleting data;
- tool results can contain text written by WhatsApp users, contacts or other third parties, including instructions your AI system should not follow. Our MCP server marks such results as untrusted data, but you are responsible for how your AI system handles them;
- data your AI system receives from Polymorfa and sends to its provider is sent on your instruction, and your duties on lawful basis and confidentiality apply to it.
This does not allow Polymorfa to train AI models on your communications or to use Customer Data beyond what section 5 allows.
10. Suspension
We may suspend all or part of your access if:
- you break these Terms or the Acceptable Use Policy;
- your use puts the Service, other customers, WhatsApp users or us at risk, for example a compromised key or a spam run;
- your use causes, or risks causing, action by WhatsApp or Meta against us, our access to their network or services, or other customers;
- a payment fails, is reversed, or is disputed;
- a law, court or authority requires it.
We limit a suspension to what is needed, usually the affected key, number or project first. We tell you why and how to fix it, before suspending when we can and otherwise right after. We lift the suspension once the cause is fixed.
11. Ending the contract
- You can stop using Polymorfa at any time. Deleting your team, or asking us in writing to close it, ends the contract for that team. If you cannot delete a team in the console, we close it on request.
- We can end the contract for any reason with 30 days' written notice. If we do, we refund the purchase price of your remaining paid credits.
- We can end it immediately if you seriously or repeatedly break these Terms or the Acceptable Use Policy, if you do not fix a breach within 14 days of our notice, if your use has caused, or creates a serious risk of, action by WhatsApp or Meta against us or other customers, or if a law requires us to stop serving you.
- If we end the contract, you have 30 days from our notice to export Customer Data through the API, unless the law or abuse of the Service prevents it.
After the contract ends, your access stops, except for the export period above, and unused credits lapse, except as the Refund Policy or the list above says. We delete Customer Data as the DPA and the Privacy Policy describe. Export anything you need before you delete a team. Sections 4, 5, 7 (for amounts owed), 12 to 16, 18 and 20 continue to apply.
12. Intellectual property and feedback
We own Polymorfa, including the software, the documentation and our brand. While the contract lasts, you may use the Service for your business. Separate software licenses govern our SDKs, our command-line tool and any Polymorfa Inspector component that names its license. These Terms govern access to the hosted Service and do not restrict the rights those licenses grant.
If you send us suggestions, we may use them without owing you anything. We will not name you as their source without your permission.
13. Confidentiality
Each of us keeps the other's non-public information confidential, uses it only for this contract, and shares it only with staff, advisers and subprocessors who need it and are bound by similar duties. This does not cover information that is public through no fault of the receiver, that the receiver already had or developed independently, or that a law or authority requires the receiver to disclose. In that last case the receiver gives notice first where it is allowed to.
14. Warranties and disclaimers
We will provide the Service with reasonable skill and care and as the documentation describes. Otherwise, and as far as the law allows, we provide the Service as it is and as available. We do not promise that it will be uninterrupted or error-free, that every message will be delivered, or that WhatsApp or Meta will keep allowing any feature or number.
15. Liability
- We are not liable for indirect or consequential loss, lost profits, lost revenue, lost business, lost goodwill, lost or corrupted data, or messages or calls that fail or arrive late.
- Our total liability for all claims arising out of or relating to this contract or the Service is limited to the greater of (a) the fees for the Service you used in the 12 months before the event that caused the first claim, meaning the paid credits you spent and the add-on fees charged, and (b) CHF 100. This limit applies whatever the legal basis of the claim, including contract, tort or any other theory.
- For this calculation only, spent paid credits count at their proportionate original purchase price, excluding tax. Promotional and bonus credits count as zero. Add-on fees count excluding tax. Amounts in other currencies are converted to Swiss francs at the exchange rate the Swiss National Bank publishes for the date of the event that caused the first claim, or, if none is published that day, the last rate published before it.
- Claims arising from the same event or from related events count as one claim.
- You cannot recover the same loss twice. Service-level credits, credits returned under Ban Credit and refunds we give for the same event count toward this limit and are deducted from any amount we owe.
- Refunds of unused paid credits that these Terms or the Refund Policy promise are not damages. This limit does not reduce them.
- These limits do not apply to our liability for intent or gross negligence, or to liability that the law does not allow us to limit.
- Nothing in this section limits your payment obligations or your obligations under section 16.
- We are not liable for delays or failures caused by events outside our reasonable control, including actions by WhatsApp or Meta, outages at network or hosting providers we do not control, and orders of authorities.
16. Claims about your use
You will protect Polymorfa, its affiliates and its staff against every claim by a third party and every proceeding by an authority that arises from any of the following. You will pay all resulting losses, damages, fines, penalties, settlements, costs and reasonable lawyer fees.
- your use of the Service, including use by anyone with access to your accounts or credentials;
- your Customer Data and other content, and your messages, calls, recordings and campaigns;
- your recipients and end users, including people who link a WhatsApp account through you, for example with QuickLink;
- any notice, consent or permission you did not obtain, including to send messages or calls, or to access, intercept, record, sync or store communications;
- your integrations, systems and connected accounts;
- your breach of these Terms, the Acceptable Use Policy or the WhatsApp and Meta terms that apply to you;
- your violation of any law or of someone else's rights.
Claims and action by WhatsApp or Meta. This obligation covers every claim, demand and enforcement action that WhatsApp, Meta or their affiliates bring against us because of your numbers, accounts, messages, calls, campaigns, recipients or conduct.
This section covers claims and proceedings by third parties and authorities, the amounts that result from them and reasonable defense costs. It does not require you to compensate Polymorfa for Polymorfa's own loss of access to WhatsApp or Meta, or for revenue or business Polymorfa loses as a result.
This obligation has no cap. It does not cover any part of a claim that our intent or gross negligence caused. Some laws give people or authorities rights against us that a contract cannot remove. For those claims, this section gives us recourse against you to the extent the claim arises from the matters listed above.
We will tell you about a claim promptly. If we tell you late, your obligation is reduced only to the extent the delay harmed your position. We may control the defense and settlement of the claim, at your cost. You will cooperate and give us the information and help we reasonably ask for. You may take part with your own lawyers at your own cost. You may not settle a claim in a way that binds us, admits fault for us, or requires us to act or pay, without our written consent.
17. Sanctions and export rules
You may not use Polymorfa if you, or anyone who owns or controls your business, is subject to sanctions under Swiss, EU, UK, US or UN law, or from a country or region subject to comprehensive sanctions. You may not use it to deal with sanctioned people. You will comply with the sanctions and export control laws that apply to your use of the Service and our software.
18. Law and courts
Swiss law governs this contract, without its conflict-of-law rules. The UN Convention on Contracts for the International Sale of Goods does not apply. The courts of La Chaux-de-Fonds, canton of Neuchâtel, Switzerland, have exclusive jurisdiction. We may also bring a claim in the courts where your business is registered.
Before going to court, write to us at hello@polymorfa.com. We will try to settle the dispute with you within 30 days. This step does not stop either of us from asking a court for urgent relief or from taking steps needed to preserve a claim, such as meeting a limitation deadline.
19. Changes to these Terms
We will email team owners at least 30 days before a material change takes effect and show the new effective date at the top of this page. When a change requires it, we ask team owners and members to accept the new version in the console before they continue using it there. API access continues. If you do not accept the change, you can end the contract before that date. Section 11 then applies as if we had ended it, so we refund your remaining paid credits. Changes required by law or that only add features can take effect sooner.
20. General terms
- You may not transfer this contract without our written consent. We may transfer it to a company that takes over Polymorfa, and we will tell you.
- If a court finds a provision invalid, the rest stays in force and the invalid part is replaced by the valid provision closest to its purpose.
- Not enforcing a right is not a waiver of it.
- These Terms and the documents in section 1 are the whole agreement about the Service and replace earlier terms. Statements outside these documents, including on our website and in marketing, are not part of the contract. This does not limit liability for fraud.
- Nobody else has rights under this contract, except data subjects who can enforce the mandatory transfer clauses that the DPA incorporates.
- This contract does not make either of us the partner or agent of the other.
- Some features work with services that others provide, such as sign-in providers, our payment processor, SIP carriers, AI providers you connect, and your own integrations. Their own terms apply to them, and we are not responsible for them.
- Notices may be given electronically. We send notices to the email address of the team owner. You send notices to the addresses in section 21.
- The English version is binding. Translations are for convenience.
21. Contact and legal notice
Rue des Musées 58
2300 La Chaux-de-Fonds
Switzerland
UID CHE-303.047.962
Email: hello@polymorfa.com
Web form: polymorfa.com/contact
Registered in the Commercial register of the canton of Neuchâtel. See the legal notice for all contacts.