Privacy Policy

Last updated: September 8, 2026

Parse API LLC operates ParseAPI. This policy explains how we handle personal data across our website, dashboard, APIs, Bulk file tools, and integrations, including purchases without an account.

1. Short version

We process data to provide lookups, run file jobs, manage accounts and payments, secure the service, and understand how people find and use it. We do not sell your personal data or your API traffic as a marketing product.

We are the controller of account, billing, support, and site data. When we process personal data you submit on behalf of your users or customers, our Data Processing Agreement also applies.

2. What we collect

Account. Email, name if you provide one, and session info so you can sign in (magic link) and use the dashboard.

Bulk files. Uploaded file contents, filenames, selected columns, sample values and results, output files, and job history. For a one-time purchase, we also keep the receipt email and payment reference. Only upload data you have the right to process.

Billing. Payment and subscription details are handled by our payment processor. We store plan status and payment references so billing works. We do not store full card numbers on our servers.

API usage. To operate the product and show you Usage / Activity, we log things like endpoint, timing, status, and related request metadata. That can include path and query parameters. See the retention section below, and do not put secrets in URLs.

API keys. Keys are stored so we can authenticate requests. Team members with dashboard access can reveal ordinary API keys. Keys managed for connected apps are not revealed.

Support. If you email us, we keep that conversation so we can help you.

Site analytics. We log visits on parseapi.com (page, referrer, IP address, user agent, and session information), campaign parameters, and advertising click identifiers. We connect these with signups, purchases, and Bulk job steps to measure which channels lead to customers and where people encounter problems. This is first-party measurement on our service. We do not sell these records or build profiles across unrelated sites.

Cookies / local storage. Used for sign-in sessions, basic site preferences (for example, docs language choice), and a short-lived first-party cookie for the site analytics above. Advertising measurement uses a separate cookie as described below.

Advertising measurement. For eligible visits from the United States, we save the Google ad-click identifier for up to 90 days. If you purchase from the United States during that period, we report the identifier, order reference, purchase time, currency and purchase amount after automatic refunds to Google to measure ad performance. These reports exclude your email, uploaded file contents and API lookup inputs, and disable ad personalization. We skip this measurement when your location is outside the United States or unavailable, or when your browser sends Global Privacy Control or Do Not Track. These signals also remove the saved advertising cookie on your next page visit and prevent its use at checkout. A direct return visit does not extend the cookie's lifetime. To request deletion of a purchase report or stop a pending report, contact Email with your order reference. Read how Google uses this data.

3. Why we collect it

• Provide and secure the service
• Process the lookups and Bulk file jobs you request
• Authenticate API calls and manage keys
• Manage subscriptions and billing
• Show usage and recent activity in the dashboard
• Send transactional email (magic links, receipts, usage notices)
• Debug outages and improve reliability
• Respond to support requests
• Measure acquisition channels, purchases, and how the service is used

4. What we do not do

• Sell or rent your personal information
• Sell your query stream as a marketing dataset
• Build advertising profiles of end users across unrelated sites

5. Service providers

We use service providers to process requests and operate ParseAPI. They receive the data needed for their work:

• Service operation and data storage
• Usage records and analytics
• Google, for advertising purchase measurement described above
• Lookup and verification providers that receive the values needed to answer your request
• Payments and billing
• Email delivery for sign-in and service notices

6. Retention

• Account and billing. Kept while your account is active and as needed for taxes, disputes, and legal obligations.
• Bulk access. Downloads and sample access expire 30 days after the job is created.
• Bulk storage. Uploaded files and result files are scheduled for automatic deletion after 31 days in storage. Removal runs asynchronously after that period. Download expiry and storage deletion are separate events.
• Job records. Job history, stored samples, and payment records are separate from the downloadable files and may remain after download access expires.
• Request and site records. Request logs, error logs, and site analytics do not currently have a fixed automatic deletion period. These records include historical API usage.
• Support. Conversations are kept for support and related legal needs.

For personal data processed on your behalf, the DPA's retention and deletion commitments also apply. These descriptions of storage and access do not extend an existing contractual deletion deadline. To request deletion or ask about a particular record, email Email.

7. Security

We use HTTPS, passwordless sign-in, API key controls, and team access roles. Our Security page describes these measures and how to report an issue. Security reports go to Email.

8. Sharing

We share data with processors listed above to run the service, or if the law requires it (subpoena, court order, valid legal process). If the business is sold or merged, account data may transfer under the same kinds of protections.

9. Your rights and choices

You can update account details in the dashboard, archive API keys anytime, and cancel paid plans. To request access, correction, or deletion of personal data we hold about you, email Email. We may need to verify your identity. Some records must be kept for legal or billing reasons.

Depending on the law that applies to you, you may also request a portable copy, restrict or object to processing, or withdraw consent for processing based on consent. You can complain to your local data protection authority. For requests covered by the EU or UK GDPR, we respond within one month. If a permitted extension is necessary, we explain the reason within that month.

If your data was submitted by one of our customers, contact that organization first. They determine why the data is processed, and we assist them with requests under the DPA.

10. Children

ParseAPI is not directed at children under 13 (or the equivalent age in your region). Do not create an account for a child.

11. International processing

We may process data in the United States and other countries where our providers operate. If you use the service from elsewhere, you are sending data across borders to us and those providers.

Contact Email for information about the destinations and transfer safeguards that apply to your data. For data processed on your behalf, see the DPA's international transfer terms.

12. Changes

We update the date above when this policy changes. Where required, we provide notice of material changes or request consent before using personal data for a new purpose.

13. Contact

Parse API LLC. Privacy questions and requests: Email

Also see Terms of Service and the Data Processing Agreement.