Privacy, plainly.

What we keep

Google gives again your account identifier, name, email address, and optional profile image so you can sign in. We also keep the preferred name, short bio, and any optional social or website links you choose to add. Identity, profile, links, and session records live in a dedicated authentication database.

Circle records contain an opaque user ID, a copy of your preferred name, your commitments, the public audience description written by an organiser, your private answer about why a particular circle fits you, and any circle you organise, join, leave, or report. Public cards never show your Google email, Google profile, bio, application answer, or social links.

Cloudflare may suggest an approximate city from request metadata. We use that suggestion only to answer your request; we do not save your IP address or connect the suggestion to your account. A place you choose for an in-person public circle is stored with approximate coordinates so nearby search can work. Online circles do not store a meeting location.

Why we keep it

We use this information to operate the service, prevent one person from claiming the same place twice, coordinate circles, respond to safety concerns, and—with your permission—understand which campaigns lead people to useful product actions. We do not sell personal information or use your profile or circle information to target advertising.

Who receives it

Cloudflare runs the application and databases. Google provides authentication. Bird sends transactional circle emails from hi@again.social; it receives the recipient address and the content required to deliver that message, but it does not receive circle membership tables or safety reports. When you submit a place search, our server sends that text to OpenStreetMap’s Nominatim service and caches only a hash of the search with the returned public place data; it is not linked to your account. Your browser’s IP address is not sent to Nominatim by again.

With your permission, Amplitude receives explicit journey and product events—such as viewing a landing page, beginning sign-in, completing a profile, or creating, applying to, joining, leaving, and confirming a circle—and records session replays so we can see where the product is confusing or broken. Replays capture page layout, navigation, clicks, and scrolling. Text entered into fields is masked, as are member cards, bios, applications, notices, and private coordination links. A replay may include public circle information already visible on screen, including its displayed neighbourhood. Before sign-in these use a random browser identifier; after sign-in they are joined to an opaque account ID. Campaign, ad-set, ad, placement, and landing-path labels may accompany those events. We do not intentionally send Amplitude your email, profile text, coordination link, application answer, report details, or location-search text, and we do not use automatic event or page autocapture.

Also with your permission, the Meta Pixel and Meta Conversions API receive a small set of advertising-measurement events: page views, completed registrations, circle applications, circle commitments, and circle creation. Browser and server copies share an event ID so Meta can avoid counting the same action twice. Meta may receive its browser identifiers, ad click identifier, your IP address and browser information, the page path, and—after sign-in—a one-way-hashed version of your Google email to match the conversion. We never send Meta a bio, preferred name, application answer, circle title, venue, precise location, coordination link, social link, or safety report.

When campaign details are present in a link, your browser keeps the first campaign that introduced Again and the latest tagged visit for up to 90 days after you allow measurement. The product database keeps the same limited campaign record under the random browser identifier and, after sign-in, the opaque account ID.

Private coordination, group-chat, and online meeting links become visible only to authenticated members after they are accepted into a circle. They are not shown on public circle pages or to people in the waiting room. An online organiser may choose not to provide a separate group-chat link.

Your preferred name, circle role, bio, and completed-circle count are visible on a contextual member card to signed-in people considering an open circle you are in, to the organiser reviewing your application, and to accepted members of your circle. Your circle-specific answer is visible only to that circle’s organiser. There is no public people directory or profile search.

Optional Instagram, X, LinkedIn, TikTok, YouTube, and website links are visible only to people who are currently accepted into the same circle. They are not shown to applicants, organisers reviewing someone who is still waiting, signed-out visitors, or public circle-page visitors. Profile fields and links are not sent to Amplitude or Bird.

Your choices

You can decline measurement without losing access to Again. You can review the choice below at any time; declining clears Again’s campaign record and random analytics identifier from this browser and stops new Amplitude and Meta measurement events from it. You can also edit your preferred name, bio, and optional links from your member dashboard, remove every optional link, and leave a circle at any time. During this alpha, request access to or deletion of your account data at support@again.social.