This describes what information 313.events actually collects, how it's used, and which outside services are involved. It only describes what the site actually does — not a generic template.
If you use the Submit an Event form, you provide event details (title, description, dates, venue, pricing, links) and, for the person submitting it: an organizer/venue name and a contact email address. If you submit an event feed instead, you provide the feed URL and a contact email for the feed owner.
This information is used to review and, if approved, publish the event listing, and to reach you if we have a question about the submission. Your contact email and organizer name are not shown on the public site — the public event pages only show the event's own details, not who submitted it.
If you email us directly, we keep that correspondence to respond to you and to keep a record of the request.
Like most websites, our hosting provider (Vercel) automatically logs standard technical information for every request — things like IP address, browser type, the page requested, and timestamps. This is standard server/CDN logging used for operating and securing the site, not something 313.events separately collects or analyzes.
313.events uses two analytics/measurement tools on its public pages, to understand traffic and how the site is used:
| Service | Purpose |
|---|---|
| Google Analytics 4 | Standard web analytics — page views, traffic sources, general usage patterns. |
| Metricool | Marketing measurement and attribution, including tracking engagement that originates from our social media activity. |
These are both active on the public side of 313.events (the event calendar, map, event pages, submission form, and similar). They are not active on our internal admin/moderation tool, since that's operational traffic, not public visitor traffic.
We don't operate any separate, custom analytics or tracking system of our own beyond these two third-party tools.
313.events' own code does not set or read cookies directly. Google Analytics and Metricool each set their own cookies in your browser once loaded, as part of how those services work — this is standard for analytics tools and is covered by each provider's own privacy policy (Google's and Metricool's, respectively).
313.events does not use browser local storage or session storage to store any data about you.
313.events runs on Vercel (hosting and serverless functions) and Supabase (database and image storage for submitted event flyers). These providers necessarily process the data that flows through the site in order for it to function — this is standard for any web application, not a separate "sharing" of your data for their own purposes.
Depending on what you're doing on the site, these additional third parties may be involved:
None of these services receive your submission-form contact email or organizer name — that information stays within 313.events' own database.
313.events links out to third-party sites constantly, by design — organizer pages, venues, and ticket sellers. Once you click through, that site's own privacy practices apply, not ours. The site also links to 313.events' own Instagram profile; visiting it is subject to Instagram's own privacy policy.
Event-submission information is kept as part of the normal event record for as long as the listing is relevant to the site's operation (including past events, for historical/editorial reference). If you'd like your submitter contact information removed, see "Your privacy choices" below.
313.events uses standard safeguards appropriate to a small web application — access to the admin/moderation tool is restricted by a secret credential, and the database's public-facing views are deliberately limited to exclude non-public fields like submitter contact information. No method of transmission or storage is 100% secure, and we can't guarantee absolute security.
We don't sell your information. We share information only with the service providers described above, to the extent necessary for them to provide their service (hosting, database, email delivery, analytics), or if required by law (for example, in response to a valid legal request).
313.events is not directed at children, and we don't knowingly collect personal information from children under 13.
313.events is operated from the United States, and information is processed and stored in the United States (via our hosting and database providers). If you're accessing the site from outside the U.S. (including from Windsor, Ontario, which is part of our coverage area), your information will be processed in the U.S.
To ask what information we have about you, request a correction, or ask us to delete your submitter contact information from our records, email us at the address below. We'll respond to reasonable requests.
We may update this Privacy Policy as the product changes. The "Last updated" date at the top of this page reflects the most recent revision.