Cookie Policy

cohero is operated by Fenkil Technologies LTD. This Cookie Policy explains how cookies, browser storage and comparable technologies support the platform when you browse dreams, sign in, prepare a dream, back a Dreamer, review milestones or use chat. It applies on phones and computers and should be read with the Privacy Policy and Terms of Service.

A Dreamer seeks support for a personal goal and a Backer gives support; the same account may do both. Storage requirements follow the action you take rather than a marketing profile assigned to you. For example, maintaining an authenticated milestone review requires a working sign-in session, while remembering a display preference does not require information about the dreams you support.

This policy describes categories of storage and their retention rules, not a promise that every category is present in every browser visit. Exact implementation names, expiration values and whether a value is held in a cookie or another browser store can depend on the application version and authentication flow. Contact hello@coheroapp.com for help understanding a particular entry rather than assuming that an unfamiliar technical name is an advertising tracker.

A cookie is a small text value that a website asks your browser to retain. Depending on its settings, the browser sends that value with later requests to the relevant site, allowing the site to recognise a session or apply a technical setting. Cookies are not programs and do not, by themselves, give a site access to every file or password on your device.

Local storage is a browser database of small values associated with a website's origin. Unlike cookies, local storage values are not automatically included with every network request; application code reads them when needed. Local storage generally remains until the application removes it, the browser clears it, or you delete the site's data, rather than expiring through the cookie expiration mechanism.

Session storage is another browser facility, generally limited to a tab's browsing session. A session cookie is normally removed when the browser session ends, while a persistent cookie has a specified expiry or is removed earlier. Browser session restoration can preserve some session information, so closing a window is not a dependable substitute for signing out.

First-party storage is associated with the service you are visiting. A payment checkout opened on our payment partner's own site has its own storage context, even when you reached it from cohero. Browser restrictions, private browsing and embedded checkout settings may affect these contexts differently.

We use cookies and local storage only to operate the service you request, keep it secure and preserve essential choices about its presentation. We do not deploy third-party advertising cookies, advertising pixels, cross-site marketing identifiers or storage intended to build a profile for targeted advertisements. We do not sell personal data or make access to dreams conditional on agreeing to advertising tracking.

• Authentication storage keeps an authorised account signed in while it performs account actions.
• Language storage remembers the language you choose for the interface.
• Theme storage applies your selected light or dark appearance.
• Security state protects sign-in and other sensitive requests against misuse.

Strictly necessary describes the relationship between a technology and a requested function; it does not mean that every technical convenience qualifies automatically. In particular, storing a language or theme choice is limited to giving effect to your selection, not to measuring you across sites. We assess any proposed additional use separately and do not treat this policy as permission to introduce unrelated tracking.

Account records, dreams, messages and backing transactions are stored on our servers under the Privacy Policy rather than kept solely in cookies. Clearing browser storage does not erase those records, reverse a gift, release a milestone, cancel membership or delete an account. Those actions have their own authenticated processes and applicable policies.

When you sign in with your email address and password, authentication state allows later requests to be associated with your account. A session token is a credential or reference used for this purpose; it is not an advertising identifier. It enables functions such as viewing account information, sending messages, editing a draft and reviewing proof without requiring a password for every action.

The functional duration is the authenticated session, including any permitted session renewal. A token may cease to be usable because it expires, is replaced, you sign out, or security action invalidates it. We do not state a universal number of hours or days because that depends on the authentication configuration and the state of your session; contact hello@coheroapp.com for clarification about the current behavior relevant to your account.

Expiry of a credential and removal of a saved browser value are different events. A browser can retain an expired value until it is overwritten or cleared, even though the server no longer accepts it. Conversely, deleting the local value can end your access from that browser while account records remain on our servers.

Treat authenticated browser access as sensitive, especially on a shared phone or computer. Do not copy session values into a message, public report or screenshot; a valid token can grant access without revealing your password. If you suspect someone else has obtained access, sign out where possible and contact support for account-security assistance.

The language preference records the interface language you select so that navigation, labels and policy pages can open in the expected language. cohero supports English, Hindi, Arabic, Spanish, French, Portuguese and Chinese. Remembering a selection avoids asking you to choose again at each page transition and supports a consistent experience between account tasks.

