QRCraft

QR Experience Builder

Back home

Subprocessors

QRCraft Subprocessors

This page lists the core third-party providers that support QRCraft today, the role they play, and the main categories of data they may process on our behalf or alongside our service.

Last updated

March 30, 2026

Operator

TECHVENTIVE IT SOLUTIONS PRIVATE LIMITED

Contact

connect@techventive.in

1. Current providers visible from the product codebase

The current product codebase shows a small provider footprint. We publish this list so customers and reviewers can understand the main service dependencies currently visible in the repository.

  • Clerk: authentication, session management, account identity, and legal consent metadata tied to signed-in users.
  • Razorpay: payment processing, subscription creation, customer records, webhook verification, and subscription state updates.
  • Neon Postgres: application database for users, workspaces, QR records, invite records, billing metadata, privacy requests, and scan counts.
  • Vercel: application hosting and deployment infrastructure.
  • Outlook: support inbox operations and operational communications.
  • Theme/local preference tooling via next-themes: browser-side theme preference persistence using local storage or similar browser storage behavior.

2. Main data categories by provider role

Different providers process different data depending on their function. QRCraft keeps the provider footprint intentionally narrow, but users should still expect provider-side processing tied to core SaaS operations.

  • Authentication providers may process account identifiers, email addresses, sign-in metadata, device/session metadata, and account security logs.
  • Payment providers may process billing contact details, subscription identifiers, payment method workflows, tax or bank data handled inside the provider environment, and payment event metadata.
  • Database and infrastructure providers may process stored workspace records, QR configuration records, invite data, logs, and normal application request traffic.
  • Browser-side preference tooling may process local preference state, browser metadata, and normal application-delivery requests in the ordinary course of service delivery.

3. Change management

This list is based on the current repository and known product dependencies. We may change providers over time as the product evolves, and we expect to update this page when material provider changes are introduced.