Public explanation
Use product, security, privacy and support pages to understand concepts, terminology and the questions a customer should resolve.
TextPulse trust center
One place to evaluate TextPulse before production
Use this index to separate public guidance from account-specific evidence. Security, privacy, availability, support, route and commercial decisions should be tied to the current document that governs the actual customer, destination and effective date.
Trust overview
Match every claim to evidence and scope
A useful answer identifies what is covered, which system or route it applies to, who issued it, when it became effective and when it should be reviewed again. Undated or universal claims should not control a production decision.
Account documentation
Use authenticated API details, sender records, route settings and account controls for the implementation being tested.
Written commercial terms
Use the current quote, order form, DPA, SLA and service agreement for rates, legal entity, obligations, support and remedies.
Conflict rule: If a general public page and a dated account-specific document differ, stop and resolve the conflict through the authorized channel before sending production traffic.
Document map
Open the source closest to your requirement
These public pages explain the current evaluation framework. Exact company, security, data-processing, service-level and commercial commitments must still be confirmed where the requirement calls for written evidence.
Security
Shared responsibility, account and API controls, OTP abuse, data handling, monitoring, incidents and evidence requests.
Security overviewPrivacy
Public information about personal-data collection, use, protection and user choices. Confirm the policy version that applies.
Privacy policyGDPR workflows
Controller and processor roles, lawful processing, minimization, rights, transfers, retention and incident preparation.
GDPR informationService levels
Measurement boundaries, API and delivery indicators, dependencies, incidents, maintenance, support and written SLA terms.
SLA planning guideSupport
Integration, delivery, sender, account, billing and security case preparation without disclosing secrets.
Support centerService terms
Review the current public terms, then confirm any customer-specific order, quote or amendment that changes them.
Terms of servicePricing and routes
Understand the variables that shape cost and the fields a dated route quote should contain.
Pricing frameworkPlatform scope
Review what TextPulse describes publicly and which claims require account or contractual confirmation.
About TextPulse SMSContact routing
Prepare sales, support, billing, security, privacy or abuse evidence and use the authorized channel.
Contact guideDisclosure matrix
Know which facts require direct confirmation
Publishing a checklist is not the same as publishing the underlying evidence. Treat every missing answer as an open due-diligence item rather than assuming the most favorable interpretation.
| Decision area | Public guidance available | Confirm in current written evidence |
|---|---|---|
| Company identity | Platform purpose and public product information. | Contracting legal entity, registration, address, tax and invoice details. |
| Security | Review boundaries, shared responsibility and evidence checklist. | Implemented controls, independent assurance, exceptions, vulnerability and incident terms. |
| Privacy | Privacy and GDPR planning information. | Roles, instructions, DPA, locations, subprocessors, transfers, retention and deletion. |
| Service level | Definitions, metrics and measurement framework. | Numerical targets, exclusions, maintenance, support times, credits and claim process. |
| Coverage and sender | Route-planning and sender guidance. | Countries, networks, sender types, registrations, filtering, throughput and effective date. |
| Pricing | Cost drivers and quote checklist. | Rates, currency, taxes, billing increment, billable states, minimums and validity. |
Buyer workflow
Run due diligence as a documented decision
Review evidence in a consistent sequence so technical, legal, security, procurement and operations teams are evaluating the same service boundary.
Define the use case
List countries, traffic type, sender, volume, latency sensitivity, data categories, user risk and business impact.
List requirements
Separate mandatory controls and contract terms from preferences. Assign an owner and evidence type to every requirement.
Review evidence
Record source, version, date, scope, exceptions and open questions. Do not mark a requirement complete from a marketing sentence alone.
Test the workflow
Validate API, sender, delivery reports, failure paths, monitoring, abuse controls, support and reconciliation with representative traffic.
Approve residual risk
Document gaps, compensating controls, owner, approval date, renewal trigger and conditions that require re-review.
Monitor change
Review route, price, subprocessor, location, API, security, SLA and policy changes before they silently alter the approved design.
Responsible messaging
Trust includes how the customer uses the service
A secure provider cannot make deceptive, unlawful or poorly controlled traffic trustworthy. Customers should document permission, sender identity, opt-out behavior, content rules, recipient protection and abuse monitoring for each destination.
Permission and transparency
- Identify the purpose and lawful basis
- Record consent where required
- Identify the sender clearly
- Honor effective opt-out requests
- Separate service messages from promotion
Security and abuse controls
- Protect account and API credentials
- Rate-limit OTP and campaign actions
- Monitor unusual destinations and volume
- Minimize message and recipient data
- Investigate complaints and repeated failures
Change and review
Keep an approval current after launch
A due-diligence decision can become stale when the route, sender, data flow, application, contract or risk changes. Establish review triggers instead of relying only on a yearly calendar reminder.
Technical triggers
New API version, authentication method, webhook design, data field, integration environment or monitoring path.
Operational triggers
New destination, sender, traffic class, volume profile, route, carrier behavior or production incident.
Governance triggers
New contract, policy, legal requirement, subprocessor, data location, assurance report, SLA or company entity.
Evidence register
Keep the reviewed evidence traceable and current
A due-diligence folder should show why a requirement was marked complete, not simply contain a collection of files. Maintain a register that connects every decision to the exact evidence reviewed and makes expired or superseded information visible.
| Register field | Record | Review control |
|---|---|---|
| Requirement | Clear security, privacy, service, legal, route or commercial condition and its owner. | Identify whether it is mandatory, conditional or an accepted preference. |
| Evidence identity | Document title, issuer, version, date, scope and authoritative storage location. | Do not rely on an undated screenshot or copied marketing text. |
| Assessment | How the evidence satisfies the requirement, exceptions found and any compensating control. | Name the reviewer and approval date instead of using an unexplained check mark. |
| Validity | Expiry, renewal date, contract term and events that can make the evidence stale. | Alert before expiry and after a material service or deployment change. |
| Open action | Missing answer, responsible party, due date and production condition. | Prevent an unresolved mandatory item from silently becoming accepted risk. |
Access control: Assurance reports, contracts, architecture records and incident material may be confidential. Limit access, record distribution and remove obsolete copies according to the applicable retention requirement.
Trust center questions
Does this trust center prove that every requirement is met?
No. It organizes public information and identifies evidence to request. A requirement is complete only after the current evidence has been reviewed for the actual service, account and scope.
Where should I verify the contracting company?
Verify the legal entity, address, registration, invoice and tax details in the current order form, service agreement or other authoritative commercial document before contracting.
Where are certifications or audit reports listed?
This page does not claim an unverified certification or audit. Request current evidence through the authorized channel and verify its issuer, period, systems, locations and exceptions.
Does the public SLA page create an uptime guarantee?
No. It explains how to evaluate service levels. Only an applicable written SLA can define numerical commitments, measurement, exclusions, support targets, credits and remedies.
How often should due diligence be reviewed?
Set a regular review and trigger an earlier review when routes, countries, senders, data, subprocessors, locations, APIs, controls, contracts or material incidents change.
Close evidence gaps before production
Record the requirement, source, scope, review date, open issue and person responsible for the decision.