The intended duration is until you choose another language or clear the relevant site data. If the preference is held in local storage, it has no automatic browser expiry and can remain between visits; if a cookie is used, its browser expiry may remove it sooner. Private browsing, storage limits or privacy settings may also prevent a choice from being remembered.

This value represents an interface preference, not verified nationality, citizenship, residence or ethnicity. We do not use a language choice as an advertising segment or as proof of which laws apply to you. Choosing Arabic also supports the intended right-to-left interface presentation where available, but it does not change your account role or financial obligations.

You may change the language through the available interface controls. Removing the saved choice may cause the service to use its default or the browser's available language information until you choose again. The English policy version prevails in a conflict between translations, subject to mandatory rights that applicable law does not allow us to exclude.

The theme preference remembers whether you select the light or dark appearance. Its purpose is to keep the interface readable and consistent across pages, including dream details, messages and milestone reviews. A presentation choice does not authorise any advertising, and we do not use theme selection to infer a medical condition or other sensitive characteristic.

The intended duration is until you change the selection or clear the relevant site storage. A preference in local storage normally persists without a built-in expiry; a cookie-based preference is also subject to the cookie's configured expiry. A browser reset, private session or device cleanup may remove it earlier, so the same account may appear differently on separate devices.

If you remove this value, the interface may return to a default appearance or follow an available device preference. You can select your preferred appearance again without changing your dreams, backings or membership. Signing out is designed to end authentication and need not remove a non-sensitive display preference.

Theme storage supports usability but cannot guarantee that every uploaded image, proof document or user-written message has suitable contrast. See the Accessibility Statement for the standard we target, limitations with user content and ways to request assistance. If a theme creates an access barrier, include the affected screen and chosen appearance when contacting hello@coheroapp.com.

Security tokens and related temporary values are used where needed to protect authentication and sensitive actions. Their purposes can include matching a request to the session that initiated it, checking that a return from a sign-in or checkout flow is expected, and reducing forged or repeated submissions. They are functional safeguards, not tools for recognising you on unrelated websites.

The intended duration is the protected action or relevant security session. A token can become invalid after use, at the end of the flow, when its server-side validity window ends, or when the associated session is invalidated. Some residual browser entries can remain until overwritten or cleared even after they have no authority; we do not represent every security value as having the same fixed lifetime.

Blocking or deleting protective state mid-flow can prevent a request from completing or require you to start again. If a backing or membership checkout appears interrupted, check the account's transaction state before attempting another payment and contact support if the result is unclear. Deleting a cookie does not establish whether a payment succeeded or failed.

We do not publish live tokens, secret values or security-sensitive implementation details in this policy. You can ask for an explanation of a storage category without providing its value. If support needs diagnostic information, send the entry name and the page on which you saw it, with authentication credentials and personal information removed.

Our payment partner handles card details and may set its own necessary cookies on its checkout page. These can support the checkout session, protect payment processing, preserve the payment flow and detect misuse of that checkout. cohero never stores full card numbers, and our use of a payment service does not make those details part of our language or theme storage.

The payment partner controls its own checkout storage and explains applicable purposes, durations and controls through its checkout information and privacy materials. The exact cookies and lifetimes may vary with the payment method, browser and security requirements. We do not imply that all payment-partner entries share the same duration as your cohero sign-in session.

Browser rules that block cross-site storage, embedded content or redirects can interfere with a checkout even when ordinary browsing works. You can review the browser's site-specific permissions or use a supported, updated browser without disabling privacy protections for every website. If you cannot complete a payment accessibly or securely, contact hello@coheroapp.com rather than sending card details through chat or email.

A Backer's payment is a voluntary gift, not a purchase of goods or services or an investment. The Backing & Gift Policy and Membership & Billing Terms explain the relevant transaction rules; storage controls do not change those rules. In particular, clearing checkout data does not cancel a recurring membership or undo a released milestone payment.

If analytics are used, they are self-hosted and privacy-friendly. Their purpose is to understand service operation, such as whether a screen fails to load or a flow is difficult to complete, rather than to follow people between websites. We do not use third-party advertising analytics or share an advertising identifier to connect your activity to an external marketing profile.

Our strictly necessary storage approach does not reserve a general analytics exception. Analytics must not introduce non-essential cookies, persistent visitor identifiers or comparable device access merely because a measurement is useful. If a proposed measurement requires consent under applicable law, we must obtain that consent before using it or refrain from that measurement.

