Privacy and cookies

Last updated November 3, 2026. This page explains what Hangar collects, why, and what you can do about it. Hangar is a global service operated from Brazil, so it follows the LGPD (Brazil), the GDPR and UK GDPR, and the privacy laws of US states such as California.

Who is responsible

Hangar is operated from Brazil and is the controller of the data described here. There is no separate data protection officer yet: privacy questions and requests go to [email protected], which reaches the people who run the service.

What we collect

Account data. Name, email, organization, authentication data and, for paid plans, billing details. We need it to run your account and to charge for it.

Service data. Logs, usage metering and security events produced while you use the platform. We need it to operate, secure and bill the service. Automated checks look through what you build and your logs for known signs of abuse, and at your email's domain and sign-in account when you sign up or deploy. When we suspend an organization for abuse, we keep a hash of its owner's email and sign-in accounts, its card's fingerprint and what it deployed, to refuse its return, until the suspension is lifted.

Website and product usage. Pages viewed, referrer, campaign parameters, device and browser information, approximate location and the steps taken in sign-up and in the dashboard. Measuring the public site in detail and our marketing tools depend on your consent, as described below. The cookie-free page count and the campaign cookie do not.

We do not read the content of your projects, environment variables, databases or volumes for analytics.

Signing in with Google

You can create a Hangar account or sign in with your Google account. When you do, Google asks you to let Hangar see your basic profile, and we request only the openid, email and profile scopes. We do not ask for access to Gmail, Drive, Calendar, Contacts or any other Google service.

What we receive. Your Google account identifier, your name, your email address, whether Google has verified that email, and your profile picture. Google also gives us the tokens of that sign-in.

How we use it. Only to create your Hangar account, sign you in, show your name and picture in the dashboard, and send you the emails the service needs, such as security notices, invitations and billing. We do not use Google user data for advertising, we do not sell it, and we do not use it to develop, improve or train AI or machine learning models.

How we store it. The profile data is kept with your account in our database, encrypted in transit and accessible only to the people who run the service. The sign-in tokens are kept only to link your Google account to your Hangar account; we do not use them to call Google on your behalf.

Who it is shared with. Nobody, except the infrastructure and email providers listed below, which process it on our behalf to run the service, and an authority when the law requires it. It is never sent to Google Ads, Meta or PostHog.

Removing it. Deleting your Hangar account deletes the Google profile data and tokens linked to it. You can also write to [email protected] to have it deleted, and you can remove Hangar's access at any time in your Google account settings.

Hangar's use and transfer of information received from Google APIs adheres to the Google API Services User Data Policy, including the Limited Use requirements.

Why, and on what legal basis

  • Running your account, deploying your applications and billing you: performance of a contract (GDPR art. 6(1)(b), LGPD art. 7, V).
  • Securing the platform and preventing abuse: legitimate interest (GDPR art. 6(1)(f), LGPD art. 7, IX).
  • Measuring the public website and the campaigns that bring people to it: your consent (GDPR art. 6(1)(a), LGPD art. 7, I), asked by the banner.
  • The campaign cookie, which tells us which ads and channels work: our legitimate interest (GDPR art. 6(1)(f), LGPD art. 7, IX).
  • The cookie-free page count, which tells us how many people visit and where they come from: our legitimate interest (GDPR art. 6(1)(f), LGPD art. 7, IX). You can object to it by writing to us.
  • Understanding how signed-in users use the dashboard, to fix what is confusing or broken: legitimate interest (GDPR art. 6(1)(f), LGPD art. 7, IX). You can object to it by writing to us.
  • Offering the support chat in the dashboard and answering you in it: legitimate interest (GDPR art. 6(1)(f), LGPD art. 7, IX), and performance of a contract once you write to us.
  • Meeting legal and tax obligations: compliance with the law (GDPR art. 6(1)(c), LGPD art. 7, II).

Cookies and similar storage

Strictly necessary. Signing in needs a session cookie, set when you sign in. It does not require consent. We also keep your cookie choice in your browser's local storage.

