Synergy 0.0.1 alpha is here.See what's new
Synergy
Legal

Cookie policy

This policy explains the cookies and similar technologies used on the Synergy website, including the checkout cookie, Clerk authentication cookies, Razorpay payment cookies, and cookies set by Google, GitHub, or Discord when you choose one of those sign-in methods. We currently use only strictly necessary cookies. We do not use advertising cookies or third-party analytics.

Last updated · 5 November 2026

1. Who controls cookies

Synergy (“Synergy”, “we”, “us”) controls the cookies set by this website. Our business is based in Bengaluru, Karnataka, India. Contact us at support@synergy.arnislive.com with the subject “Cookie request”. Our privacy policy explains how we handle personal data more generally.

This policy does not control cookies set by third-party websites. When you use Clerk, Razorpay, Google, GitHub, Discord, or another provider, that provider may set its own cookies under its own policy.

2. What cookies and similar technologies are

Cookies are small text files stored by your browser. Similar technologies include local storage, session storage, pixels, SDKs, and server-side identifiers. They can keep you signed in, remember a checkout, protect against fraud, or measure how a site is used.

Session cookies expire when you close the browser. Persistent cookies remain until they expire or you delete them. First-party cookies are set by our domain; third-party cookies are set by another domain, such as a payment or sign-in provider.

3. Strictly necessary cookies we use

These cookies are required for the Service to work. They do not require consent under the ePrivacy Directive, UK PECR, or similar laws because the Service cannot function without them.

synergy_order (first party). A short-lived, signed, HttpOnly cookie set after checkout so the success page can identify the order you just completed. It is SameSite=Lax, marked Secure in production, and expires after 2 hours. It contains an order identifier and an HMAC signature, not your card details.

Clerk authentication cookies (first party, via Clerk). If accounts are enabled and you sign in with an email code, Google, GitHub, or Discord, Clerk sets session and anti-CSRF cookies needed to keep you signed in, protect your account, and complete the OAuth redirect. Clerk may also use local storage or similar storage for session state. Durations are set by Clerk and may include a short-lived session cookie and a longer-lived client cookie.

Razorpay cookies and storage (third party). When you proceed to payment, we load Razorpay Checkout from Razorpay’s domain and open Razorpay’s payment interface. Razorpay may set cookies, local storage, device identifiers, or similar technologies on its own domains to process the payment, remember payment-method choices, prevent fraud, and secure the transaction. These are controlled by Razorpay, not us, and are subject to Razorpay’s cookie and privacy policies.

OAuth provider cookies (third party). If you choose “Continue with Google”, GitHub, or Discord, you leave our site for the provider’s authorization page. Google, GitHub, or Discord may set cookies on their own domains before returning you to Clerk. We do not control those cookies. Review the provider’s cookie and privacy settings if you do not want them.

4. Analytics, advertising, and cross-site tracking

We do not currently use Google Analytics, advertising pixels, cross-site behavioural advertising, or third-party analytics. We do not sell personal data and we do not share it for cross-context behavioural advertising. The only cookies are those needed for checkout, authentication, payment processing, security, and fraud prevention.

If we add analytics, advertising, or other non-essential cookies, we will update this policy, add the relevant consent mechanism where the law requires it, and honour applicable opt-out signals.

5. Consent and your choices

Because we use only strictly necessary cookies, we do not show a non-essential cookie consent banner. Where the law requires consent for a cookie or similar technology, we will ask before setting it.

You can block, delete, or restrict cookies in your browser. Blocking the checkout cookie may prevent the success page from showing your order. Blocking Clerk cookies will prevent you from signing in or staying signed in. Blocking Razorpay cookies or storage may prevent payment. Clearing cookies does not delete your account, order, or license.

If you are in India, we handle cookie data as part of your consent to the Service or another lawful basis under the Digital Personal Data Protection Act, 2023. If you are in the EEA or UK, strictly necessary cookies rely on the ePrivacy/PECR exception. If you are in California, we do not sell or share personal information for cross-context behavioural advertising, and we honour Global Privacy Control where required. You can also contact us to exercise your privacy rights.

6. Third-party links and payment pages

Our site links to Razorpay, Clerk, Google, GitHub, Discord, Telegram, and other services. Their cookies and privacy practices are their own. We encourage you to read their policies before signing in or paying. A link to a third party is not an endorsement of its cookie practices.

7. How long cookies last

The checkout cookie expires after 2 hours. Clerk and Razorpay set their own durations, which may range from a single session to a longer period. Browser and device settings can remove them sooner. Server-side records linked to a cookie are kept for the periods described in our privacy policy.

8. Changes to this policy

We may update this policy if we add or remove a cookie, change a provider, or the law changes. We will post the updated version and change the “Last updated” date. If a change requires consent, we will ask for it before the change takes effect.

9. Contact and complaints

Cookie questions and privacy requests go to support@synergy.arnislive.com with the subject “Cookie request”. You can also message us on Telegram at @ARNISLIVE or on Discord at @ARNISLIVE. If you are not satisfied, you may complain to the data-protection authority in your country.

See also our privacy policy, terms of service, and refund policy.