Privacy Policy

Last updated: 24 October 2026

This Privacy Policy explains how Wedge ("we", "us") collects, uses, and protects information when you use Homla ("Homla") at app.homla.ai and homla.ai, and its connectors, including the Google Analytics connector. Homla is the home for your team's work with AI: shared skills, shared memory, each person's own access to company tools, and agents that ask before they act, inside Claude, ChatGPT, Cursor and Codex. It works as a multi-tenant remote MCP (Model Context Protocol) server that connects third-party tools to your AI assistant.

Information we collect

Account & sign-in information. When you sign in (including with Google), we receive your name and email address to create and secure your account.
Connected-service credentials. When you connect a service, we receive and store the OAuth tokens needed to call that service on your behalf.
Google Analytics data. When you connect the Google Analytics connector, we access your Google Analytics reporting data on a read-only basis via the scope https://www.googleapis.com/auth/analytics.readonly, for example account and property lists, dimensions, metrics, and the results of reports you or your AI assistant request.
Analytics and campaign information. How you reach and use our sites, as described in Analytics and cookies below.

How we use information

To authenticate you and operate your account.
To fulfill the specific requests you or your AI assistant make in a session, such as running a Google Analytics report and returning the results to you.
To secure the platform, prevent abuse, and provide support.
To understand how people find and use Homla, and to credit referral partners for the sign-ups they send us.

We do not use Google user data for advertising, and we do not sell your data or share it with third parties except as needed to provide the service (e.g. our hosting, database and analytics providers) or as required by law.

Google API Services User Data Policy: Limited Use

Homla's use and transfer of information received from Google APIs to any other app will adhere to the Google API Services User Data Policy, including the Limited Use requirements. Specifically, Google user data obtained through the Google Analytics connector is used only to provide or improve the user-facing features that are prominent in Homla's interface; it is not used for advertising, is not sold, and is not transferred to others except as necessary to provide and improve those features, to comply with applicable law, or as part of a merger or acquisition. Humans do not read this data unless we have your consent for specific data, it is necessary for security purposes (such as investigating abuse) or to comply with applicable law, or the data is aggregated and anonymized. Google user data is never sent to the analytics tools listed below.

Analytics and cookies

We use the following tools and cookies on homla.ai and app.homla.ai. Tools marked "after consent" only load once you accept analytics in the cookie banner, and you can change your choice at any time.

Microsoft Clarity (after consent, on homla.ai): session replay and heatmaps that show how visitors use the marketing site, so we can improve it.
PostHog (after consent): product and web analytics, such as which pages are visited and whether a sign-up completes. We use PostHog's EU cloud, so this data is stored in the EU.
Cloudflare Web Analytics: cookieless page view counts. It sets no cookie and does not identify you.
homla_attr: a first-party cookie on .homla.ai that records how you first and last reached us (campaign fields such as utm_source, the referring site, a partner's ref code and the landing page). It holds no name, email or other identifier, lasts 60 days, and is used to credit referral partners for the sign-ups they send us.
homla_consent: a first-party cookie that stores your analytics choice (accepted or declined) so we respect it on both sites. It lasts 180 days.
Sign-in storage: when you sign in to the app, your browser keeps your session so you stay signed in. This is needed for the service to work.

To change your analytics choice, use the cookie settings link on homla.ai, or clear the cookies for homla.ai in your browser.

Storage & retention

Credentials and OAuth tokens are stored encrypted in our database. We retain your account and connection data for as long as your account is active. Google Analytics report results are returned to you in-session and are not retained by Homla beyond what is needed to deliver the response and operate the service.

Your choices & revoking access

You can disconnect the Google Analytics connector at any time from within the Homla app, which removes the stored credentials. You can also revoke Homla's access directly from your Google account permissions page. To request deletion of your account data, contact us using the details below.

Data security

We protect your information with encryption of stored credentials, access controls, transport encryption (HTTPS), and role-based access within each tenant. No method of transmission or storage is completely secure, but we work to protect your data using industry-standard measures.

Children

Homla is a business tool and is not directed to children under 16, and we do not knowingly collect their data.

Changes to this policy

We may update this Privacy Policy from time to time. Material changes will be reflected by updating the "Last updated" date above.

Contact us

Questions about this policy or your data? Contact us at support@homla.ai.