Skip to content

Sign in to SYO

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

or use your email

Cookie policy and settings

Optional analytics is off by default. Essential browser storage supports the work you choose to do.

Last updated: 31 October 2026. SYO is operated personally by Mayank Dholakhandi. Contact privacy@settleyourown.in about privacy or browser-storage questions.

Change your choice

Use Cookie settings at the bottom of this page to allow, reject or withdraw optional analytics. Rejecting is a complete choice: the website and available structured workspace controls remain usable.

Optional Google Analytics is available after consent. Cookie settings provides Allow optional analytics and Reject optional analytics. Visiting a page, leaving the choice unanswered or dismissing settings does not provide consent. Analytics stays off until you explicitly allow it, and stays off if you reject it.

Withdrawing turns collection off and resets the page if a Google tag was loaded, so its listeners do not continue running. Unsaved public-page interaction can be lost in that reset. The integration also attempts to expire its first-party GA cookies. Withdrawal cannot remove an event already sent to Google.

Cookies and local storage are different

Cookies are small records that a browser can attach to requests. Local storage keeps records in this browser for a particular site and is not automatically sent with every request. Applications can read a local record and send selected information when an action needs it. This policy explains both.

The public site does not need to connect to the Case File backend just to render its informational pages. Authentication and workflow storage are used when you enter and use the available workspace.

Essential storage used by the current workflow

  • Privacy preference: a local-storage record named syo:analytics-consent:v1 remembers whether you accepted or rejected optional analytics. It contains the choice, not your claim content.
  • Account session: authentication uses HttpOnly, Secure cookies with SameSite=Lax in production. Page scripts cannot read the credentials. Sessions expire after 30 minutes of inactivity or eight hours in total.
  • Sign-in verification: when you start a supported sign-in flow, the server stores a PKCE code verifier in an HttpOnly cookie to connect the return to that browser. Use the same browser and site origin to finish sign-in.
  • Guest draft: provisional claim facts, conversations, reminder previews and tone are held in the current tab’s memory. Reloading or closing the tab clears them.
  • Guest-session token: a signed guest-session token is held in tab memory and expires independently of the draft.
  • Local case conversation: signed-in workspace transcripts are held in memory for the current account and case. The authoritative saved Case File is a separate server record.

These records support the requested functionality, rather than public-site audience measurement. They are not switched off by rejecting analytics. When authentication initializes, the application removes its older locally stored drafts, transcripts and authentication tokens.

If you choose Google sign-in when enabled, you visit Google’s sign-in pages, where Google may use its own cookies and process account and connection information under its privacy practices. This optional sign-in choice does not grant permission for SYO’s optional Google Analytics.

Optional Google Analytics

After you allow optional analytics, Google Analytics receives manually reported visits to selected public pages. The integration disables automatic page views, supplies the public path with a blank referrer, and disables Google signals and advertising-personalization signals. The production Analytics property must also have automatic enhanced measurement disabled before use.

Workspace routes, case and user identifiers, query strings, claim amounts, contacts and conversation text are excluded from page events. Moving from a public page into the workspace opens a separate document so that the public analytics script is not carried into the workspace.

Google may process browser and connection information and create analytics identifiers after opt-in. Its standard first-party GA4 cookies can include _ga and _ga_…. Cookie and event retention depend on Google’s cookie behaviour and the Analytics property settings; no fixed retention duration is promised here.

No Google Analytics script or request is initiated by this integration before explicit opt-in. There is no consent-mode ping before consent. If the measurement ID is absent or invalid, analytics remains inactive.

Storage failures, shared devices and deletion

If browser storage is blocked or full, your privacy choice can apply only in the current tab and may be asked again. The fallback remains off until you explicitly allow it. Changing the stored choice in another tab is reflected when the browser reports that change.

You can manage cookies and site data in your browser. Clearing site data may sign you out or remove guest work and locally retained conversations. It also removes the saved preference, so the site asks again with analytics off.

Signing out clears the current tab’s drafts and transcripts. Closing or reloading the tab clears them too. Downloaded documents remain under your control. Clearing browser storage does not erase saved Case Files, notices, proof records or provider records on servers.

For server-data requests, use the contact in the privacy policy. The data handling page explains the distinct processing boundaries.

Have an overdue payment?Start in Resolve