Analytics. With your consent, we use PostHog. It stores an identifier in a cookie or in local storage and receives the pages you view, your referrer, campaign parameters and device information, and it also records clicks and sessions. If you decline, the site works the same.

Cookie-free page count. If you decline or have not chosen, PostHog stores no identifier in your browser and receives only the pages you view, your referrer, campaign parameters and device information. If you accepted and later withdraw, it keeps only a note of that choice. To count visits, it combines your IP address and browser details into a hash with a value that changes every day, so it can't recognize you from one day to the next or link these visits to an account.

Campaign cookie. Whatever you choose in the banner, we keep the campaign or site that brought you here (the UTM parameters, the referrer and, for an ad, the click identifier) in a cookie of our own for 90 days, and attach it to your account if you sign up. It holds no identifier of you and no record of the pages you visit. You can delete it in your browser.

Marketing measurement. With your consent, if you sign up with an email and password, PostHog also receives your email address. PostHog passes sign-ups, with a hash of that email, to Meta through Meta's Conversions API, so Meta can measure our ads; nothing is loaded from Meta in your browser. If you sign up with Google, GitHub or single sign-on, no email is sent for this. If you never chose, the banner also asks inside the dashboard. Until you accept, none of this is sent, and if you decline, now or later, it stops.

Support chat. Once you are signed in, the dashboard loads a chat from Crisp so you can reach the team. It is never loaded on the public site or the sign-in pages. Crisp stores an identifier in a cookie or in local storage and receives your name, email, the organization you are working in and its plan, so we know who we are talking to, along with the messages you send and the page you write from. When you sign out, the chat forgets the conversation on that browser.

Advertising. We advertise on Google Ads. If you arrive from one of our ads, our campaign cookie keeps Google's click identifier. If you then sign up, PostHog sends Google that identifier, the event and when it happened, so Google can measure our ads and bid on them. We do not send your name, email or any other contact detail. We load no advertising pixels on the site.

Who receives your data

We use providers that process data on our behalf: infrastructure hosting, email delivery, payment processing, the support chat (Crisp), product analytics (PostHog) and ad measurement (Google Ads and Meta). They may only use the data to provide their service to us. We do not sell personal data. Apart from the marketing and ad measurement described under cookies, which needs your consent, we do not share it for cross-context advertising.

Some of these providers run outside Brazil, including in the United States, so data can be transferred internationally. Where the law requires it, we rely on safeguards such as the EU Standard Contractual Clauses and the UK addendum (GDPR chapter V) and the mechanisms of LGPD art. 33, together with our providers' own commitments.

We may also share data when a court or authority requires it.

How long we keep it

Account data is kept while your account exists and afterwards only for as long as the law requires, for example for tax records, or to defend ourselves in a dispute. Analytics and service data are kept only as long as they are useful for the purposes above, then deleted or anonymised.

Security

We use encryption in transit, access controls and isolation between customers. No system is perfectly secure; if an incident puts your data at risk, we will tell you and the ANPD as the law requires.

Your choice on cookies

You can change your mind at any time. . You can also clear this site's local storage and cookies in your browser.

Your rights

Wherever you live, you can ask us to confirm that we process your data, give you access to it, correct it, delete it, export it, tell you who it was shared with, and revoke consent. You can also object to processing based on legitimate interest or ask us to restrict it. Write to [email protected] and we will answer within 15 days, and in any case within the time your local law sets. We will not treat you differently for using these rights.

EU, UK and Brazil. These rights come from GDPR arts. 15 to 22 and LGPD art. 18. If you are not satisfied with our answer, you can complain to your local data protection authority, or to the ANPD in Brazil.

California and other US states. You can know, access, correct and delete your personal information and opt out of its sale or sharing. We do not sell it. The only sharing for advertising is the marketing and ad measurement described under cookies, which starts only after you accept cookies. Declining cookies, now or later in the cookie preferences, opts you out of it.

Children

Hangar is a service for developers and businesses and is not directed at children under 18, or under 16 where local law sets that age. We do not knowingly collect their data.

Changes

When this page changes in a way that matters, we update the date at the top and, if consent is involved, ask again.