Privacy

TitleChk processes your email address, uploaded documents, extracted text, review results, chat history and payment references to provide the service. Property documents may contain personal information; upload only information you are authorised to share.

Processing and storage

Original files are kept in private object storage. Application records and retrieval embeddings are stored in TitleChk’s database. Access is scoped to your account’s workspace. Extracted passages and selected images may be sent to configured AI service providers for analysis. Provider requests use the account’s configured data-retention restrictions; we do not claim that AI analysis is performed entirely on your device.

Authentication and payments

We send one-use email sign-in links and store hashed session tokens. Razorpay handles card, UPI and other payment information; TitleChk retains payment identifiers, amounts and account credits, not card numbers or banking credentials. Essential cookies maintain your sign-in session.

When you purchase through Microsoft Marketplace, Microsoft handles payment details. TitleChk verifies the purchase using Microsoft subscription and purchaser identifiers, verifies your Microsoft work account and connects the purchase only after you sign in to your own TitleChk workspace. We report the subscription identifier, usage hour and number of property checks to Microsoft for billing. Property documents, party names, chat content and reports are not included in these billing events. Marketplace setup uses a short-lived essential cookie. An email match alone does not link accounts.

Retention and requests

We retain documents and outputs so you can revisit your property file. Workspace owners can request exports and delete properties through Account settings when data controls are enabled. Deleted properties are hidden immediately and can be restored for 30 days. Permanent removal follows the published recovery period and operational retention controls. Contact support after signing in for correction, account recovery or privacy requests. Payment and audit records may need to be retained separately. Deleting an active record may not immediately remove copies from backups. Daily database backups currently have a dated expiry, while some manual recovery snapshots have no automatic expiry and require separate removal. We have not enabled automatic permanent purging pending a verified backup restore and retention review. Requests already sent to external processors are subject to those providers’ retention and deletion controls; deleting a property does not recall an already-started request.