This Privacy Notice for Get In (also presented as “we,” “us,” or “our”) explains how and why information may be accessed, collected, stored, used, or shared when you use this website, submit an event or correction, receive the newsletter, or otherwise interact with the project.
The short version
Get In is a public events calendar. It does not require an account or request access to private social-media profiles. We use public event information, information you choose to submit, and limited technical data needed to run and protect the service. We do not sell personal information or use it for behavioral advertising.
1. Scope and project purpose
Get In collects publicly available event information from public calendars, venue websites, approved community submissions, and supported public-content APIs. It organizes those listings into a searchable calendar and links visitors to the original source.
2. Information we collect
Information you voluntarily provide
If you submit an event, correction, source suggestion, privacy request, or other inquiry, we may receive the details you enter in the form. This may include an email address, event information, source links, and explanatory notes. Contact details and moderation notes are kept private and are not published with an event.
If you ask to receive the newsletter, we collect the email address only after you actively accept the newsletter consent. We also store the edition choice: all events, or local events within a fixed 20-mile radius of the town or ZIP code you provide. A double-opt-in confirmation email is required before the address becomes eligible for newsletter delivery.
Website access and abuse-prevention information
The public site is delivered through Cloudflare. Cloudflare may process technical request information, including network addresses, browser information, and security signals, to deliver and protect the service under its own terms and privacy practices. The site does not place advertising or behavioral-tracking cookies.
Anonymous visit measurement records session-arrival and action signals without sending a browser identifier or network address to the analytics dataset. A boolean marker in your browser indicates whether it has visited before; that signal does not contain a visitor ID and does not identify you across websites. Clearing browser storage resets the marker. Event likes are currently disabled.
A link printed on a card or shared in a post may carry a short campaign label, such as a coffee-shop card or a weekly social post. An untagged arrival from an approved search engine may carry a fixed label such as Google or Bing. These labels describe how someone arrived, never who they are. The original search-referrer URL and query stay in the browser and are not sent to or stored by the application. Temporary session flags prevent repeated measurement; they contain no visitor identifier and do not carry attribution between sessions.
For abuse prevention, a visitor’s network address may be used briefly to create a rotating one-way rate-limit hash. The raw address is not stored in the application database. A Cloudflare Turnstile check may also be used on public submission forms to distinguish legitimate requests from automated abuse.
No social-media login or private account access
The project does not offer Facebook Login or ask visitors to authorize access to a social-media account. It does not request or process a visitor’s private profile information, friends, messages, check-ins, likes, birthday, or current city.
3. Public event-source information
For event listings, the project may process public business or organization metadata and public posts that contain event details, such as a title, date, time, venue, description, image, admission information, permalink, and source name. This is limited to content made publicly available by the source. The project does not attempt to bypass access controls or collect private Page, group, profile, or message content.
Public event details may be stored in datasets and limited historical change records to detect duplicates, corrections, cancellations, and outdated listings. Every listing links to its source so visitors can confirm current details.
4. How we use information
We may use information to:
- Identify, organize, and display public event announcements.
- Prioritize and filter listings by location and date.
- Detect duplicates, changes, cancellations, and expired listings.
- Generate the public calendar and optional newsletter.
- Display aggregate event-like totals and remember whether the same browser liked an event.
- Measure aggregate visits and estimate new and returning browsers.
- Review community submissions before publication.
- Investigate corrections, removal requests, source suggestions, security issues, and abuse.
- Comply with applicable law and platform requirements.
5. Service providers and sharing
We use service providers that help operate the project:
- Cloudflare provides website delivery, security, bot checks, the application API, and cloud data storage.
- GitHub provides source control, automated processing, and encrypted runtime-secret storage.
- Brevo sends the double-opt-in confirmation and future newsletters, and processes the address and edition attributes as the email service provider. Brevo’s unsubscribe mechanism is required in every campaign send.
- Cloudflare provides the protected submission review queue and private storage. Historical Google tracker snapshots are archived and are not active review inputs.
- Source platforms and websites provide the public event pages and supported public-content APIs used to locate event announcements.
We do not sell personal information and do not use it for targeted or behavioral advertising. Public event details and source links are displayed on the website. Information may be disclosed when legally required, when needed to respond to a valid rights request, or when reasonably necessary to protect the service and its users.
6. How long we keep information
Upcoming event records remain available while useful to visitors. Limited historical event and change information may be retained to improve duplicate detection, corrections, and source-quality checks. Daily anonymous traffic records are retained for up to 13 months. Rotating abuse-prevention records are retained for up to 14 days. A hashed like record remains while the like is active so the public total and per-browser toggle remain accurate. Private submission contact information and moderation notes are retained only as long as reasonably needed for review, follow-up, security, and legal obligations. Newsletter records are kept while a subscription is pending or active, and an unsubscribe record may be retained to prevent re-addition and document the withdrawal. Provider-side records are also subject to Brevo’s terms and retention controls.
7. How we protect information
We use reasonable organizational and technical safeguards, including restricted moderation records, prepared database writes, double opt-in, unsubscribe handling, and encrypted runtime secrets. No electronic transmission or storage system is completely secure, so absolute security cannot be guaranteed. API credentials are not intentionally published in the repository or website.
8. Children’s privacy
The service is a general-audience events calendar and is not directed to children under 13. We do not knowingly collect personal information from children. If you believe a child has submitted personal information, use the request methods below so it can be reviewed and removed.
9. Your privacy rights
Depending on where you live, you may have the right to request access to personal information we maintain about you, correct inaccurate information, obtain a copy, request deletion, or withdraw consent. You may also have the right to appeal a denied request or use an authorized agent. These rights may be limited by applicable law.
We may ask for enough information to verify that a request concerns you or that an authorized agent may act for you. Verification information is used only to assess and respond to the request. We do not discriminate against anyone for exercising a privacy right.
10. Global Privacy Control and Do Not Track
The site does not use behavioral-advertising trackers. When a browser sends Global Privacy Control or Do Not Track, the site does not send anonymous visit measurement. This includes short campaign links, which still take you where they point but record nothing. Public like totals may still load without a browser identifier. If you choose to like an event, a random browser identifier is created only to save and protect that like. You can reset that identifier by clearing this site’s stored data in your browser.
11. Data deletion, review, and correction requests
To request deletion of information you submitted, removal or correction of an event listing, removal of public content obtained through a supported platform API, access to information associated with you, or removal from the newsletter distribution list, use the newsletter unsubscribe form for an immediate unsubscribe request, or either option below for a broader privacy request:
Include the affected event, email address, or source URL and enough detail to identify the information. Requests will be reviewed and handled as reasonably required by applicable law and platform policy.
12. Updates and contact
This notice may be updated when the project adds or changes a source, service provider, or feature. The revised date at the top will be updated when material changes are published.
For questions or comments about this notice, email ag2022qa@gmail.com or use the correction and privacy request form.
This notice was adapted for this service from content created with Termly’s Privacy Policy Generator.