Privacy, in plain words.
This page covers the echelar.ai website. It collects very little, and everything it does collect is listed here. The Echelar product has its own data-processing terms, agreed with each customer.
Last updated 12 September 2026.
Privacy policy
Who is responsible
Echelar is operated by Rimovate FZE, Ajman Free Zone, Building C1, Premises BC 1306457, Ajman, United Arab Emirates. For anything about your data, write to mohamed@echelar.ai. The founder reads every message.
What this website collects
- Visits and interactions. With your consent, we use PostHog to understand which pages and features are useful and where people choose to book a call. Analytics and the country lookup stay off until you accept. A first-party cookie holds a random browser identifier so we can recognise repeat visits; it does not tell us who you are. We do not attach names, email addresses, or person profiles to these events. We record page views, booking-button views and clicks, content and FAQ interactions, demonstration controls, scroll milestones, and time a page stays visible. Events include their time, page, browser and device information, browser language, referring site, and campaign tags. Our server looks up approximate country from the connection IP using a local database and sends only the country result as event properties; we do not add the raw IP or precise location to analytics events. We also collect page-performance measurements and browser error diagnostics. URL queries and fragments are removed from captured URLs, and common personal fields are filtered. We do not record sessions, capture form input, or automatically collect every click.
- Bookings. When you book a call, you do so on cal.com. The name, email address, and notes you enter there are processed by cal.com under its own privacy policy and shared with us so we can hold the meeting. We keep them to prepare for and follow up on that conversation.
- Email. If you write to us, we keep the correspondence for as long as it takes to answer and to keep the context of the relationship.
- Server logs. Our hosting provider records standard request logs (IP address, requested page, time, browser) for security and reliability. They are kept for a short period and are not combined with anything else.
Cookies and local storage
The essential echelar_consent cookie remembers your privacy choice for 180 days. Your light or dark theme choice is stored locally under echelar-theme. Neither preference is sent to PostHog. If you accept analytics, PostHog also stores a first-party browser identifier in a cookie for up to 180 days from its latest update and uses session storage to distinguish browsing sessions and tabs. Your browser may remove these sooner.
Your analytics choice
Accepting and rejecting analytics are equally available, wherever you visit from. You can continue browsing and book a call with analytics off. Use Privacy choices in the footer to change your preference. Withdrawing consent stops further analytics collection and removes the analytics identifier from this browser. It does not undo events already sent. Contact us below about data previously collected.
Third parties
We rely on three: PostHog for analytics, cal.com for bookings, and our hosting provider for serving the site. Our PostHog project is hosted in the United States. The consent banner is open-source software served by our own site; it does not send your choice to an external consent service. We do not sell visitor data.
Your rights
Under the GDPR and comparable laws you may ask what we hold about you, have it corrected or deleted, or object to how it is used. Email mohamed@echelar.ai and we will answer within thirty days. You may also complain to your local data-protection authority.
The product is different
When a company uses Echelar, repository contents, Session activity, and configuration are processed on that company's behalf under a separate agreement. The security page explains where code runs and what agents can never do; the contract governs the rest.
Changes
On 12 September 2026 we introduced an opt-in analytics choice for all visitors and a browser identifier for consented repeat visits. Before this change, analytics used a daily cookieless identifier. If this page changes in a way that matters, the date above changes with it.