Service measurements and security records are not the same thing. A server can record a failed sign-in or an application error without placing an analytics cookie in the browser, and the resulting record may still contain personal data. The Privacy Policy governs the purposes, safeguards, retention and applicable rights for personal information in those records.

We do not promise that every form of measurement is anonymous merely because it is self-hosted. We limit information to what is appropriate for the stated purpose and do not use language or theme values to construct a behavioral advertising profile. Questions about a particular measurement or your account history can be sent to hello@coheroapp.com.

We do not use tracking pixels on the platform. A tracking pixel is typically a small resource whose loading signals an interaction to a tracking service; changing its format or making it invisible would not make advertising tracking acceptable under our approach. Ordinary images that display dreams or proof are content delivery, not permission to monitor users across unrelated websites.

We record sign-ins, sign-outs, failed sign-ins, account changes, dream changes, reports and errors on our own servers for security, fraud prevention and support. These records can include IP address and device or browser type. Server-side logging is distinct from saving a cookie, but it still involves information about how a device connects to the service.

Device and browser information helps investigate suspicious access, diagnose compatibility problems and understand why a request failed. We do not use it to create an advertising fingerprint for cross-site tracking. Please read the Privacy Policy for information about personal-data handling and how to request a copy of your account history.

Uploaded photos, videos and proof are stored privately and displayed through expiring or signed links. Such links authorise access to particular content for a limited context; they are not advertising cookies. Avoid sharing a private content link in a public support report, since possession of a valid link may expose the material while it remains usable.

Rules on storing information on a device commonly distinguish technologies strictly necessary to provide a service you request from optional technologies such as advertising trackers. Where that necessary-storage exemption applies, consent is not required before setting the essential values described here. Because we do not deploy optional advertising storage, we do not present a banner asking you to accept advertising cookies that we do not use.

This is a description of our present approach, not a claim that every jurisdiction has identical rules or that calling a cookie necessary makes it exempt. Authentication and security must actually support the requested function, and preference storage must be confined to implementing your choice. We assess requirements under applicable law and will adjust notices or controls if those requirements demand it.

An exemption from cookie consent does not remove transparency duties, security obligations or personal-data rights. Where a stored value or associated server record is personal information, the Privacy Policy explains the relevant processing separately. Accepting the Terms of Service does not operate as blanket consent to any future optional tracking.

If we introduce an optional technology requiring a choice, we will explain it before it is activated and obtain consent where required. We will not describe a refusal as acceptance or make withdrawal unnecessarily difficult. Material policy changes are notified in advance in the app or by email as described below.

Most browsers let you inspect or delete cookies and other site data, block some storage and set exceptions for individual sites. Menu wording varies by browser version, operating system and managed-device policy, so look for settings labelled privacy, site data, cookies or website permissions. Prefer a site-specific change when you want to troubleshoot cohero without signing out of unrelated services.

• On a computer, open the browser's settings and locate its privacy or site-data controls. Search for the site's address, inspect the stored entries if available and delete that site's cookies and local storage; some browsers list local storage under a broader website-data control.
• On a phone or tablet, use the browser's own settings or its entry in the device settings. Review website data and select the relevant site where a per-site option exists; clearing all browsing data may affect every signed-in website in that browser.
• In browsers with separate cookie and local-storage controls, clear both when your intention is to reset all saved preferences and authentication state. Clearing only cached images or browsing history may leave cookies and local storage intact.
• For private browsing, review the browser's explanation of what is removed when all private windows close. Private mode does not prevent the service from receiving requests, processing payments or keeping necessary server-side security records.
• For a work, school or supervised device, an administrator may restrict storage controls. Seek assistance from the device administrator without sharing your account password or session credentials.

You can generally block third-party cookies without preventing basic first-party preferences, although payment checkout behavior can vary. Blocking all cookies or all browser storage can prevent sign-in or protected actions, and it may stop your preferred language or theme from persisting. We cannot guarantee a fully functional authenticated experience where the browser refuses the state needed to secure it.

If your browser synchronises settings across devices, check whether a deletion or privacy exception is also synchronised. Otherwise, repeat the change in each browser profile and on each device you use. Browser extensions can also alter storage behavior, so include their relevant privacy effects when diagnosing a problem without broadly disabling security protections.

