1. Scope
This policy covers the public website (www.apipull.com, including its Spanish and Chinese versions), the developer console, and the API gateway at gateway.apipull.com. It does not cover the systems of the institutions our endpoints query, nor the systems of customers who call our API — those are governed by their own policies.
2. Who is responsible Pending confirmation
The registered entity behind API Pull and its formal role as data controller are listed below. Where a row reads “Pending confirmation”, that fact has not been published and we will not substitute a plausible-looking placeholder for it.
3. Account data
Registration asks for four fields: a username, a display name, an email address, and a password. Passwords are stored hashed, never in a readable form. Email verification and an image CAPTCHA are required to complete signup. After registration the account record also accumulates the IP address and timestamp of your most recent sign-in, your prepaid balance, an API token used to authenticate gateway calls, and an invite code. We do not ask for a government identifier, a date of birth, or a payment card in order to create an account.
5. Website analytics
Page views, clicks on links and buttons, and page-exit events are sent to our own endpoint and stored on our own servers. Each record can contain: event name, your user id if signed in, the device identifier above, the page URL and title, the referring URL, user agent, derived device type, browser, operating system, screen resolution, browser language, and IP address. Click events additionally record the clicked element's tag, its visible text truncated to 100 characters, its id, its CSS classes truncated to 200 characters, and the destination URL for links. Google Analytics 4 runs in parallel on every page; that data sits with Google under their terms, not ours.
6. API calls
Two separate records are written when you call an endpoint. The first is billing and operations metadata: your user id, the product and endpoint, a trace id, HTTP method and route, the calling IP address, the user agent, the amount charged, the HTTP status, the response time, and any error message. The second record — written for troubleshooting and billing disputes — additionally stores the request parameters you sent and the response body the upstream source returned.
7. People you look up
Most personal data flowing through the platform is not about our customers — it is about the individuals whose records a customer queries. For that data we act on the customer's instruction: the customer decides who to look up and why, and the customer is responsible for having a lawful basis to do so. We do not compile our own marketing database from query results, and we do not resell query results to other customers.
8. Why we process it
- Operating your account, authenticating you, and authenticating gateway calls.
- Metering calls and charging your prepaid balance.
- Diagnosing failures and disputes — the reason request and response bodies are retained.
- Understanding which pages and endpoints get used, so documentation effort goes where it is needed.
- Detecting abuse, credential sharing, and automated scraping of the site.
10. How long we keep it
Account records persist for as long as the account exists. Analytics records, API call metadata, and the stored request and response bodies described in section 6 currently have no automated deletion schedule in place. We are not going to state a retention period we do not enforce. A defined retention and purge policy is outstanding work; until it ships, assume records persist. You can ask us to delete your account and its associated records using the contact channels below.
11. Security
The site and gateway are served over HTTPS. Account passwords are hashed. Gateway access requires a per-account API token, and console access requires a session token that expires. What we will not claim is a certification, an audit, or an encryption-at-rest guarantee that we cannot point to. Treat the request and response retention described in section 6 as the honest upper bound on our current data-minimisation posture.
12. Your choices
- Block or clear cookies and localStorage in your browser to stop device-level analytics grouping.
- Use Google's opt-out browser add-on, or a tracker blocker, to stop Google Analytics collection.
- Email us to access, correct, or delete your account data.
- Strip the _source parameter from a campaign link before opening it if you do not want the embedded name and email stored locally.
13. If a record about you was returned by our API
If you are not our customer but believe your personal data was returned through one of our endpoints, write to us with enough detail to locate the query and we will tell you what was retained and remove it from our own stores. We cannot correct the underlying record: it belongs to the issuing institution, and a correction has to be made there to take effect. The Data Usage page lists each institution and its official channel for exactly this purpose.
14. Cross-border transfers Pending confirmation
Queries about Mexican, Chilean, and Colombian data subjects are served from infrastructure that may sit outside those countries, and Google Analytics data leaves for Google's infrastructure. The formal transfer basis depends on the registered entity and its jurisdiction, which is still pending confirmation.
15. Changes to this policy
Material changes will be reflected in the “Last updated” date at the top of this page. Because this document is generated from the platform's actual configuration, a change in what we collect shows up here rather than being quietly absorbed.
Registered entity Pending confirmation
The registration details for the entity operating API Pull have not been published yet. Rather than print a placeholder here, we are leaving the table empty and keeping this page out of search indexing until the details are confirmed. Until then, the contact channels below are the authoritative way to reach a responsible party.
How to reach us
Questions about this document, requests about your own data, and requests about a record returned by one of our endpoints all go to the same two channels. Written requests by email are preferred because they leave a record on both sides.
- partner@apipull.com
- Telegram
- https://t.me/Api_pull