Skip to content

AdLemur privacy policy

Effective October 6, 2026

Alamas Labs Inc., United States, operates AdLemur and is responsible for the information described here. This policy covers www.adlemur.com and our applications at app.adlemur.com and ads.fort.dev. Contact us at privacy@adlemur.com. Independently hosted installations have their own operators and privacy practices.

Information we collect

  • Account and support information you provide, including your name, email, company, workspace details and messages.
  • When you sign in with Google, your Google account identifier, name, email address and profile picture, plus authorization scopes and tokens. We use these to create and secure your AdLemur account. Google handles your password. Signing in does not authorize access to an advertising account.
  • For email sign-in, a password hash and records needed for verification and password resets. We do not store your password in plain text.
  • When you connect Meta through Facebook Login, your Meta user ID and name, authorization scopes and access tokens. The reporting connection requests ads_read and public_profile. Meta handles your Facebook password; AdLemur does not collect it.
  • Authorized ad account identifiers, names, currencies, timezones, campaigns, ad sets, ads, creative references and reporting metrics such as spend, impressions, clicks and conversions. Other advertising connections supply the account and reporting information you authorize.
  • Public advertising evidence collected for competitor research, and content, settings and reports you save in your workspace.
  • Website visits, browser and device information, network request metadata and interaction recordings. Our website uses Plausible and analytics.jamalavedra.com for analytics and session recording. Cookies and browser storage also support authentication and preferences.

AdLemur software can send an installation heartbeat to PostHog in the United States. It contains a random installation identifier, software version, aggregate usage counts and setup-status flags. It does not include Meta user or ad account IDs, access tokens, ad content or reporting values. This heartbeat is disabled at app.adlemur.com.

How we use information

We use connected-account data to provide the reports requested by the authorizing client, organize multiple ad accounts and compare their results. Reports are available to authorized operators in that workspace. Reporting-only connections cannot change campaigns. Any campaign-management connection requires separate authorization.

We also use information to operate and secure the service, respond to support requests, research public advertising, understand website use, and send updates you request. Where applicable, processing is based on providing the requested service, consent, legitimate interests such as service security, or a legal obligation. You can withdraw consent by disconnecting a provider or contacting us.

Service providers and sharing

Our application is hosted by Hetzner Online GmbH in Germany. Cloudflare, Inc. provides our website hosting, proxy and access services through its international network. These providers process service data to run and protect the service. Resend stores website subscription email addresses and sends account verification and password-reset emails. Autumn receives workspace identifiers and account email addresses to manage access and usage-credit balances. Website analytics use Plausible and analytics.jamalavedra.com; Google Fonts supplies website fonts.

Apify handles public-ad research when enabled. Requests include public advertiser identifiers and search criteria. We do not send connected-account access tokens or private reporting data to Apify.

When enabled, AI features send relevant conversations, workspace information and advertising tool results to OpenRouter and the model provider handling the request. Tool results can include authorized account and reporting data. These AI features are currently disabled in our operated application.

We do not sell connected-account data. We share it with the authorizing client and service providers needed to deliver that client's service. We review the legality of requests from public authorities, challenge them where warranted and legally permitted, and disclose only the data lawfully required. We document the assessment and response.

The operator is in the United States and our providers operate in other countries. Information may therefore be processed internationally. You can contact us for information about the providers and safeguards applicable to your data.

Retention and security

We retain information while it is necessary to provide the authorized service or meet legal obligations. We delete Meta Platform Data when it is no longer needed for the permitted service, the client relationship ends, or Meta, the client or the affected user requests deletion, unless retention is required by law. We explain any legally required retention when responding to a request.

Disconnecting a profile removes its stored access tokens and stops further reporting requests. It does not erase previously stored reports; use the data deletion instructions to request their removal. We protect provider tokens with encryption and restrict application access. Restricted backups may contain earlier records. We must apply deletion requests before using restored data.

Your choices and rights

You may request access, correction, a copy or deletion of your information at privacy@adlemur.com. Depending on the law that applies, you may also object to processing, request restrictions, withdraw consent, or complain to a supervisory authority. We verify that you are entitled to the requested information before acting. Do not send passwords or access tokens. Contact us to opt out of marketing updates.

Changes and contact

We publish policy changes here with an updated effective date. For privacy questions, deletion requests or a security concern, contact privacy@adlemur.com and identify AdLemur in your message.