On this page⌄
Skrap.ai is a product operated by dev4web.co, a sole proprietorship registered in India.
Save this DPA as a PDF, or ask us for a copy countersigned by dev4web.co.
Skrap.ai Data Processing Agreement
Version of November 16, 2026 · dev4web.co, 9, Kiran Nagar Phase 2, Ayodhya Bay Pass, Huzur, Bhopal, Madhya Pradesh 462022, India · contact@skrap.ai · skrap.ai/legal/dpa
1. Parties and scope
This Data Processing Agreement ("DPA") is between the customer that accepted the Skrap.ai Terms of Service ("Customer") and dev4web.co, a sole proprietorship registered in India that operates Skrap.ai (9, Kiran Nagar Phase 2, Ayodhya Bay Pass, Huzur, Bhopal, Madhya Pradesh 462022, India; contact@skrap.ai) ("Skrap").
It applies whenever Skrap processes Customer Personal Data on Customer's behalf in providing the Service and that processing is subject to Data Protection Law. It forms part of the agreement between the parties (the Terms of Service and any order form). If this DPA and the agreement conflict on the processing of personal data, this DPA prevails; if the Standard Contractual Clauses apply, they prevail over both.
2. Definitions
- Data Protection Law: the EU General Data Protection Regulation 2016/679 ("GDPR"), the UK GDPR and Data Protection Act 2018, the Swiss Federal Act on Data Protection ("FADP"), and any other data protection law that applies to the processing.
- Customer Personal Data: personal data that Customer or its users submit to the Service (for example emails to verify, names and domains to find, uploaded lists) and the results the Service returns for them, processed by Skrap on Customer's behalf.
- Service: the Skrap.ai website, web app, API, MCP server, browser extension and Google Sheets™ add-on.
- Sub-processor: a third party Skrap engages to process Customer Personal Data.
- Standard Contractual Clauses ("SCCs"): the clauses approved by European Commission Implementing Decision (EU) 2021/914.
- "Controller", "processor", "data subject", "personal data breach" and "processing" have the meanings given in the GDPR.
3. Roles of the parties
For Customer Personal Data, Customer is the controller (or a processor acting for its own controller) and Skrap is the processor (or sub-processor). Customer is responsible for having a lawful basis for the processing it asks for, including any outreach to the people it verifies or finds, and for the accuracy of its instructions.
Skrap is a controller, not a processor, for the account, billing, security and usage data it needs to run the Service, as described in the Privacy Policy.
4. Details of the processing
The subject matter, duration, nature and purpose of the processing, the types of personal data and the categories of data subjects are described in Annex I. Skrap processes Customer Personal Data for as long as Customer uses the Service, and afterwards only as described in section 9.
5. Skrap's obligations
- Instructions. Skrap processes Customer Personal Data only on Customer's documented instructions: the agreement, this DPA and Customer's use of the Service's features. Skrap tells Customer if it believes an instruction breaks Data Protection Law, unless the law forbids it.
- Confidentiality. Everyone at Skrap who can access Customer Personal Data is bound by confidentiality, and access is limited to what their role requires.
- Security. Skrap applies the technical and organisational measures in Annex II, and may improve them as long as the overall level of protection does not go down.
- No other use. Skrap does not sell Customer Personal Data and does not use it for advertising.
6. Sub-processors
Customer gives Skrap general written authorisation to engage Sub-processors. The current list is in Annex III and at skrap.ai/legal/subprocessors.
- Skrap imposes data protection obligations on each Sub-processor that are no less protective than this DPA, and stays responsible to Customer for its Sub-processors' performance.
- Skrap announces a new or replacement Sub-processor before it starts processing Customer Personal Data, by updating the list and emailing everyone who subscribed to changes on that page.
- Customer may object on reasonable data protection grounds within 30 days of the notice by writing to contact@skrap.ai. The parties will discuss the objection in good faith; if they can't resolve it, Customer may stop using the affected part of the Service or terminate the agreement, and receives a pro-rata refund of prepaid fees for the period after termination.
7. Assistance to Customer
- Data subject requests. Taking the nature of the processing into account, Skrap helps Customer answer requests from data subjects. Customer can export or delete its data in the app itself. If Skrap receives a request about Customer Personal Data directly, it refers the person to Customer unless the law requires otherwise. People can also ask Skrap to stop returning their details at skrap.ai/privacy/opt-out.
- Impact assessments and consultations. Skrap gives Customer the information it reasonably needs for data protection impact assessments and prior consultations with supervisory authorities about the Service.
8. Personal data breaches
Skrap notifies Customer without undue delay after becoming aware of a personal data breach affecting Customer Personal Data. The notice describes, as far as known, the nature of the breach, the categories and approximate number of data subjects and records concerned, the likely consequences, and the measures taken or proposed. Skrap sends updates as more becomes known, and takes reasonable steps to contain the breach and limit its effects. Notice goes to the email address of the account owner.
9. Deletion and return
- Bulk jobs. Bulk result files and the uploaded rows are deleted 30 days after the job finishes. On the Enterprise plan the team owner can choose a shorter window (7 or 14 days) and can have uploaded rows deleted as soon as a job finishes.
- During the agreement. Customer can download its results and export its account data at any time.
- At the end. When Customer deletes its account, Skrap deletes its bulk result files, uploaded rows, lists, saved searches, API keys and sessions. Billing and usage records are kept for as long as accounting and tax law requires.
- Verification cache. To answer repeat checks, Skrap keeps a verification and finder cache: an email address, or a name and company domain, with its last result, plus mail-server facts per domain. The cache holds no uploaded file, no other columns and no record of which customer asked, so it is not returned or deleted per customer. Skrap's own company and contact database (the business profiles the email finder and Search Leads draw on) is kept on the same terms and records no customer.
10. Information and audits
Skrap makes available the information reasonably necessary to show compliance with Article 28 of the GDPR, including written answers to security questionnaires. Skrap does not hold SOC 2 or ISO 27001 certification today. If that information is not enough, Customer may audit Skrap's compliance with this DPA, at Customer's cost, once a year (or after a personal data breach, or when a supervisory authority requires it), with at least 30 days' written notice, during business hours, under confidentiality, and in a way that does not disrupt the Service or expose other customers' data. The scope and timing are agreed in advance.
11. International transfers
Skrap is based in India and its Sub-processors are mostly in the United States. Where Customer Personal Data is transferred from the European Economic Area to a country without an adequacy decision, the SCCs are incorporated into this DPA by reference:
- Module 2 (controller to processor) where Customer is a controller;
- Module 3 (processor to processor) where Customer is a processor;
- with Clause 7 (docking clause) included, option 2 (general authorisation) in Clause 9(a) with the notice period of section 6, the optional wording in Clause 11 left out, Clauses 17 and 18 governed by and brought before the courts of Ireland, and Annexes I to III of this DPA as the SCC annexes.
For transfers from the United Kingdom, the UK International Data Transfer Addendum to the SCCs (version B1.0) applies, with the information in this DPA completing its tables. For transfers from Switzerland, the SCCs apply with the FADP in place of the GDPR, the Swiss Federal Data Protection and Information Commissioner as the competent authority, and the term "member state" read to include Switzerland. Skrap requires its Sub-processors to use a valid transfer mechanism as well.
12. Term, liability and governing law
This DPA lasts as long as Skrap processes Customer Personal Data. Each party's liability under this DPA is subject to the limitations in the agreement, except where Data Protection Law or the SCCs do not allow that. Apart from the SCCs, this DPA is governed by the law and courts named in the Terms of Service. Skrap may update this DPA to reflect changes in law or in the Service; changes that reduce Customer's protection need Customer's agreement.
Annex I. Description of the processing
| Data exporter | Customer (controller, or processor for its own controller). Contact: the account owner's email. |
|---|---|
| Data importer | dev4web.co, operating Skrap.ai, 9, Kiran Nagar Phase 2, Ayodhya Bay Pass, Huzur, Bhopal, Madhya Pradesh 462022, India. Contact: contact@skrap.ai. Role: processor. |
| Categories of data subjects | Customer's users (team members); people whose contact details Customer submits, looks up, verifies or saves (typically business contacts and prospects). |
| Types of personal data | Names, work email addresses, company names and domains, job titles, LinkedIn profile URLs, verification and finder results, IP addresses and device details of Customer's users, and account data (name, email, team membership). |
| Sensitive data | None intended. Customer should not submit special categories of personal data. |
| Frequency | Continuous, for as long as Customer uses the Service. |
| Nature and purpose | Email verification (checking an address with its mail server without sending an email), email finding, lead search, enrichment, storing lists and bulk results, and returning results to Customer through the app, API and integrations. |
| Retention | As set out in section 9. |
| Competent supervisory authority | The authority that is competent for Customer under Clause 13 of the SCCs. |
Annex II. Technical and organisational measures
The measures in place in the Service today:
- Encryption in transit: the website, app and API are served over HTTPS only (TLS terminated by Cloudflare), with HSTS telling browsers to keep using HTTPS.
- Credentials: passwords and API keys are stored only as one-way hashes; API keys are shown once, when they are created.
- Sign-in protection: two-factor authentication with an authenticator app (TOTP) and recovery codes; rate-limited sign-in and public endpoints; bot protection on sign-up and public forms.
- Team controls: owner, admin and member roles; team owners can require two-factor authentication for every member and, on the Enterprise plan, require sign-in with Google Workspace or Microsoft and restrict member email domains.
- Sessions: users see the devices they are signed in on and can sign out any device or all others.
- API keys: on paid plans a key can be limited to an IP allowlist and given an expiry date; API requests are rate-limited per key.
- Webhooks: deliveries are signed with HMAC-SHA256 over a timestamp and the body (Skrap-Signature header) so receivers can check their origin.
- Logging: on paid plans an activity log records sign-ins, API key and team changes and downloads with IP address and browser; entries are kept 365 days and can be exported as CSV.
- Access by staff: limited to what each role requires.
- Retention and deletion: as in section 9, with self-serve data export and account deletion.
- Security headers: pages tell browsers not to let other sites frame them and not to guess content types.
Annex III. Sub-processors
As listed at skrap.ai/legal/subprocessors on the date of this version:
| Sub-processor | Purpose | Location |
|---|---|---|
| Amazon Web Services, Inc. | Hosting of the website, app, API and databases (Amazon EC2, us-east-1), and delivery of account emails (Amazon SES, through our self-hosted useSend server). | United States |
| Cloudflare, Inc. | DNS, HTTPS/TLS termination, content delivery and DDoS protection in front of skrap.ai, app.skrap.ai and api.skrap.ai. | Global network (United States company) |
| RackNerd LLC | Servers that run Skrap.ai's email verification checks (they talk to the recipient's mail server and end the conversation before any email is sent) and Skrap.ai's own mail server. | United States |
| Cloudinary Ltd. | Storage of bulk result files and images. | United States |
| Stripe, Inc. | Payments, invoices and tax IDs. | United States |
| Google LLC | reCAPTCHA (bot protection on sign-up and public forms), Google Analytics (only with your consent) and Sign in with Google. | United States |
| Microsoft Corporation | Sign in with Microsoft, only when you choose it. | United States |
| Anthropic, PBC | The AI model behind Skrap Assistant (support chat) and AI search. | United States |
| Functional Software, Inc. (Sentry) | Error monitoring. | United States |
| IPinfo, Inc. | IP geolocation for sign-in security and fraud prevention. | United States |
| B2B data provider | Company and professional profile data for Search Leads, the email finder and enrichment. | United States |
| Web data provider | Web search, public company pages and public professional profiles. | On request |