Cookie Policy
How Motiofy uses cookies and similar technologies.
Last updated: 2026-09-01
Overview
Motiofy Inc. ("Motiofy", "we", "us", or "our") uses cookies and similar technologies when you use Motiofy's websites, applications, and related services (the "Service"). This Cookie Policy explains what they are, why we use them, and how analytics choices will work. It should be read together with our Privacy Policy.
Cookies are small text files that a website can store in your browser. Similar technologies include local storage, SDK state, and other browser storage that can remember a setting or recognise a session.
Categories We Use
- Strictly necessary and functional technologies support sign-in, security, language and interface choices. They are not used for advertising or cross-site behavioural tracking.
- First-party attribution technologies remember campaign or external-referrer information so Motiofy can understand how a visit led to signup or purchase. They are not used for third-party advertising or cross-site behavioural profiles.
- Analytics technologies help us understand aggregate use of the Service and improve it. They are not needed to use Motiofy.
- Marketing technologies are not used. We do not use advertising, retargeting, or cross-site behavioural marketing cookies.
Technologies in the Current Service
| Technology | Purpose | Duration | Category |
|---|---|---|---|
better-auth.session_token or __Secure-better-auth.session_token | Maintains your authenticated session and protects access to your account. | Up to 7 days, subject to session renewal or sign-out. | Strictly necessary |
motiofy_device | Stores a random signed device identifier used for signup-Credit abuse prevention and security. It does not contain your name or email address. | Up to 1 year. | Strictly necessary security |
marketing_first_touch, marketing_last_touch, utm_source | Stores first-party campaign, referrer, and landing-page attribution when a tagged campaign or external referrer is present. | Up to 30 days. | First-party attribution; subject to consent where required |
sidebar_state | Remembers an account holder's sidebar preference after they change it. | 7 days. | Functional preference |
PARAGLIDE_LOCALE | Remembers the language you select for the Service. | Until you change the language choice or your browser clears it. | Functional preference |
Google Identity Services g_state | Helps Google One Tap remember sign-out state and avoid repeated sign-in prompts. It is controlled by Google Identity Services when One Tap is enabled. | Set and expired according to Google Identity Services and browser settings. | Functional authentication |
| Motiofy preference LocalStorage | Remembers choices such as hidden Prompt suggestions, welcome-offer suppression, the last viewed Changelog, pricing-offer timing, sidebar sections, and verification-email cooldown. | Until the relevant feature clears it or you clear site data. | Functional preference |
| Motiofy workflow SessionStorage | Temporarily preserves generation drafts, Paywall recovery, generation notifications, and pending analytics events within the current browser session. | Current browser tab/session, with shorter application-level expiry where applicable. | Functional workflow recovery |
Google Analytics 4 _ga and _ga_<container-id> | Distinguishes users and preserves session state for basic website analytics. | Up to 2 years under Google Analytics' documented defaults. | Analytics — only after consent controls are live and you opt in where consent is required |
| Plausible standard self-hosted script | Collects basic aggregate traffic analytics. The configured standard Plausible script does not set analytics cookies or persistent browser identifiers. | Not applicable. | Analytics — only after consent controls are live and you opt in where consent is required |
| Microsoft Clarity storage | Supports interaction analytics when a Clarity project is configured. The provider-defined keys and lifetimes must be disclosed before the integration is enabled. | Provider-defined. | Analytics — only after consent controls are live and you opt in where consent is required |
| Crisp or Tawk storage | Supports customer-service chat when the relevant integration is configured. Provider-defined cookies or browser storage may be used to maintain the conversation. | Provider-defined. | Customer support — enable only with an appropriate disclosure and legal basis |
The table reflects storage paths supported by the current application code. A conditional provider is not active unless both the production third-party-service gate and that provider's configuration are enabled. We will update this table before enabling a new technology or materially changing its purpose, provider, or retention period.
Analytics Consent and Cookie Settings
Strictly necessary technologies may operate without an optional analytics choice. The current application build does not yet provide a cookie-preference interface or script interception.
Where prior consent is required, Google Analytics 4, Plausible, Microsoft Clarity, first-party attribution cookies, and other non-essential technologies must remain disabled until an appropriate accept/reject control is deployed. Once controls are live, visitors will be able to accept, reject, or later change optional choices. Rejecting optional analytics will not stop you from using Motiofy.
Managing Cookies in Your Browser
You can also block or delete cookies through your browser settings. Doing so may prevent sign-in, session continuity, language choices, or other parts of the Service from working correctly. Browser controls do not necessarily stop all non-cookie technologies, which is why the Motiofy Cookie Settings control will be the primary way to manage optional analytics once it is available.
Changes to This Policy
We may update this Cookie Policy when our technologies or legal obligations change. We will post the updated version here and revise the "Last updated" date. For questions, contact us at support@motiofy.ai.