VeloCrew processes customer content (tasks, locations, messages) as a processor on your instructions. This page is a buyer-friendly summary — your order form or enterprise MSA may supersede.
We collect account and usage data needed to run the service: identifiers (phone, email where provided), operational logs, device/browser metadata, and content your users submit in the product. We do not sell personal data. Sub-processors typically include cloud hosting (e.g. AWS region you select), maps/geocoding if enabled, WhatsApp/Meta when you turn on those integrations, and payment providers (e.g. Razorpay) when you pay in-app.
For enterprise customers we provide a DPA that covers: purpose limitation, confidentiality, security measures appropriate to risk, assistance for data subject requests where applicable, breach notification timelines aligned with your contract, deletion or return of data at offboarding, and Standard Contractual Clauses / transfer mechanisms if data leaves India.
Controller vs processor: Your company is the controller for worker and customer personal data you load into VeloCrew. VeloCrew acts as processor for that workspace data. For a few account-billing fields VeloCrew may act as controller — described in your commercial agreement.
Account owners can export and delete much of their workspace from the admin portal where features exist. For statutory erasure requests, tenant offboarding, or processor-assisted deletion (including backups per retention policy), email:
privacy@velocrew.in (or hello@velocrew.in if the alias is not yet live)
Include: company name, workspace ID if known, requester role, and whether the ask is erasure, export, or restriction. We respond within a reasonable period defined in your plan (enterprise SLAs available).
Commercial terms, acceptable use, and liability caps are provided at contract or checkout. Link your executed agreement here when available.