Cookie Policy

Last updated: September 23, 2026. This policy applies to Support14.com and its online customer-support services. It is written for a U.S.-based online service that may serve customers in other jurisdictions. A law mentioned below applies only when its legal scope and thresholds are met.

1. What cookies are

Cookies are small data files placed on a browser or device. Support14.com may use cookies and similar technologies to keep customers signed in, protect accounts, remember security state, and support basic site functions. The base site is designed so essential functionality does not depend on advertising cookies. A cookie normally contains a small identifier rather than the contents of a customer’s ticket.

2. Essential session cookies

When a customer logs in, Support14.com uses a session cookie so the server can recognize the authenticated session as the customer moves between pages. Without this cookie, the ticket dashboard, account pages, and secure ticket submission flow would not function correctly. These cookies are operational rather than promotional and are intended to expire when the session ends or according to the configured session lifetime.

3. Security tokens

The site may use short-lived tokens for form protection, including measures intended to reduce cross-site request forgery. Password-reset links use separate random tokens and are designed to expire after a limited period. These technologies support account security and are not intended to track customers for advertising purposes.

4. Optional analytics

The base Support14.com build does not require third-party advertising trackers. If analytics are later enabled, the service should disclose the provider, categories of data, purpose, retention, and available choices. Where a jurisdiction requires prior consent for non-essential cookies, the site should obtain that consent before setting them. Analytics should be configured to collect no more information than reasonably necessary for the stated purpose.

5. California privacy law

California privacy law can regulate online identifiers and may require disclosure about collection and use. The California Attorney General explains that businesses covered by the CCPA have obligations concerning notice at collection, privacy policies, and consumer rights. Support14.com is not designed around selling or sharing support-ticket information for cross-context behavioral advertising.

6. European Economic Area and United Kingdom

For users protected by the GDPR or UK GDPR, cookies that are not strictly necessary may require consent depending on how they are used. Users may have rights to withdraw consent and to exercise other data-protection rights. Essential authentication and security technologies may be treated differently where they are necessary to provide a service requested by the user. Consent choices should be clear, specific, informed, and capable of being withdrawn where required.

7. Managing cookies

Most browsers allow users to block, delete, or restrict cookies. Disabling essential session cookies may prevent login and ticket functionality. Browser controls differ by device and browser version, so users should review their browser’s privacy settings for current instructions. Clearing cookies may also sign a customer out of Support14.com and remove local preferences.

8. Do Not Track and Global Privacy Control

Browser privacy signals may be relevant to certain forms of online tracking and California law. If Support14.com engages in a practice for which a legally recognized signal must be honored, the site will implement the applicable technical response. The service is not intended to sell or share support-ticket information for cross-context behavioral advertising.

9. Third-party content

External websites linked from Support14.com may use their own cookies after a customer leaves the site. This policy does not govern independent third-party websites. Customers should review those services’ privacy and cookie policies. A third-party provider may also set a cookie if a future Support14 feature embeds its service; such use should be disclosed when material.

10. Cookie security

Cookies do not replace account security. Where supported by the hosting configuration, authentication cookies should use secure transmission and appropriate HttpOnly and SameSite settings. Customers should avoid signing in on untrusted public computers. If a customer believes a session was stolen, the customer should reset the password and contact support.

11. Retention

Cookie lifetimes vary by function. Session cookies generally last for the session, while security tokens are intentionally short-lived. Optional preference or analytics cookies, if later added, should have a documented retention period appropriate to their purpose. Server-side ticket and account retention is governed by the Privacy Policy rather than by this Cookie Policy.

12. Children

The site does not intentionally use cookies to profile children. If a future analytics or advertising feature could materially affect children, the operator should review the applicable child-privacy requirements before enabling it. U.S. COPPA and other laws may impose special requirements for services directed to children or knowingly collecting information from them.

13. Accessibility

Cookie choices and essential login functions should remain usable with keyboard navigation and assistive technologies. If a cookie banner or preference control is added later, it should use accessible labels, focus management, and clear action names. The U.S. Department of Justice has emphasized that inaccessible web content can prevent equal access to information and services.

14. Changes

Cookie technologies can change as the service evolves. This policy will be updated when material changes occur. The revision date at the top indicates when the current version was posted. If a new category of non-essential tracking is introduced, the site should update its disclosures and consent process before deployment where required.

15. Contact

Questions about cookies can be submitted through Support14.com. Please do not include passwords or other confidential authentication information in a cookie-related support request. Customers who cannot log in because cookies are blocked should first check browser privacy settings and then use the password or support options available to them.

16. Essential versus optional technologies

A practical distinction exists between technologies required to provide a feature a customer specifically requests and technologies used for unrelated measurement or advertising. A login session is directly connected to the customer’s request to access a private account. An advertising identifier used to build a profile across unrelated websites serves a different purpose. Support14.com is designed to rely primarily on essential technologies for its core support workflow.

17. Consent records

