Skip to content

NewThe DPDP Rules phase in by May 2027.Check your website’s consent readiness

Home

SaaS and online services

Consent as an API, with receipts your customers can check

Software companies capture consent inside their own sign-up flow. Record it from your backend, check it before every marketing send, and let webhooks keep your stack in sync.

Get startedGet it set up for you
Check consent
js
import { OptProof } from '@optproof/node';​const optproof = new OptProof({ secretKey: process.env.OPTPROOF_SECRET_KEY, propertyId: 'prp_…' });​// Before sending a product-update emailconst granted = await optproof.consents.isGranted({ externalId: 'user_8812' }, 'product_updates');if (!granted) return; // respect the choice

Where you collect consent

  • Server API

    Call one endpoint after sign-up. Check consent before any email or in-app message.

  • Web widget

    Cookie consent for your marketing site, with Google Consent Mode v2.

  • Webhooks

    Signed events for every grant, withdrawal and erasure request.

Your notice, already started

The saas and online services template sets up 6 purposes, each with its data items and how long it is kept. Edit anything; your counsel should review it before you publish.

  • Your account and sign-in

    Needed for the service

    We use your details to create your account, sign you in securely and keep it safe.

    Data collected

    • Full name
    • Email address
    • Mobile number
    • Password (stored only as a secure hash)
    • Sign-in history and device details

    Kept for: 3 years

  • Running the service

    Needed for the service

    We process the content and settings you add so the product does what you asked it to do.

    Data collected

    • Content you create or upload
    • Workspace and team settings
    • Names and emails of teammates you invite

    Kept for: 3 years

  • Subscriptions and invoices

    Needed for the service

    We use your details to charge your subscription and send GST invoices.

    Data collected

    • Billing name
    • Billing address
    • GSTIN (if you give one)
    • Plan and payment history
    • Payment reference

    Kept for: 8 years

  • Customer support

    Optional

    We use your messages and account details to answer your questions and fix problems.

    Data collected

    • Name
    • Email address
    • Support messages and attachments
    • Screenshots you share

    Kept for: 2 years

  • Improving the product

    Optional

    We look at how features are used, so we can fix bugs and decide what to build next.

    Data collected

    • Features used and clicks
    • Error reports
    • Device and browser type
    • Account ID

    Kept for: 395 days

  • Product news and tips

    Optional

    We email you about new features, tips and webinars.

    Data collected

    • Name
    • Email address
    • Plan and features you use

    Kept for: 2 years

Systems that need to hear about changes

When someone withdraws or asks for erasure, these are the places their data usually lives. Connect the ones we support; the rest go on a checklist for your team.

  • Product database
  • Payment gateway / subscription billing
  • Support desk (Freshdesk, Zoho Desk)
  • Product analytics
  • Email marketing tool
  • Error monitoring

Records you may have to keep

An erasure request does not override a legal duty to keep some records. Your team picks the reason, and the person is told which records stay and why.

  • Invoices and accounts

    We must keep invoices and payment records for tax purposes. We keep only what the bill needs.

  • Security and processing logs

    We keep security logs for a minimum period to detect and investigate misuse of data.

  • Open dispute or legal claim

    Some records must be kept while a dispute, complaint or legal claim is open.

Start with test keys today. Go live when you’re ready.

Install the widget, record test consents and verify your first receipt in under ten minutes.

Get startedBook a demo