Cookie Policy

The weefund_token cookie identifies an authenticated session. The current sign-in token expires after seven days unless you sign out or the session becomes invalid earlier. It is used to access account information and enforce permissions, not as an advertising identifier. Blocking it prevents authenticated features from working.

Local storage may keep saved-project summaries, an unfinished campaign form, and language/currency preferences. The campaign form is an unsent working copy, not a published campaign. Saving a project on a device does not subscribe you to email or make a pledge.

These items may remain until the feature clears them or you clear site data. Shared-device users should sign out and remove local information they do not want the next user to see. Clearing local saved projects is separate from unfollowing projects stored in your account.

Payment checkout, hosted campaign images, and embedded video services may make requests to their own providers and use their own cookies or similar mechanisms under their policies. You can choose not to load a video or open an external link.

The current WEEFUND application does not install a cross-context advertising-cookie system or provide a banner claiming that such cookies are already controlled by it. Hosting providers may keep operational and security logs. If optional tracking is introduced, the notice and any required consent controls must reflect the actual change.

Use your browser’s privacy settings to inspect, block, or delete cookies and site storage. This may sign you out or remove local preferences and unfinished forms. It does not automatically delete server-side account, transaction, support, follow, or subscription records.

Manage project email consent through Following or an unsubscribe link, not browser-cookie settings. Contact Support for an account-data or privacy request. We do not claim that a browser Do Not Track signal performs a server-side account deletion or email unsubscribe.