If the site later adds a consent-management system for non-essential cookies, the operator should maintain appropriate records of consent choices when required. A consent mechanism should explain categories in understandable language and avoid treating continued browsing as consent where the applicable law requires an affirmative action.

18. Withdrawal of consent

Where a cookie requires consent, users should have a reasonably easy method to withdraw that consent. Withdrawal does not necessarily require deleting essential cookies because essential session technology may still be needed for a requested account function. When consent is withdrawn, optional technologies should stop being used as required by the applicable rules.

19. Server logs are different

Cookies are not the only technical records generated by a website. Web servers may create logs containing IP addresses, request paths, response codes, timestamps, and security information. These records are addressed more broadly in the Privacy Policy because they can exist even when cookies are blocked.

20. Email links and tracking

Support14.com may send account and ticket emails. The base support workflow is not designed around marketing tracking pixels. If marketing or engagement tracking is added in the future, the operator should assess applicable privacy and electronic-communications requirements and update the relevant disclosures before enabling the feature.

21. Browser settings

Browser cookie controls vary. Some browsers can block third-party cookies while allowing first-party session cookies. Others provide broader site-specific controls. Customers should understand that strict privacy modes can interfere with account sessions, password reset flows, or embedded content. The operator cannot control browser behavior on the customer’s device.

22. Security and cookies

Cookies are one component of security rather than a complete security system. A secure account also depends on password strength, HTTPS configuration, server-side authorization, session expiration, and the security of the customer’s device and email account. Customers should report unexpected logins or suspicious account activity promptly.

23. Updates

Technology providers may change cookie names, domains, retention periods, or purposes. The operator should review this policy when the website changes materially. Customers should consult the current version rather than relying on an old copy saved elsewhere.

24. Legal basis and necessity

For users protected by data-protection laws, the operator should distinguish cookies that are necessary to provide a requested service from cookies used for additional purposes. Authentication, security, and session functions are directly connected to the customer’s requested use of the private support center. Non-essential tracking may require a separate legal basis or consent depending on jurisdiction.

25. Cookie preference changes

If Support14.com later provides a cookie-preference center, customers should be able to review available categories and change non-essential choices without being forced to delete their entire browser history. A preference center should not interfere with the ability to log in or submit a support request when essential cookies remain enabled.

26. Third-party processors

If a third-party analytics, security, chat, or support provider sets cookies, the operator should identify the provider and purpose in an updated disclosure where required. A provider’s own cookie practices can also apply. Customers should review the provider’s documentation when they need more detail than can reasonably be included on this page.

27. Security limitations

A cookie can be copied or misused if a device or browser is compromised. Customers should use updated browsers, avoid untrusted extensions, and protect their devices. Support14.com can apply server-side authorization checks, but no cookie mechanism can compensate for a compromised customer device in every circumstance.

28. Regulatory change

Cookie and privacy laws continue to evolve. Rules can differ between U.S. states, European countries, the United Kingdom, Canada, Brazil, and other jurisdictions. Support14.com may update this policy and its technical configuration when a material legal or service change requires it.

29. User questions

If you have a question about why a cookie is present, submit a support request and identify the browser and page involved. Do not send the cookie value itself, because session identifiers can be sensitive security information.

30. Cookie inventory changes

The exact names and technical attributes of cookies can change when software or hosting components are updated. A cookie may be renamed without changing its purpose, or a provider may replace one technical identifier with another. For that reason, this policy describes categories and purposes rather than promising that a particular cookie name will remain unchanged forever.

31. Local storage and similar technologies

Modern browsers can store information using technologies other than traditional cookies, including local storage and session storage. If Support14.com uses such technologies for essential session or preference functions, the same privacy principles should apply: use should be limited to a legitimate purpose, disclosures should be updated when material, and non-essential tracking should not be introduced without considering applicable consent requirements.

32. Privacy by design

The support center is designed to minimize reliance on advertising technology. Customers come to the site primarily to request help, not to receive behavioral advertising. Limiting third-party tracking can reduce unnecessary exposure of browsing information and simplify the security model for account and ticket pages.

33. Questions about browser privacy

Customers who want stronger browser privacy can review controls for cookies, site data, third-party content, tracking prevention, and private browsing. These settings can vary substantially and may affect site functionality. Support14.com can help identify whether a browser setting is interfering with login or ticket submission, but the operator cannot change settings on the customer’s device.

34. Policy hierarchy

This Cookie Policy should be read together with the Privacy Policy. The Privacy Policy describes the broader collection and use of personal information, while this page focuses on browser-based storage and similar technologies. If mandatory privacy law requires a different treatment, the applicable legal requirement controls.

35. Practical privacy expectations

Customers can reduce unnecessary tracking by keeping browser privacy settings enabled and declining non-essential technologies when a choice is provided. Support14.com’s core purpose is customer support, so essential session and security technologies should remain focused on providing that service. Customers should review the current policy whenever the site introduces a materially different analytics, advertising, personalization, or embedded-service feature.