Scope and compliance
What PulseWire is, and where it stops.
PulseWire is an independent third-party API gateway for publicly available Twitter/X data. This page summarizes the service scope, acceptable use, and data practices that apply to every plan.
Data scope
The gateway serves information that is publicly visible on the platform without authentication as a follower or recipient.
In scope
- Public user profiles and normalized handles
- Public post timelines, post detail, quotes, and reply threads
- Public follower and following lists
- Public engagement metrics returned with the post or profile
- Search results and trending topics for supported locations
Out of scope
- Private or protected accounts and their posts
- Direct messages and any other private conversation surface
- Non-public account settings, contact details, or billing information
- Deleted content, which is removed from responses once it is no longer publicly visible
Acceptable use
Access is sold for monitoring, research, analytics, and product enrichment workloads. The following are not permitted on any plan.
- Building profiles of private individuals for harassment, doxxing, or targeting
- Discriminatory decisions about individuals, including employment, credit, housing, or insurance
- Surveillance of individuals or groups on behalf of a government or law enforcement body
- Reselling raw responses as a competing bulk data feed
- Any use that breaches applicable law or the platform policies that apply to you
We may suspend access where we have a reasonable belief that traffic falls into one of these categories.
Your compliance responsibility
You are responsible for making sure your use of PulseWire complies with applicable laws, platform policies, and the PulseWire agreement. That includes deciding whether you have a lawful basis to store and process the personal data contained in public posts and profiles, honoring deletion requests from the individuals in your own datasets, and meeting the disclosure obligations that apply in your market.
Privacy summary
We collect the information needed to operate accounts, billing, support, security, and API usage tracking. That means contact details for your team, billing records, support correspondence, and request metadata such as endpoint, timestamp, status, and volume.
- Request metadata is retained for operational troubleshooting and quota accounting
- We do not sell customer account data
- Eligible individuals can request access, correction, or deletion of their personal data
- Subprocessors are limited to hosting, payment, and email infrastructure providers
Requests can be sent to our team and are answered within the statutory window that applies to the requester.
Terms summary
- Access is granted per API key, scoped to the endpoint set agreed during onboarding
- Quota and rate behavior are set per agreement and visible in the console
- Keys must not be shared outside the contracting entity
- The service is provided without warranty as to third-party platform availability or data completeness
- Either party may terminate with the notice period stated in the commercial agreement