Skip to content

Sign in to SYO

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

or use your email

Privacy policy

Understand what stays in your browser, what is saved to a Case File, and what can be sent to an assistant.

Last updated: 31 October 2026. SYO (Settle Your Own) is operated personally by Mayank Dholakhandi. Privacy questions and requests can be sent to privacy@settleyourown.in.

This policy describes the current product design. Runtime availability, provider settings and production data practices must match this policy before launch. Independent legal approval or a privacy certification has not been established.

Contractual service provisions are in the Terms of Use, including warranty disclaimers, liability limits, indemnification, termination rights, Indian governing law and arbitration for eligible disputes. Those provisions do not waive mandatory privacy rights or authorize processing beyond a lawful basis. Privacy choices, including analytics consent, are separate from acceptance of a contractual arbitration agreement.

What this policy covers

It covers the public SYO website and the Resolve and Formal Notice workspace. SYO helps you organize an overdue-payment claim. A browser draft, an assistant suggestion and a confirmed Case File record have different storage and authority.

A deployment with missing backend configuration may show an unavailable workspace. Public pages do not create a Case File simply because you visit them.

Information you provide

  • Account information: your sign-up email and authentication information, processed through Supabase authentication when you create or use an account. If Google sign-in is enabled and you choose it, Google and Supabase process the sign-in and provide your account identifier, email and basic profile information, such as your name and profile picture, to support your SYO account. SYO does not receive your Google password or request access to Gmail, Drive or Calendar.
  • Claim details: creditor and counterparty names and contact details, claim description, invoice reference, overdue amount and due date.
  • Workflow records: confirmed facts, reminder drafts, communications you mark as sent, responses, follow-up dates, payments, settlement terms and outcomes you record.
  • Formal Notice material: reviewed notice content, revisions, generated PDFs and dispatch or proof information you explicitly record through available controls.
  • Assistant conversation: messages you type, replies and case context used to explain or propose the next step.

Provide only information needed for your claim. Avoid passwords, identity-document numbers, bank credentials, medical information or unrelated personal information. Information about a counterparty can be personal data too; you are responsible for having an appropriate reason to provide it.

Browser drafts and local storage

Guest facts, conversations, reminder previews and guest-session tokens are held in the current tab’s memory. Closing or reloading the page clears them. Saved Case Files are separate server records. Authentication uses secure cookies that page scripts cannot read, with a 30-minute inactivity limit and an eight-hour maximum session.

“In this tab” describes where a provisional draft is retained. It does not mean every action stays offline. Guest-session, reminder-preview and assistant requests can send the relevant input to SYO’s server. Using the assistant can send it onwards to the AI provider described below.

Tab memory is not an account backup. Reloading, closing the tab or signing out clears current drafts and transcripts. The application removes its older local draft and authentication records when initialized. Sign out on a shared device and manage downloaded files separately.

Saved Case Files and documents

When you sign in and explicitly save or confirm a supported action, SYO’s server uses Supabase to store the account-owned Case File and its recorded events. The assistant does not become the authoritative record simply by proposing a fact or an action.

Formal Notice revisions, PDF bytes and proof records are handled through authenticated, ownership-checked server routes and private database records. They are not intended to be published in the public website or sitemap. Downloads create another copy on your device; you control any copies you share outside SYO.

Generating a draft or PDF does not deliver it to the recipient. If you send a communication through email, WhatsApp, post or another service, that service’s handling of the information is separate. SYO records the action you confirm.

Optional assistant processing

When configured and used, the assistant processes data through Microsoft Azure OpenAI. The current-message extractor receives the message you just typed. The reply step can receive that message, up to eight recent conversation entries, suggested facts, and either your provisional facts or a projection of the saved Case File.

That case projection can include names and contacts, amounts, dates, response notes, settlement terms and recent event summaries. These inputs are not automatically anonymized. You can use the structured workflow controls without relying on an assistant reply.

The application requests AI responses with provider response storage switched off (store: false). This does not establish that Microsoft retains no operational, security or abuse-monitoring data. Provider contractual settings, region, processing terms and retention need to be confirmed for the production deployment. No model-training exclusion or residency guarantee is claimed here.

Service operations and optional analytics

SYO uses authentication, ownership checks and rate limits to operate the workflow and reduce misuse. Rate-limit processing can use an HMAC-derived identity from a user or network address. Hosting and service providers can also process connection and request information needed to serve the site. This is separate from optional audience analytics.

Optional Google Analytics is available on SYO’s public pages. It stays off until you choose Allow optional analytics in Cookie settings. If you have not chosen yet or reject optional analytics, this integration does not load Google Analytics or send analytics requests, including consent-mode pings. You can use SYO without allowing analytics.

After consent, the integration measures selected public page visits, with automatic page views disabled and the referrer blanked. It excludes the workspace, case and user IDs, query strings, amounts, contacts and messages. Advertising features are disabled by the integration. Entering the workspace unloads the public analytics environment.

After opt-in, Google can receive the public-page event, browser and connection information, and use analytics identifiers. Open Cookie settings to reject or withdraw; withdrawal stops future collection and attempts to remove this integration’s first-party GA cookies. It cannot retract events already sent. See the cookie policy.

Access, retention and your requests

The current application uses account ownership checks to restrict case access. These controls reduce risk; they are not a guarantee against every security failure. SYO does not sell case data through the described workflow or publish it as a customer case study.

A production retention schedule, account-deletion workflow, backup-deletion process and response timetable have not been confirmed. No automatic deletion period is promised. Clearing browser storage does not delete server records, and recording a case as withdrawn is a workflow outcome, not a data-erasure request.

For access, correction, deletion or privacy questions, contact privacy@settleyourown.in. Identify the account and describe your request; do not email your password or unnecessary claim evidence. Identity and applicable legal requirements may need to be checked before a request can be fulfilled. No response SLA is represented.

Providers, transfers and updates

Supabase supports account and persistent workflow processing; Microsoft Azure OpenAI supports the optional assistant; Google supports optional Google sign-in when chosen and consented public-site analytics. Google sign-in and optional analytics are separate choices: signing in with Google does not grant analytics consent. Their actual production regions, contracts, subprocessors and transfer arrangements must be verified. An India-first product does not establish that all processing stays in India.

We will update this policy when the operational practices change. Material new processing should be explained before it begins, with consent sought where required. The data handling page gives a practical overview, and the terms of use explain the service boundaries.

Have an overdue payment?Start in Resolve