Security

Last updated: 17 October 2026. This page describes how ContentSERP.in protects customer data. It describes controls that are in place today; it does not claim certifications we do not hold.

Data in transit

All traffic to and from contentserp.in and auth.contentserp.in is served over TLS. Cloudflare terminates TLS at the edge and applies its web application firewall and DDoS protection in front of every request. Plain HTTP is redirected to HTTPS.

Payments

Payments are processed by Cashfree Payments. Card data is entered on Cashfree’s payment surface and is never transmitted to or stored on our servers, which keeps our systems out of card-data scope. Refunds are issued through the same provider.

Hosting and isolation

Production runs on a VPS provided by InterServer. The web application, its database and its file storage are separated by filesystem paths per site, and administrative access is restricted to named accounts. No shared credentials are used for production administration.

Access control

Administrative access requires individual authenticated accounts. Integrations that write to the site use scoped, revocable tokens rather than stored passwords, and those tokens can be invalidated without changing any account password.

Backups

Automated backups of the site and its database are taken on a schedule and stored separately from the production filesystem. Restores are tested as part of routine maintenance.

AI features and your content

AI-assisted features send the text you submit to the model providers listed on our subprocessors page, and that text is handled under those providers’ terms. Do not paste credentials, API keys or other secrets into AI features. Content you generate remains yours.

Vulnerability management

Dependencies and plugins are reviewed and updated on an ongoing basis, and access tokens are rotated when staff or integrations change. If you believe you have found a vulnerability, report it to [email protected] with steps to reproduce. We will acknowledge receipt and keep you informed of the fix. Please do not test against other customers’ accounts or run automated scans that degrade service.

Incident response

If a breach affects personal data, we will notify affected account holders and the relevant authority without undue delay, and within 72 hours of becoming aware where the law requires it. Notification will describe what happened, what data was affected and what we are doing about it.

Contact

Security questions: [email protected].

ContentSERP AI
Hi! I'm the ContentSERP AI. How can I help you optimize your SEO today?
[gtranslate]