Use the in-app sign-out control when you finish on a shared device. Sign-out ends your authenticated use through the app, while clearing site data removes locally retained values from that browser profile. Do not assume signing out of one device signs out every other device, and do not rely only on closing a tab to protect an account.

After signing out on a public or shared computer, close remaining account pages and remove downloaded proof or documents if appropriate. Browser history, downloads, password managers and operating-system files are separate from cookies. Deleting site data cannot recall information already viewed, copied or downloaded by another person.

Account deletion is available from the profile and has a 30-day grace period. Signing in and choosing to keep your account during that period cancels deletion; simply clearing cookies does not submit or complete a deletion request. After the period, personal data is deleted or retained only in anonymised form and as required by law, as explained in the Privacy Policy.

Clearing storage does not cancel a Dreamer membership, change the status of a dream or remove messages sent to others. Use the profile's membership controls to cancel renewal and consult the Membership & Billing Terms for the effect of cancellation. If an accessibility or account-access issue prevents you from using these controls, contact hello@coheroapp.com for assistance.

Do Not Track is a browser signal expressing a preference not to be tracked, but its interpretation is not uniform across services or legal systems. Our no-advertising-tracker and no-cross-site-tracking approach applies whether or not this signal is enabled. We do not promise that enabling it suppresses essential authentication, payment security or records necessary to investigate account misuse.

Global Privacy Control is a browser or extension signal intended to communicate certain privacy preferences, including opt-outs where recognised by applicable law. We do not sell personal data or use third-party advertising tracking. Where a recognised signal creates an applicable obligation, we respect that obligation; we do not treat the absence of a signal as permission for practices prohibited by this policy.

Neither signal is a request to sign you out, erase an account, cancel a membership or delete transaction records. A signal also may not communicate which person is using a shared browser or provide the verification needed for an account-specific request. Contact hello@coheroapp.com if you want to exercise a personal-data right or understand how an applicable opt-out works.

Privacy controls can operate at different levels: a browser signal communicates a preference, a storage setting blocks or deletes local data, and an account request concerns server-held information. Combining these tools may be appropriate, but one does not necessarily perform the others' functions. We will explain the distinction when helping you resolve a request.

Depending on applicable law, you may have rights to access personal data, obtain a copy, correct inaccurate information, seek erasure or restriction, object to certain processing, or receive portable data. These rights are subject to their legal conditions and do not all apply to every technical value. A language preference stored only on your device may be more directly controlled through browser settings than through a server-record request.

You may request a copy of your account history and ask how security events relate to your account. We may need proportionate information to verify that a request comes from the person entitled to the records, particularly where disclosure could expose messages or account security. We do not ask you to send passwords, full payment-card numbers or active session tokens to establish identity.

A request to erase information may not require deletion of records that must be retained for legal duties, accounting, fraud prevention or the protection of other people. Where a limitation applies, we explain the relevant reason as permitted by law rather than presenting a browser cleanup as complete server-side erasure. Mandatory consumer and privacy rights remain unaffected by this policy.

If you believe a storage entry conflicts with our necessary-only approach, tell us the page, approximate time, browser type and entry name, but omit the stored value. We can investigate whether it belongs to our service, a checkout context, an extension or a different site. You may also raise a complaint with the competent data-protection authority where applicable.

We may update this Cookie Policy to reflect technical changes, legal requirements or improvements in the explanations we provide. Material changes are notified in advance through the app or by email. Continued use after a notified change takes effect constitutes acceptance to the extent permitted by law; it does not replace any separate consent that applicable law requires for optional storage.

An updated description does not authorise us to activate advertising tracking without the protections described above. If a new feature needs a new essential storage category, we will explain its purpose and retention approach, and assess whether it is genuinely necessary. If a proposed technology is not necessary, it cannot simply inherit the exemption used for authentication or your requested preferences.

For questions, storage identification, privacy-rights requests or help with a browser control, contact hello@coheroapp.com and identify this Cookie Policy. Include enough context to locate the issue, such as the affected screen and whether you were signed in, but remove private proof, card details and authentication values. Fenkil Technologies LTD operates cohero and is responsible for addressing questions about our own platform practices.

The Privacy Policy provides the broader explanation of personal-data handling, and the Accessibility Statement explains assistance for barriers that affect use of these controls. Policies are available in the supported interface languages; the English version prevails in a conflict, subject to mandatory law. Nothing in this policy limits rights that cannot lawfully be waived.