Cookie Policy

1. What Are Cookies

Cookies are small text files that are placed on your device when you visit a website. They are widely used to make websites work more efficiently, provide a better user experience, and supply information to the site operators.

SecureCodingHub (operated by LimePlate, Inc.) uses cookies and similar tracking technologies to operate our platform, remember your preferences, and understand how you interact with our services.

2. Cookies We Use

3. Third-Party Cookies

We use a limited number of third-party services that may set cookies on your device. Our analytics provider collects anonymized, aggregated data about how visitors use our platform. This helps us understand usage patterns and improve the experience for all users.

We do not sell your data to third parties, and we do not use advertising cookies or tracking pixels for ad targeting purposes. Any third-party services we use are bound by their own privacy policies and our data processing agreements.

4. Managing Cookies

You have the right to decide whether to accept or reject optional cookies. You can manage your cookie preferences in the following ways:

• Browser settings: Most web browsers allow you to control cookies through their settings. You can set your browser to refuse cookies, delete existing cookies, or alert you when a cookie is being set. Consult your browser's help documentation for specific instructions.
• Opt-out: For analytics cookies, you can opt out by adjusting your cookie preferences when prompted on our platform, or by contacting us at privacy@securecodinghub.com.
• Do Not Track: We respect Do Not Track (DNT) signals sent by your browser. When we detect a DNT signal, we disable optional analytics tracking.

Please note that disabling essential cookies may prevent you from using certain features of the platform, including authentication and session management.

5. Cookie List

The following table provides details about each cookie we use:

6. Changes to This Policy

We may update this Cookie Policy from time to time to reflect changes in our practices or for other operational, legal, or regulatory reasons. When we make changes, we will update the "Last updated" date at the top of this page. We encourage you to review this policy periodically to stay informed about our use of cookies.

If we make material changes to how we use cookies, we will notify you by posting a notice on our platform or by sending you an email (if applicable) before the changes take effect.

7. Contact Us

If you have any questions about our use of cookies or this Cookie Policy, please contact us:

8. Why We Publish This in Addition to the Privacy Policy

Our privacy policy describes, at a high level, what personal data we collect and how we handle it. This cookie policy exists as a focused, operational view of one specific mechanism: the small text files that browsers store on your device and the role they play on our platform. Keeping the two documents separate makes it easier to answer two different questions. The privacy policy answers "what does SecureCodingHub know about me and why," while this policy answers "what is set in my browser when I use the platform, and what can I do about it."

The separation also reflects how the underlying legal frameworks treat the topic. Under the General Data Protection Regulation in the European Economic Area, the California Consumer Privacy Act in the United States, and Turkey's KVKK, you have the right to be informed about cookies, to refuse non-essential cookies, and to withdraw your consent at any time. We honour those rights regardless of where you access the platform from, which is why optional categories remain off until you opt in and why a clear opt-out path is always available through the controls described above.

9. How to Clear or Block Our Cookies

Every major browser exposes controls for viewing, clearing, and blocking cookies on a per-site basis. The exact menu paths change between versions, but the locations below are stable enough to use as a starting point:

• Chrome: Settings, then Privacy and security, then Cookies and other site data. You can clear cookies for a specific site or block cookies globally.
• Firefox: Settings, then Privacy and Security, then Cookies and Site Data. Use Manage Data to remove entries for a single domain.
• Safari: Settings, then Privacy, then Manage Website Data. Select the entry for our domain and remove it.
• Edge: Settings, then Cookies and site permissions, then Manage and delete cookies and site data.

Clearing essential cookies will sign you out and reset your in-session preferences. Clearing analytics or preference cookies will remove the corresponding data without affecting your account. If you would like a more complete reset, signing out and then clearing site data for our domain achieves both at once.

10. What We Never Use Cookies For

It is often easier to describe a policy by what it excludes. To make our position concrete, the following uses are off the table for SecureCodingHub cookies:

• No cross-site tracking. We do not follow you across other websites or attempt to build a profile of your activity outside our platform.
• No third-party advertising network integrations. We do not embed advertising network tags, do not place cookies for ad targeting, and do not sell or share data with ad exchanges.
• No fingerprinting. We do not combine browser, device, or network signals to identify you when cookies are absent or cleared.
• No silent re-identification. If you clear our cookies, we treat that as a clear signal and do not attempt to reconstruct your previous session through alternative means.

The boundaries above are deliberate. They reflect how a security-focused product should treat the people who trust it with their learning and their code, and they are designed to remain stable as the platform grows.