Skip to content

Sign in to SYO

Access your business’s Case Files and keep confirmed actions available across devices.

or use your email

Data handling and safeguards

A practical view of the information SYO processes and the controls around a user-owned Case File.

Last updated: 31 October 2026. Operator: Mayank Dholakhandi, personally operating SYO (Settle Your Own). Privacy contact: privacy@settleyourown.in.

This page describes controls present in the application and decisions that still require production confirmation. It is not a DPDP, GDPR, ISO or other compliance certification, a legal opinion, or proof of a security audit.

Four different information boundaries

  1. Public information: service explanations, guides, help and clearly labelled illustrative scenarios. A visit does not create a saved recovery claim.
  2. Provisional work: guest facts, conversation and reminder previews can be retained in browser storage. These remain proposals until a supported confirmation saves authoritative facts.
  3. Assistant processing: a message and relevant bounded context can leave the browser through SYO’s server and be processed by a configured Azure OpenAI assistant. Local retention is not an offline-processing promise.
  4. Confirmed records: an authenticated user’s Case File, events, notice revisions, PDFs and recorded proof are persisted through Supabase-backed server operations when the relevant action succeeds.

These boundaries help you understand both where information goes and which record should guide the next action. An assistant statement does not prove that a payment, sending action or case update occurred.

Case ownership and confirmation

Case and document routes verify the signed-in user and check account ownership before returning or changing private records. Server operations use authenticated identity rather than trusting a user ID supplied by an assistant or browser conversation.

Commands carry revision and request identifiers so that stale facts, conflicting changes and retries can be handled deliberately. The workspace separates suggestions from explicit confirmation and treats uncertain write results as unresolved until reconciled.

These are application safeguards. Their presence in source does not establish that every migration, provider policy or live deployment is configured correctly. Production permissions and access boundaries need verification against the actual deployed system.

What the assistant receives

The Resolve extractor receives the current message. The reply step can receive the current message, up to eight recent conversation entries, suggested facts and either provisional claim facts or a saved-case projection. Saved context can include contacts, balances, responses, settlement terms and recent event summaries.

The input is not automatically anonymized. Avoid unnecessary sensitive information. Model output is interpreted as a suggestion or explanation; it does not directly authorize a database command, sending action or stage transition.

Azure requests use store: false. This setting concerns provider response storage; it does not prove that every provider log or abuse-monitoring record is absent. Contracts, deployment region, transfer arrangements, training use and provider retention must be established before making broader claims.

Documents and communications

Formal Notice content and generated PDF bytes are associated with a specific owned case and revision. Download routes check access. Recorded dispatch and proof material is handled as private case information rather than public marketing content.

Generated content is a draft or artifact, not a lawyer-review certificate. You review and decide what to send. Email, WhatsApp, post and other external channels process whatever you choose to share under their own practices. SYO’s explicit dispatch record does not independently verify delivery or legal service.

Downloaded files and copies shared externally are outside the browser workspace’s control. Keep original evidence securely and consider the recipient and channel before sharing claim details.

Analytics and operational data

Optional Google Analytics is available after explicit consent and measures selected public page visits. Before you choose, or if you reject optional analytics, the integration stays off and sends no analytics requests. Workspace content, private identifiers and query strings are excluded. Entering the workspace unloads the public analytics environment.

Use Cookie settings to allow, reject or withdraw optional analytics. Withdrawal stops future collection and attempts to clear this integration’s first-party GA cookies; it cannot retract events already sent. Google sign-in and essential account storage are separate from analytics consent, so rejecting analytics does not prevent sign-in or use of the available workspace.

Authentication and rate limits are separate from analytics. Rate limits can process HMAC-derived user or network identities. The AI provider adapter’s operational-metadata hook is designed for content-free categories, token counts, timing and correlation information, rather than prompts or replies; a production telemetry sink is not established by that hook.

Hosting and providers can still process information needed to deliver and secure the service. A decision to reject audience analytics is not a claim that all server or network processing stops.

Retention, requests and practical precautions

No fixed production retention period, automated account-erasure workflow, backup-deletion schedule or deletion SLA has been confirmed. A case marked withdrawn remains a workflow record unless separately erased through a supported process. Deleting browser data does not delete persistent server records.

For access, correction, erasure or another privacy concern, write to privacy@settleyourown.in. State the account and the request without sending a password or unnecessary evidence. Identity, applicable rights and record-preservation requirements may need to be checked; no response deadline is promised here.

On a shared device, protect the account and manage local site data. Maintain separate copies of evidence needed for your claim. Review the privacy policy and cookie policy for more detail.

Production decisions that remain open

Provider contracts and regions, processing purposes and applicable lawful bases, retention and backup policies, request handling, incident response and any international-transfer requirements need confirmation for the launched service. No public office or registered-company identity is represented.

SYO’s India-first audience does not by itself establish India-only data residency or compliance with every applicable privacy law. Independent operational and legal review is required before claiming certification or legal approval. The terms of use explain the product’s limitations.

Have an overdue payment?Start in Resolve