Skrap.ai Trust Center
Everything a security or procurement review needs: how we protect accounts and data today, how long we keep it, who processes it, and the documents to sign.
Security practices
Each card is a control that exists in Skrap.ai now, with a link to the details. We don't hold SOC 2 or ISO 27001 certification and don't offer an uptime SLA, so you won't find those claims here.
Encrypted in transit
The website, app and API are served over HTTPS only, with TLS terminated by Cloudflare and HSTS telling browsers to stay on HTTPS.
Data in transitHashed credentials
Passwords and API keys are stored only as one-way hashes. API keys are shown once, when you create them.
Accounts and sign-inTwo-factor authentication
Authenticator-app (TOTP) codes with downloadable recovery codes. Team owners can require 2FA for every member.
Two-factor sign-inSingle sign-on rules
Enterprise team owners can require sign-in through SAML 2.0, Google Workspace or Microsoft, limit members to company domains and provision members with SCIM.
Team sign-in rulesSessions you control
See every device you're signed in on, with its approximate location, and sign out one device or all the others.
SessionsAPI key controls
On paid plans, limit a key to an IP allowlist and give it an expiry date. Requests are rate-limited per key by plan.
API keysSigned webhooks
Every delivery carries an HMAC-SHA256 signature over a timestamp and the body (Skrap-Signature header), with retries and a delivery log.
Webhook docsActivity log
On paid plans, sign-ins, API key and team changes and downloads are logged with IP address and browser, kept 365 days, exportable as CSV.
Teams and accessData retention
Bulk result files and uploaded rows are deleted 30 days after a job finishes; Enterprise owners can choose 7 or 14 days.
Retention detailsDo-not-contact list
Teams keep a shared list of emails and domains they must not contact; matches are flagged in finds and exports.
Your controlsDPA and sub-processors
A GDPR Article 28 DPA with the EU Standard Contractual Clauses, and a public list of every sub-processor with change notices.
Read the DPAOpt-out for anyone
People who aren't customers can ask us to stop returning their email address or LinkedIn profile, or request a copy of their data.
Opt-out pageVulnerability disclosure
Report security issues privately. Our contact details are published in a standard security.txt file.
Disclosure policy
Data retention
| Data | How long we keep it |
|---|---|
| Bulk result files and the rows you uploaded | Deleted 30 days after the job finishes. Enterprise team owners can choose 7 or 14 days, and have uploaded rows deleted as soon as a job finishes. |
| Verification and finder cache | Kept, so repeat checks can be answered: an email address (or a name and company domain) with its last result, plus mail-server facts per domain. No uploaded file, no other columns, no record of which customer asked. |
| Skrap's company and contact database | Kept: the business profiles the email finder and Search Leads draw on (companies, people's work details and work emails), from our data providers and earlier lookups. It records no customer. People can opt out at skrap.ai/privacy/opt-out. |
| Request history (submitted values and results) | Up to 3 years for billing records and your usage history, or until you ask us to delete it. |
| Activity log | 365 days. |
| Support chat messages | Deleted from the chat system 180 days after the last message. |
| Your account | Until you delete it. Deletion purges bulk files, uploaded rows, lists, saved searches, API keys and sessions; billing records stay as long as the law requires. |
Full details in section 8 of the Privacy Policy.
Documents
- DPAData Processing AgreementGDPR Article 28 terms with the Standard Contractual Clauses. Download as PDF or request a signed copy.
- ListSub-processorsWho processes personal data for us, what for and where. Subscribe to change notices.
- SecuritySecurity overviewThe protections in your account, API keys and team, as they work today.
- GDPRGDPR & data protectionRoles, legal bases, retention and the controls you have.
- PolicyPrivacy PolicyThe full description of how we handle personal data.
- TermsTerms of ServiceThe agreement for using Skrap.ai, its API and integrations.
- RFC 9116security.txtMachine-readable security contact (RFC 9116).
- PrivacyOpt-out and data requestsFor people who aren't customers: stop us returning your details, or request your data.
Request a security review
Send us your security questionnaire or vendor-onboarding form, or ask for our procurement pack. We answer from how the product works today and reply within 24 hours on business days with next steps.
Need a signed DPA? Request it on the DPA page.
Security questionnaire FAQ
Who operates Skrap.ai, and where?
Skrap.ai is operated by dev4web.co, a sole proprietorship registered in India (9, Kiran Nagar Phase 2, Ayodhya Bay Pass, Huzur, Bhopal, Madhya Pradesh 462022, India).
Where is customer data hosted?
On Amazon Web Services (Amazon EC2) in the us-east-1 region, United States, behind Cloudflare. Email verification runs on our own servers in the United States, and bulk result files are stored with Cloudinary. Every provider is on the sub-processors page.
Do you hold SOC 2 or ISO 27001 certification?
No. Skrap.ai does not hold SOC 2 or ISO 27001 certification today, and we don't have a published penetration test report. We describe the controls we do have on this page and on Security, and answer security questionnaires on request.
Is data encrypted?
Data in transit between you and Skrap.ai is encrypted with HTTPS/TLS (Cloudflare in front, HSTS on). Passwords and API keys are stored only as one-way hashes. Ask us about anything beyond that for your questionnaire.
Do you support SSO and MFA?
Yes. Everyone can turn on two-factor authentication (authenticator app, with recovery codes), and team owners can require it. On the Enterprise plan, owners can require sign-in with Google Workspace or Microsoft and restrict member email domains; the owner keeps break-glass access. Enterprise teams can also connect a SAML 2.0 identity provider (Okta, Microsoft Entra ID, OneLogin, Google Workspace) after verifying their company domain, provision and remove members with SCIM 2.0, set session and sign-in IP rules, and stream audit events to their own endpoint; see the SSO and SCIM guide.
Who at Skrap.ai can access customer data?
Only staff who need it for their role, such as support answering a ticket you opened. Access is limited by role, and the support assistant can read only the signed-in customer's own account.
How long do you keep data?
Bulk result files and uploaded rows are deleted 30 days after the job finishes (7 or 14 days if an Enterprise team owner chooses). The verification and finder cache that answers repeat checks is kept, and so is Skrap's company and contact database; neither holds your uploaded file or any record of which customer asked. Deleting your account purges your bulk files, uploaded rows, lists, saved searches, keys and sessions. See Data retention.
Do you sign a DPA, and how are transfers covered?
Yes. Our DPA applies to the contact data you process with us and includes the EU Standard Contractual Clauses (Modules 2 and 3), the UK Addendum and Swiss adjustments. Request a countersigned copy from the DPA page.
How will you tell us about a data breach?
Without undue delay after we become aware of a breach affecting your data, by email to the account owner, with what we know and what we're doing about it, as set out in section 8 of the DPA.
How do we learn about new sub-processors?
Subscribe on the sub-processors page. We email subscribers before a new or replacement sub-processor starts processing personal data, and customers can object within 30 days.
Do you have a status page or an uptime SLA?
Not yet. There is no public status page and we don't offer an uptime SLA. If something isn't working, open a ticket from Help & support in the app or write to contact@skrap.ai.
Can we get a completed security questionnaire?
Yes. Use the security review form on this page and attach or describe your questionnaire. We answer from how the product works today.