re:Invent Hive is a browser extension and a mobile web page that show which coworkers at your company favorited or reserved AWS re:Invent sessions. SharpBits, LLC ("SharpBits", "we") operates it and is the party responsible for the data described here. Questions and requests go to privacy@sharpbits.io.
What the extension runs on

The extension runs only on these pages:

https://registration.awsevents.com/flow/awsevents/reinvent2026/*, the re:Invent registration site for the 2026 event.
https://aws.amazon.com/events/reinvent/calendar/*, the My Calendar page.


It also sends requests to the re:Invent Hive service at https://reinvent-hive.com/*. It does not run on, read, or collect data from any other website or tab, and it does not collect browsing history.
What we collect and where it comes from
Sign-in

Your email address. The extension takes it from your registration profile, and you cannot change it in the sign-in form. Amazon Cognito emails a one-time code to that address through Amazon SES, and you enter the code in the extension to sign in. We use the address only for sign-in codes and to match your Hive account to your registration account. We send no marketing email.
Sign-in tokens issued by Cognito (see "What the extension keeps in your browser").


From the registration site (while you are signed in to it)

Your profile: email, first name, last name, job title, and company name.
Your favorite sessions and your reserved sessions, as session IDs.
The extension reads the site's own rfjwt cookie to authenticate its requests to catalog.awsevents.com. The cookie is not sent to re:Invent Hive.


From My Calendar (while you are signed in to it)

The extension repeats the calendar page's own sign-in steps by calling auth.aws.amazon.com and prod-api.awseventservices.com with your existing AWS session, and it sends a randomly generated device ID (Browser- followed by a UUID) with that sign-in. The resulting tokens are used for that run and are not stored by the extension.
It then reads your profile (email, first name, last name, job title), your favorite and reserved sessions, and your personal calendar blocks.
Personal calendar blocks are stored only when you press "Share with my hive" on a block. For each shared block we store its title, description, date, and start and end times (local and UTC). The block's location is not stored.


Page content

On the catalog and calendar pages the extension reads session identifiers, titles, and start times from the page in your browser so that it can place its icons on the right cards. That page content is not sent to re:Invent Hive. Only the data listed in this section is sent.
What you enter

Notes on sessions (1 to 2,000 characters each).
Teams you create or join, and team names (1 to 50 characters). Teams and memberships carry over between event years.
Your audience settings for Favorites, Reservations, and Notes.
A company name, if you are a company manager and edit it. If your company has no name yet, the first company name read from a registration profile is stored.


Kept by the service

The company your email domain belongs to. Domains of public email providers cannot sign up.
Whether you are a company manager (set by the operator).
The time of your last sync, the event year in which you last verified your email, and the account creation time.


How often data is sent

When a registration or calendar page loads, and every 5 minutes while that tab is visible, the extension reads the site and sends your favorites, reservations, and shared calendar blocks to re:Invent Hive. It sends an update only when the data differs from the last update the service accepted from that tab.
Who can see your data

Only signed-in users at your own company can see data about you. Your company is determined by your email domain. We do not make your data public.

For Favorites, Reservations, and Notes you choose one audience each. The choices are exactly:

Nobody: no coworker sees that type of data. This is the default for all three.
Entire company: every signed-in user at your company sees it.
My teams: coworkers who share at least one team with you see it. Anyone at your company can join any team.


Shared personal calendar blocks follow your Favorites audience. A note is shown with its text to coworkers allowed by your Notes audience.

Some information is visible to signed-in users at your company regardless of your audience settings:

Your first name, last name, and job title, when you are listed as a member of a team, or when a coworker can see at least one type of your data.
Team names, team member counts, and the member list of any team at your company.
Your company name.
The time of your last sync, which is part of the coworker data the service returns.


Your email address is not shown to coworkers. You always see all of your own data in My Hive.

The operator, SharpBits, can access stored data through its AWS administrative access, and uses admin functions to load the session catalog, block email domains, remove teams, designate company managers, and process company opt-outs. SharpBits personnel do not read individual users' data except with your consent, to investigate abuse or security problems, to comply with law, or as aggregated or anonymized data.
Where data is stored
On our servers

Your account data, favorites, reservations, shared calendar blocks, notes, teams, audience settings, and company records are stored in Amazon DynamoDB in the AWS US East (N. Virginia, us-east-1) region. The table has point-in-time recovery enabled.
Your email address and sign-in state are stored in an Amazon Cognito user pool in us-east-1.
The service runs on AWS Lambda behind Amazon CloudFront, AWS WAF, and Amazon API Gateway. Requests use HTTPS.


Logs

The API writes logs to Amazon CloudWatch Logs and keeps them for 30 days. For each request the log records the HTTP method, the URL including its query string (for example the text of a team search), the host, the remote address and port reported to the API, a request ID, the response status code, and the response time. Error entries add the error details. Request bodies and request headers are not logged. Because the remote address is logged, a log entry can contain an IP address.

AWS WAF processes the IP address of each request to enforce rate limits (a limit per IP address over 5 minutes) and keeps a small sample of recent requests, including source IP addresses, that we can view in the AWS console.
What the extension keeps in your browser

storage.local: your Cognito access token, ID token, and refresh token with their expiry time, and a copy of the public session catalog that is refreshed after 6 hours. The tokens are removed when you sign out or when the server rejects them.
storage.session: while a sign-in code is pending, your email address, the Cognito session handle, and the send time. The browser clears it when it exits, and the extension deletes it after sign-in, after sign-out, and when the 10-minute code validity ends.
In memory only: a copy of your coworker view for 60 seconds.


The mobile web page keeps its access token in page memory. It receives the refresh token in a cookie named hive_rt (HttpOnly, Secure, SameSite=Strict, path /api/auth, 365 days) that page scripts cannot read. Signing out clears the cookie and revokes the token.

The extension contains no analytics, advertising, or telemetry code.
How long we keep data and how to delete it

Delete account. In the extension popup, open Settings and choose Delete account. This removes you from every team you belong to (a team left with no members is deleted with its name), deletes your favorites, reservations, shared calendar blocks, and notes for every event year, deletes your profile, audience settings, and company link, and then deletes your Cognito user. The deletion runs immediately. The company record (name and email domains) is not deleted.
Company opt-out. If a company asks us to remove its people, the operator blocks the company's email domains from signing up and runs the same deletion for every user at the company, then deletes the company's remaining records, including teams. Send a request from an address at the company's domain to privacy@sharpbits.io.
Everything else. We set no expiry on stored data. It is kept until you delete your account or your company opts out. Each new event year, you must verify your email again; your data is kept in between.
Backups and logs. Deleted data can remain in DynamoDB point-in-time recovery for up to 35 days (the AWS default recovery period, which we do not change). API logs are deleted after 30 days.
Uninstalling. Removing the extension deletes what it stored in your browser. It does not delete data on our servers, so use Delete account first.


To ask for a copy of your data or for deletion when you cannot use the extension, email privacy@sharpbits.io from your registered address.
Who processes your data

We use Amazon Web Services as our processor for hosting, authentication (Amazon Cognito), and email delivery (Amazon SES). The extension also calls AWS-operated services for the event (registration.awsevents.com, catalog.awsevents.com, auth.aws.amazon.com, prod-api.awseventservices.com) using your own sessions, to read your own data; it sends them no Hive data other than the device ID described above.

We do not sell your data, we do not share it with third parties other than AWS as our processor, and we do not use it for advertising. We may disclose data if the law requires it.