Privacy — Atlanta Marketing Events

The short version

We hold what you tell us and what happened at our events: your name, your email address, your RSVPs, and whether you turned up.
Other members can see your email address on your profile page. That is deliberate. This is a room of people meant to be able to reach each other.
Nobody but the two of us who run the club can see your phone number, and no member can see your event history.
We do not sell anything about you, we run no advertising, and there is no analytics or tracking software on this site.

What we hold, and where it came from

Things you typed. Your name and email address. At signup, the kind of company you work for (agency, brand, or solo/fractional) and your broad role (owner, director, or strategist). On your profile, anything you choose to fill in: job title, organization, city and state, a short bio, a LinkedIn URL, a website, a photo, and a phone number. You can edit all of these yourself.

Things an organizer recorded.Many people are in our records because they came to an event, asked to be kept in the loop, or were added by one of us. For each event we track whether you were invited, what you answered (yes, no, or maybe), whether you raised your hand for it, whether you actually attended, your answers to any questions the host put on the RSVP form, and the time you ticked an event’s confirmation box if it had one. Organizers also keep internal notes and tags on a record, and a note of when they first contacted you about an event.

Things the system recorded. If you have a login: a password (stored only as a bcrypt hash, never as text), when you last signed in, and a count of failed attempts so the account can lock itself. A log of the emails we sent you, with the subject line, the address, and whether it was delivered or bounced. A log of changes made to event rosters. Your IP address, used as a counter in a short time window so that the sign-in, signup, and RSVP forms can rate-limit abuse.

Who can see it

This is the part worth reading twice, because it is more open than people expect.

Any signed-in member can browse the directory and see, for every person in our records: name, photo, organization, job title, bio, city and state, LinkedIn, website, who referred them, and their company-type and role tags. The directory covers everyone we have a record of, not only people who created an account.
On your profile page, a signed-in member also sees your primary email address. It is not on the directory list itself, so the whole roster is not readable in one request, but any member who opens your page has your address.
Your phone number is never shown to another member, hosts included. Only a super-admin account can see it.
No member can see your event history. Not your attendance, not a count, not a total of any kind. You can see your own. Event pages today show how many people are coming, not who they are; where we do show a guest list, it is only for an event you can already see.
Organizers see more. Internal notes, internal tags, who owns a relationship, and the contact log are ours and are never shown on a member surface.
The public sees almost none of this. The directory and every profile page need a signed-in account. An event page a stranger can open shows the host and a headcount, never a guest list and never an email address.

What we do with it

We run the club with it: inviting you to things, taking RSVPs, sending you a calendar invite, telling you your event moved, letting you sign in, letting members find each other, and knowing how many chairs to put out. We send transactional email (verification, invitations, password resets, event confirmations) and occasional email about upcoming events. We do not sell or rent your information, and we do not hand it to advertisers.

The companies that touch it

Short list, and it is the whole list of services this software talks to:

Vercel hosts the site, and Vercel Blob stores profile photos and event photos. Those image files are served from public URLs: the addresses are long and unguessable, but they are not password-protected, so anyone given the link can open the image.
Neon hosts the database everything above is stored in.
Resend sends our email. Resend also tells us when a message bounced or was marked as spam, which we record so we stop mailing a dead address.
Google Calendar delivers calendar invites. If you RSVP yes to an event that has one, your email address goes onto that calendar entry so Google can invite you. For events we run as a single shared calendar entry, the other guests can see your address in their own calendar, the same way any ordinary calendar invitation works. A host connects their own Google account to make this possible; we never read their mail, only their calendar.
Google reCAPTCHA can be switched on to keep bots off the public signup and RSVP forms. When it is on, Google receives the usual signals it uses to decide whether you are a person.
A few events take registration on another company’s site instead of ours. The button says so when that is the case, and once you follow it you are on their site under their policy, not ours.

There is no analytics package, no advertising tag, no session recorder, and no third-party font or icon service on this site. The typefaces and icons are served from our own domain.

Cookies

One cookie, event-mgmt-session. It says who you are after you sign in, it cannot be read by scripts, and it lasts seven days. Your light-or-dark theme preference is kept in your own browser’s local storage and never reaches us. There are no advertising or tracking cookies to consent to, which is why this site has no cookie banner.

Photographs

Photographs are taken at our events and used on this site and to promote future ones. If you would rather not appear, tell whoever is holding the camera, or email us and we will take the picture down. Some events ask for something more specific — a session being filmed, for instance — and those carry their own tick box on the RSVP form with the exact wording of what you are agreeing to.

Getting your record changed or removed

You can edit every field on your own profile yourself, at any time.

If you want out of the community, we revoke your login and stop mailing you. By default we keep the underlying record — your name and the events you came to — because it is the club’s own history of who was in the room. Say so if you want the record deleted outright and we will delete it.

Two honest footnotes about deletion. Our internal log of roster changes stores names as plain text, so your name can survive there after the record itself is gone. And our log of sent email stores the address each message went to, so an address can survive there too. We can clear both by hand on request.

Reaching a human

Email hello@atlantamarketingevents.com for anything on this page: a correction, a copy of what we hold, a photo you want down, or deletion.

Still to be decided

Left open rather than guessed at. Each of these needs an answer from Chris or Mickey before this draft becomes the policy:

TODO(chris) Who is the legal entity behind Atlanta Marketing Events — Classic City Consulting, GreenMellen Media, both, or a separate entity? The policy needs to name whoever is accountable for the data, with a postal address.
TODO(chris) How long do we keep things? Nothing in the software expires or deletes on a schedule today, so this document cannot yet state a retention period for records, email logs, or the roster-change log.
TODO(chris) Is Google reCAPTCHA actually switched on in production? It runs only when its keys are configured, and this draft describes it conditionally because that could not be determined from the code.
TODO(chris) What is the standing policy on event photography? The paragraph above is a reasonable guess at what the club already does in practice, not a decision anyone has recorded.
TODO(chris) Do we owe anyone a formal rights section (GDPR, CCPA, or similar)? That depends on who the members are and where they live, which is a question for a lawyer rather than for this draft.