Cookie Policy
Effective date: 20 July 2026 · Public website version
Cookies and similar technologies used by Hello Moti
Operator: Avatud OÜ (registry code 12443197) · Viru väljak 2, 10111 Tallinn, Estonia · team@hellomoti.app
Current position. Hello Moti uses strictly necessary technologies for sign-in, security, account sessions, and payments. At the effective date, we do not use advertising cookies or behavioural advertising, and this policy assumes no optional analytics tool is enabled.
This Cookie Policy explains how Avatud OÜ ("Avatud", "we", "us", or "our") uses cookies and similar technologies on hellomoti.app and related web applications. It should be read with our Privacy Policy.
1. What are cookies and similar technologies?
Cookies are small text files placed on a browser or device. Similar technologies include local storage, software-development-kit identifiers, pixels, and server-side tokens. They can remember a session, keep an account signed in, protect a form, prevent fraud, or complete a payment.
2. Technologies we currently use
| Category / provider | Purpose | Typical duration | Consent status |
|---|---|---|---|
| Hello Moti authentication and session | Keep the adult Account Holder signed in, connect requests to the correct account, maintain language or necessary preferences, and prevent session misuse. | Session or a limited persistent period, depending on the "remember me" setting and security configuration. | Strictly necessary. |
| Security and anti-abuse | Protect forms and APIs, detect suspicious traffic, prevent cross-site request forgery, rate-limit requests, and maintain service integrity. | Session to approximately 12 months, depending on the security control. | Strictly necessary. |
| Google sign-in | Complete adult authentication when the Account Holder chooses "Continue with Google". Google may set cookies needed for account selection, security, and authentication. | Set by Google; duration depends on the Google account and browser settings. | Necessary when Google sign-in is chosen. |
| Stripe payment flow | Open and secure checkout, process payment, prevent fraud, remember the payment session, and support refunds or disputes. | Set by Stripe; session and persistent identifiers may be used under Stripe's policy. | Strictly necessary for the requested purchase. |
| Load balancing, hosting, and reliability | Route traffic, maintain uptime, prevent repeated failures, and support secure delivery of the website. | Usually session or short-lived. | Strictly necessary. |
Exact cookie names and durations may vary as browsers, security settings, Google, Stripe, and hosting infrastructure change. We keep the deployed cookie inventory under review and update this Policy when a change materially affects users.
3. What we do not currently use
- Advertising cookies or advertising pixels.
- Cross-site or cross-context behavioural tracking of children.
- Cookies used to sell or share personal data for targeted advertising.
- Optional analytics cookies at the effective date of this Policy.
If we introduce optional analytics, product-experiment, or marketing technologies, we will identify them, explain their purpose and duration, and request consent where required before they are activated.
4. Legal basis and consent
Strictly necessary cookies are used because they are required to provide the website or feature requested by the Account Holder, protect the Service, and complete payment. They cannot generally be disabled through a consent banner without breaking the requested function.
Non-essential cookies, if introduced, will be based on consent where applicable. Refusing or withdrawing optional consent will not prevent access to core paid features, although an optional feature may not work.
5. Children and cookies
The account and payment flow are controlled by an adult. We do not use cookies to profile a child for advertising. Necessary device and session identifiers may still be processed while a child uses a parent-authorised session because they are required to deliver and secure the Service.
6. How to control cookies
You can delete or block cookies through browser settings. Blocking necessary cookies may prevent Google sign-in, account access, secure voice sessions, or payment. Browser controls do not necessarily remove server-side records required for security, accounting, or legal compliance.
- Use the browser's privacy or site-data settings to view and delete cookies for hellomoti.app.
- Use Google Account settings to manage Google sign-in and Google cookies.
- Use the payment page and browser controls to manage Stripe cookies, understanding that blocking them may stop checkout.
- Where a Hello Moti consent control is shown, use it to accept, reject, or change optional categories.
7. Third-party information
Major third-party information: Google Privacy Policy · Google cookies information · Stripe Privacy Policy
Third-party cookie names and retention may be controlled by those providers. We configure integrations to use the least intrusive settings reasonably available for the requested function.
8. Changes to this Policy
We may update this Policy when our cookie inventory, providers, or legal requirements change. The effective date appears at the beginning. Material changes to optional tracking will be reflected in the consent interface before the relevant technology is enabled where required by law.
9. Contact
Avatud OÜ · Registry code: 12443197 Viru väljak 2, 10111 Tallinn, Estonia Email: team@hellomoti.app · Website: https://hellomoti.app