- Documents you send to the parsing API are processed and not stored once parsing is complete.
- Your documents and parsed data are never used to train general-purpose or shared AI models.
- We keep only what we need to run your account and bill for usage: your account details, API keys and request metadata such as time, endpoint and status.
- Card payments are handled by Stripe. We never see or store full card numbers.
- We do not sell personal data.
01Who we are
Parsinga is a document parsing service operated by Talentmicro Innovations (“we”, “us”), [Registered office address]. This policy explains how we handle personal data when you visit parsinga.com, create an account, contact us, or send documents to our API.
For your account and website data, we decide how and why it is processed. For documents you send to the API, you decide what is processed and why, and we process it on your behalf to return the parsed result.
02What we collect
Account information
Your name, organisation, email address and password when you sign up. Passwords are stored only as a salted bcrypt hash, never in plain text.
API keys and usage
The API keys you create, and metadata about each API request: the endpoint called, time, response status, response time, response size, any error message, and the IP address the request came from. We also keep running totals of your requests for usage reporting and billing. This metadata does not include the content of your documents.
Billing and payment information
If you add a payment method, your card or bank details are entered into secure fields that Stripe hosts on our billing page and go straight to Stripe. We never see or store full card numbers. Billing details you enter, such as your company name, billing email, address and tax ID, are stored with Stripe for your invoices. We keep your Stripe customer ID, your subscription status, a daily count of billed parses for each parser, and records of your invoices. Stripe shares the card brand, last four digits and expiry date with us so we can show which payment method is on file.
Documents and parsed results
The files you send to the API and the data we extract from them. These may contain personal data, for example the contact details and work history in a resume or the details on an identity document. See how we handle your documents.
Contact and sales enquiries
When you use our contact form: your company name, name, email, phone number if you give it, your message, your IP address and browser user agent.
Website analytics
We use Google Analytics to understand how the website is used, such as pages visited and approximate location. It uses cookies, described below.
03How we use personal data
- To provide the service: create and secure your account, authenticate API requests and return parsed results.
- To measure usage, apply your free parses and bill you through Stripe.
- To keep the service secure and reliable, for example detecting abuse and investigating errors.
- To reply to enquiries and provide support.
- To understand and improve the website.
- To meet legal and accounting obligations.
04How we handle your documents
Zero Data Retention (ZDR). Documents sent to the parsing API, and the results we return, are not stored once parsing is complete. Our full approach is in the Zero Data Retention (ZDR) Policy.
No training. Your documents and parsed data are never used to train general-purpose or shared AI or LLM models.
Custom parsers. If you ask us to build a custom parser, you may share sample documents with our team. People on that project review them to design and validate your parser. We use samples only for your parser, restrict access to the people working on it, and delete them as set out in the ZDR Policy.
On-premise deployments. When Parsinga runs in your own infrastructure, your documents do not reach our systems.
06International transfers
Our service providers may process data in countries other than yours. Where the law requires it, we use appropriate safeguards such as standard contractual clauses.
07How long we keep it
We keep personal data only as long as we need it for the purposes above. Periods for each type of data, including request logs, account data and contact enquiries, are set out in the Zero Data Retention (ZDR) Policy.
08Security
Data is encrypted in transit and at rest. Passwords are hashed with bcrypt, sign-in sessions use signed, HTTP-only cookies, and access to production systems is limited to people who need it. No system is perfectly secure, so please keep your password and API keys private and revoke any key you think has been exposed.
09Your rights
Depending on where you live, you may have the right to:
- access the personal data we hold about you and get a copy of it;
- correct inaccurate data;
- ask us to delete your data;
- object to or restrict certain processing;
- withdraw consent where we rely on it;
- complain to your local data protection authority.
To use these rights, email support@parsinga.com. If personal data reached us inside documents you were sent, for example a candidate’s resume, please contact the organisation that used Parsinga to process it, and we will help them respond.
11Children
Parsinga is a business service and is not intended for anyone under 18. We do not knowingly collect data from children through our website.
12Changes to this policy
We will update this page when our practices change and revise the date at the top. For material changes, we will notify account holders by email before they take effect.
Questions about this policy? Email support@parsinga.com.