Cookie Policy
1. Scope and operator
This policy explains cookies and similar technologies used by Sincliq Inc., 1000 Northwest Street, Mid-Town Brandy Wine, Suite 1200, Wilmington, DE 19801, USA, on the Sincliq website and in functions that refer to this document. It covers public pages, privacy preferences and, when requested, sign-in, the customer panel and order management. It does not mean that every available tracking technology is in use. A merchant's systems, partner applications and externally linked services may have their own policies. Contact about this policy: hello@sincliq.com.
2. Cookies, local storage and logs
A cookie is a small record that a browser may send with later requests to the relevant domain. localStorage keeps information for an origin, including its domain and protocol, until it is removed or overwritten; it is not automatically attached to every request. sessionStorage belongs to a browser tab's session. Local storage does not automatically mean disclosure to an advertiser. Separately, the server receives data needed to deliver a page, such as an IP address and request details. Blocking cookies does not stop server communication itself. Personal-data processing is described in the Privacy Policy.
3. Necessity and voluntary choice
We distinguish mechanisms needed for communication, security and expressly requested functions from optional mechanisms. Authentication following a sign-in request and remembering a privacy decision are not marketing consent. Rejecting optional categories does not prevent reading the public offering. Not every record is created on a first visit: some arise only after sign-in, a settings change or an order-status request. Necessity is assessed against the specific purpose and scope, not merely a tool's name or a label in the preference panel.
4. Recording your privacy choice
Our localStorage entry sq_cookies_v1 contains category choices for necessary, analytics, ads and targeting, together with the save date. It remembers the decision and displays saved preferences; it does not contain payment-card details or passwords. The necessary category remains enabled. This entry has no configured automatic expiry: it remains until a choice is changed, site storage is cleared or the browser removes it. Its internal timestamp is not an automatic deletion deadline. Removing it causes the choice prompt to appear again on a later visit.
5. Sign-in and user session
Account functions use Supabase Auth. Browser storage may contain session entries, particularly the project-specific sb-…-auth-token key. These maintain and refresh authentication, not advertising. Token validity and the lifetime of a localStorage entry are different: a token can expire or be refreshed while the entry remains. Signing out removes the current session managed by the application; site data can also be cleared. Do not copy these entries into messages, screenshots or reports. Different domains may hold separate sessions.
6. Remembered device
If you choose to remember a device during an additional sign-in confirmation, our sincliq_urzadzenie cookie may be set for a maximum of 90 days. It contains a random trust identifier associated with the account on the server, not the account password. It uses HttpOnly, Secure and SameSite=Lax attributes to recognize a previously confirmed device. Signing out does not automatically revoke trusted-device status. You can manage devices through the available account settings or delete the cookie; removing trust may require a new sign-in confirmation.
7. Panel settings and language
Panel functions store selected preferences in localStorage: sincliqJezyk for language, sincliqMotyw for theme, sincliqPasekZwiniety for the navigation layout and sincliqNotif for notification settings. The older nuvioNotif entry may be read to preserve an earlier choice. These interface settings are not evidence of consent to every marketing channel. They have no automatic local-storage expiry; changing a setting overwrites its value. The guest QR payment language, sincliqCheckoutJezyk, uses sessionStorage associated with the tab session, not a persistent advertising identifier.
8. Orders and abuse prevention
On the retained legacy hardware order-status page, sq_zam_email in localStorage may remember the email address entered to simplify later status checks. This is personal information stored on the device without automatic expiry, not marketing consent. Clear site data after using a shared device. sincliqResetKody contains timestamps of password-recovery requests and limits repeated sending. The limit considers the previous hour, but the local record does not automatically expire after one hour. Clearing these entries does not delete the order or account from the system.
9. Payment-form technologies
After a relevant payment function is opened, the site may use Adyen components and connections needed for the chosen method, authentication or fraud prevention. The payment components currently have the SDK analytics option disabled. This does not disable communication necessary to process a payment. Provider and bank mechanisms depend on the method and transaction stage; their privacy notices govern processing they carry out in their own roles. Merely opening a pricing page is not an instruction to make a payment.
10. Analytics, advertising and personalization
The website's current first-party preference mechanism stores choices but does not activate analytics, advertising or cross-site tracking tools through them. A visible category does not mean a provider is enabled. Accepting a category is not consent to undisclosed future tools, unrestricted data combination or transfers to any country. Introducing new technologies that require consent requires prior information about the provider, purposes, data and duration, and the appropriate choice before activation.
11. Changing choices and browser controls
Open “Privacy settings” in the footer of the home or product pages to reject optional categories, save selected settings or change an earlier decision. From a standalone legal page, use the Sincliq return link to reach that footer. Choices apply to the current browser and domain; they do not automatically synchronize across devices or between development and production sites. Browser controls independently allow blocking or deleting site data. Blocking storage may prevent persistent sign-in or settings, but it neither withdraws a statutory privacy request nor deletes information held on the server.
12. Market-specific rules
In the United States, obligations depend on applicable state law, the processing involved and statutory applicability criteria. Where the CCPA/CPRA or other state privacy laws apply, rights may include opting out of selling personal information, sharing for cross-context behavioral advertising and targeted advertising. Selecting the US market does not alone determine those rights. The current preference panel records local choices; it is not an automated Global Privacy Control (GPC) handler or confirmation that an account-wide request has been fulfilled. The website mechanism described here does not activate advertising tools; applicable statutory rights remain unaffected.
13. External links and AI services
ChatGPT, Gemini, Perplexity and Grok icons link to separate services with a prepared question about Sincliq's public offering or allow that question to be copied. They are not tracking tools activated by the preference panel. Opening a provider sends it a browser request; a prepared link may transmit the question in the address. Further cookies and processing follow the provider's rules. Do not include customer information, payment details, passwords or business secrets in questions. Rejecting optional categories at Sincliq does not change an account's settings with another provider.
14. Duration, recipients and transfers
The durations above concern device storage, not the full retention of personal information. Session storage generally ends with the tab session, although browser session restoration can restore its contents. localStorage entries remain without automatic expiry unless stated otherwise for the mechanism. Infrastructure, authentication and payment services may receive data necessary for the requested function. Access, legal bases and international-transfer safeguards are addressed in the Privacy Policy. Cookie consent does not replace a required legal mechanism for transferring personal data outside the EEA.
15. Contact and updates
Send questions about storage or an unexpected tool to hello@sincliq.com, stating the page address, approximate time and browser. Do not send session tokens or complete browser-storage exports. Access, deletion and objection requests follow the Privacy Policy; a technical report does not limit those rights. We update this document when the described use of technologies changes. Publishing a new version does not replace required consent or retroactively extend the purpose of an earlier choice.