Skip to main content
Praman Labs
ProductHow it worksSolutionsResearchLogin
Book a backtest
Navigation
ProductHow it worksSolutionsResearchLoginBook a backtest

Legal record / Privacy

Website privacy notice.

How the public site and backtest form handle business contact information. Production deployments are governed separately.

Status
Public website notice
Effective
12 August 2026
Applies to
Public site & backtest form

Record register

  • Privacy
  • Terms
  • Security
  • Model governance

On this page

  1. 01Scope
  2. 02Information processed
  3. 03Purposes
  4. 04Providers & transfers
  5. 05Retention & deletion
  6. 06Your requests
On this page
  1. 01Scope
  2. 02Information processed
  3. 03Purposes
  4. 04Providers & transfers
  5. 05Retention & deletion
  6. 06Your requests

Record 01

This notice stops at the website boundary.

Praman Labs acts as the data fiduciary for business-enquiry information submitted through this site.

This notice covers the public website and the backtest request form. Product deployments use separate customer agreements, approved data flows and notices.

Do not submit applicant data

Do not place customer records, account numbers, identity documents or other personal data about an applicant into the public site or form.

Record 02

The site processes a narrow business record.

The form collects only the information needed to understand and route the enquiry, plus short-lived abuse-prevention data.

  • Backtest request

    Business contact data

    The form collects your name, work email, institution, role, monthly application-volume band, selected modules and the note you choose to provide.
  • Delivery records

    External delivery

    The message is delivered to a configured business mailbox through Resend and may also be sent to a configured CRM webhook. The application does not write the submitted payload to its own database or application logs.
  • Abuse-prevention record

    15-minute window

    The server reads the network address forwarded by the hosting provider, hashes it with a deployment salt and keeps request times in process memory for 15 minutes to enforce the form limit.
  • Basic server traffic

    Service operation

    The hosting provider may process request headers, network addresses and error records needed to serve and protect the site under its own service terms.

Record 03

Processing follows the request you initiate.

Contact fields support the business conversation and protect the form; they are not collected for behavioural advertising.

  • Respond to an enquiry

    We use the form fields to identify the institution, understand the requested backtest and arrange a business conversation.
  • Prepare an NDA and data plan

    If the conversation proceeds, the same business contact details may be used to coordinate an NDA, field map and secure transfer method.
  • Prevent automated abuse

    A hidden field, submission timing and short-lived hashed network key are used to reject automated or excessive requests.
  • Meet a legal request

    Information may be preserved or disclosed where applicable law requires it. A request is reviewed before any disclosure is made.

Record 04

A submission passes through named service roles.

Provider involvement is limited to hosting, delivery and an optional company CRM.

  • Website hosting

    The hosting provider processes the request data needed to serve the site, protect the form and keep operational error records.
  • Message delivery

    Resend receives the submitted fields to deliver the enquiry to the configured business mailbox.
  • Optional CRM

    If a CRM webhook is configured, the same submitted fields are sent to that service. Current provider and transfer details are available through the privacy contact below.

Advertising and sale

We do not sell contact information. We do not use backtest requests for behavioural advertising, and the site does not set an analytics identifier or advertising cookie.

Record 05

Retention follows the business exchange.

The application keeps no contact-form database, but delivered copies may remain in the receiving mailbox or configured CRM.

  • Business enquiries

    Up to 24 months

    Records are retained for up to 24 months after the last substantive exchange, then deleted unless a legal obligation, dispute or active commercial relationship requires a longer period.
  • Rate-limit entries

    15 minutes

    Entries stop counting after 15 minutes and are removed on the next request or when the server instance ends.
  • Deletion requests

    Identify the work email used in the enquiry. Do not send identity documents unless the privacy contact asks for a proportionate verification step.

Record 06

You can inspect, correct or remove the enquiry record.

Where possible, send the request from the work address connected to the original enquiry.

  • Access and correction

    You may ask what contact information is held and request correction of an inaccurate business record.
  • Erasure

    You may request deletion of the enquiry from the receiving mailbox and configured CRM, subject to any legal obligation to retain it.
  • Withdraw the enquiry

    You may ask us to stop follow-up at any time. Withdrawal does not affect processing that was lawful before the request.
  • Escalation

    Include the work email used for the enquiry and the action you want us to take. Do not attach identity documents unless we ask for a proportionate verification step.

Privacy contact

Use this route for access, correction, erasure, withdrawal and privacy concerns.

Praman Labs

Everyone verifies documents. We verify people.

Product

OverviewPersonhood ScoreCluster IntelligenceV-CIP IntegritySleeper WatchWorkbench

Solutions

OverviewNBFCs and digital lendersBanks and SFBsInsurersPayment aggregatorsBrokers and AMCs

Technical

How it worksPrivacy architectureModel governanceSecurity

Company

ResearchEngagementCompanyCareersContact

Legal

PrivacyTerms

Application-time personhood scoring for Indian financial institutions.

© 2026 Praman Labs