Privacy Policy
Last updated: October 4, 2026
This shared policy explains how Local Robot® handles information for eventsinprovidence.com, the Events in Providence app, and Providence Passport. The app-specific sections distinguish their different features. Providence Passport is an independent Local Robot® app, not affiliated with the Providence Downtown Improvement District (DID); permission to use DID content does not make DID the app operator. Events in Providence is independent of the City of Providence and government agencies.
Website information and submissions
When you submit an event or yard sale, contact us, or subscribe to a newsletter, we receive the information you provide. This can include a name, email address, optional phone number, address, listing dates, descriptions, links, and images. We use it to review and publish submissions, respond to inquiries, and deliver newsletters you request. You can unsubscribe using the email’s unsubscribe link.
Details intended for a public listing, including a yard sale address and submitted images, may be published. Do not include private information you do not want published. Contact details supplied only for editorial communication are used for that purpose.
Website cookies, analytics, and technical information
Website visits and API requests send technical information such as an IP address, browser or device information, requested pages, search terms, and referring pages to the server and its providers. We use this information to operate the services, understand usage, diagnose problems, and limit abuse. Temporary abuse counters can use keyed values derived from an IP address.
The website uses functional cookies and Google Analytics to understand website traffic and performance. Analytics may use cookies or similar identifiers. Google Search Console provides search-performance information. Your browser can block or delete cookies, although some website functions may be affected. The native apps’ features and provider data are described separately below; a web page opened inside an app follows website practices.
Sharing, service providers, and security
We do not sell, rent, or trade your personal information. Hosting, email delivery, analytics, map, weather, and other service providers receive information needed for their services. Information may also be disclosed with your direction, for publication you request, or when necessary to comply with law or protect rights and service security. External websites, ticket sellers, messaging apps, and other providers have their own policies.
We use reasonable safeguards, but no internet transmission or storage system can be guaranteed completely secure. Avoid sending unnecessary sensitive information in forms or reports.
Website retention, children, and your choices
Published listings remain while relevant to the directory or archive. Submissions, private support messages, and editorial reports remain as needed for review, communication, and site operations. Newsletter information remains until you unsubscribe or request removal, subject to necessary records of that choice. Hosting logs, backups, and provider records may follow different retention processes. App-specific retention is described below.
The services are for a general audience and are not directed to children under 13. We do not knowingly collect personal information from children under 13. A parent or guardian who believes a child has supplied personal information should contact Local Robot® so it can be reviewed and removed as appropriate.
Depending on where you live, you may request access, correction, deletion, or withdrawal of consent where applicable. Use the contact form, identify the service and information involved, and do not send passwords or sign-in codes. We may need to verify that you control the relevant account or information. We publish policy updates here with a revised date.
Events in Providence app: Browsing and search
The app requests listings, images, and filters from eventsinprovidence.com. The website receives the search words and filters needed to respond; geographic searches also send the selected point, radius, or map area. As with other internet requests, the server and its providers receive technical information such as an IP address.
The API uses temporary counters derived from IP addresses to limit abusive requests. The app does not create an Events in Providence account or a personal search history for advertising. Hosting logs and third-party services may have their own retention practices.
Events in Providence app: Location, maps, and directions
Mapbox provides maps, address searches, and routes. It receives the location or address needed for the feature you choose. Device location access is requested for nearby discovery or navigation from your current position. You can browse manually and preview a route from an address without that permission.
During a trip you start, guidance can continue using location and audio while the screen is locked or the app is in the background. Ending the trip stops the navigation session. You can change location permission in device settings.
Mapbox SDKs may process precise or approximate location, identifiers, interactions, usage, and performance or diagnostic data to provide and improve their services. The SDK privacy manifests describe these data as not linked to your identity and not used for advertising tracking. Mapbox telemetry controls are available through the map’s information or attribution control.
Events in Providence app: Private favorites and iCloud
The app stores your favorites, a copy of their public listing details, and preferences on the device. When iCloud is available, favorites sync through a private CloudKit database associated with your Apple Account. That list is not published on the website or shared as a public community list.
Remove a favorite by tapping its heart again. The app retains a record of that change, which may include the listing snapshot, to prevent a later sync from saving it again. Removing a favorite from the list therefore does not immediately erase all of its sync records.
Deleting the app removes its local data; iCloud data is managed separately through Apple’s iCloud storage controls. If you change accounts, the app keeps each account’s favorites separate. For help managing or deleting information, use the contact link on this page.
Events in Providence app: Apple Weather
The app asks Apple for a forecast for the place you are viewing, such as Providence or an event’s location. It temporarily caches a response to avoid repeated requests. Forecasts display Apple Weather attribution and a link to its legal sources.
Events in Providence app: Clambot and Clam stickers
Clambot uses the same listing searches and filters as the calendar. Its temporary guide history stays on the device; it does not use a camera or a conversational AI service.
The Clam sticker extension uses images bundled with the app. It makes no network requests, creates no accounts, and does not read your conversation content. You choose which sticker to send through Messages. Apple handles message delivery according to its services and settings.
Events in Providence app: Reminders and Calendar
The app asks for notification permission when you choose a reminder. The event’s title, time, and other details are used to schedule a local notification on that device. You can change permission in Settings. Event changes can update a reminder only after the app receives them.
When adding an event to Calendar, you review its details in Apple’s editor. The copy you save belongs to the selected calendar under that account’s settings and does not automatically update from Events in Providence.
Events in Providence app: Forms, links, and contact
Event and yard sale forms open in an in-app browser. They can ask for a name, email address, address, and listing details. The event form requests a poster; the yard sale form allows an optional phone number. Information intended for publication, including a yard sale address, can appear publicly. The website’s newsletter asks for an email address if you choose to subscribe.
Listing issue reports are saved privately for the website team’s review. The app support form saves your optional name, email address, and message in a private website queue for administrators to review. It does not automatically send email or subscribe you to a mailing list. Avoid including unnecessary sensitive information.
Web pages, the browser, ticketing services, and other external destinations may use cookies, analytics, or other technologies under their own policies. The website policy describes practices for forms, newsletters, and web visits.
Events in Providence app: Your choices and requests
You can use the app without its own account, choose a location manually, deny or change location and notification permissions, remove favorites, and manage iCloud data with Apple. The app has no advertisements or paid subscription.
To request access, correction, or deletion of information you submitted, or ask about choices available where you live, contact Local Robot and include “Events in Providence — privacy request.” Identify the information or feature involved without sending passwords. Requests involving an Apple Account or information managed directly by another provider may also require that provider’s privacy controls.
Events in Providence app: Retention and updates
Favorites and their sync records remain until managed or removed through the app or iCloud as explained above. Reports, inquiries, and submissions are retained as needed for review, communication, and website operations. Backups and providers may follow different retention processes. Removing an item from the screen does not promise immediate deletion of every copy.
We will publish changes to this policy here with a revised date. Use the contact form for questions about how information is handled.
Providence Passport: The service
Providence Passport uses Events in Providence servers to provide a place directory, saved walks, favorites, visits, current event listings, and optional public leaderboards. It is an independent Local Robot® app with content supplied by Downtown Providence, Events in Providence, DowntownParks.app, and WBNA. This notice describes the Passport service. Other websites and map services have their own policies.
Providence Passport: Guest and email accounts
A guest profile receives a random identifier and alias. If you sign in by email, your address is used to deliver a one-time code. The Passport account database stores a keyed hash of that address, not a readable address. Email delivery providers necessarily receive the address and message. Session credentials are stored securely on your device; the server stores their hashes.
Providence Passport: What your passport saves
The service saves your profile preferences, chosen public name and name history, favorites, walks, and stamps. A stamp contains a place ID, visit day and timestamp, and whether you checked in by location or QR. It does not contain the precise coordinates you supplied. These records remain with an active profile until you change or delete them, or delete the profile.
Providence Passport: Location, walking directions, and the camera
Location is optional for browsing. With permission, it helps find nearby places and verifies an explicit location check-in. The server evaluates check-in coordinates in memory and does not save them in Passport tables. Nearby transit searches send the selected coordinates to the service. User-started walking guidance uses your location and may continue while the screen is locked when the platform and permissions allow it. Stop guidance or change system permissions to end that access. Map rendering and route requests use Mapbox and may send location, route endpoints, and technical information to that provider. The camera scans venue QR codes; the scanned link is sent for verification, not a camera photograph. Legacy DID QR links are verified by the Downtown Providence server.
Providence Passport: Mapbox telemetry
Mapbox SDKs can send location and usage telemetry and process device identifiers, interactions, diagnostics, and performance information under Mapbox’s privacy policy. These provider records are separate from Passport’s stamp database. The map’s information or attribution control includes Mapbox’s telemetry choice so you can opt out of location telemetry. Necessary map and route service requests may continue when you use those features.
Providence Passport: Passport stickers
Passport stickers are fixed artwork bundled with the app. The sticker tools do not read what you type, inspect conversations, access your Passport account or location, or send network requests. Sharing or inserting a sticker sends only the artwork you select through the messaging app or system sharing destination you choose; that app has its own privacy practices.
Providence Passport: Public names and leaderboards
Leaderboard participation is off by default. When you opt in, other people can see your selected name or alias, visit count and rank at a place. Your email and precise location are not published. You can opt out at any time. Display-name reports and moderator decisions are private; moderators can reset names or restrict leaderboard participation.
Providence Passport: Retention and deletion
Deleting your profile immediately removes its sessions, stamps, favorites, walks, name history, and leaderboard participation, and clears its email hash and public name. Existing private moderation reports and audit evidence have a 180-day retention limit; the deleted-profile tombstone is also removed within that limit. Expired codes, session records, and abuse counters are cleaned daily after a one-day grace period. Old name revisions on active profiles are retained for at most 180 days. Support requests are separate private records and remain as needed to review and respond. Hosting backups, operational logs, and delivery or map providers may follow separate retention processes.
Providence Passport: Technical requests and support
Servers and providers receive ordinary connection information such as an IP address. Passport uses temporary hashed-address counters to limit abuse; those counters do not store a readable IP address. Support forms save the email address and message you provide in a private administrator queue and do not subscribe you to marketing. Use the support or account-deletion links below for a request about your data.
Providence Passport: weather, transit, and deletion requests
Passport requests Providence weather through Events in Providence’s weather integration, including OpenWeather data; this is separate from Apple Weather in the Events in Providence app. RIPTA stops, bus positions, predictions, delays, and alerts are obtained through the Events in Providence transit service from public transit sources. Viewing these feeds does not create a transit operator account. Nearby-stop searches may send the location you select to Events in Providence.
Previously viewed places and personal progress are cached on your device. Pending favorite and walking-itinerary changes can be sent when connectivity returns. Device copies and secure credentials are managed through the app and operating-system controls. Removing the app does not itself delete a Passport server profile; system backups or secure storage may remain separately. Use Delete profile in Passport or the account-deletion request page; a web request is reviewed privately and requires identity verification before a profile is removed.
Place stories, tours, banners, and permitted event details can include public images, audio, video links, and 3D assets from the credited sources. Loading an image or model, playing native audio, or opening an external resource sends ordinary connection information to its hosting provider. Passport does not send your account credentials with those media requests and does not collect a playback history for native place stories or tours. Interactive pages and external videos open as external destinations with their own practices.
Tour progress is stored on this device with the tour revision and stop position; it is not synchronized to a Passport account or submitted to the server as tour tracking. Previously loaded content and downloaded model assets may be cached locally. New content requests refresh source status when online; cached content can become outdated. Device storage and system backups follow the app and operating-system controls described above.
YouTube video cards can load a preview thumbnail from Google’s image servers when displayed. The thumbnail request shares ordinary connection information with that provider. Showing the preview does not play the video; video playback opens only when you choose its action and follows the video provider’s privacy practices.
Providence Passport: music at Murmur
When you tap Recognize this song at Murmur HiFi Lounge, Passport briefly uses your microphone in the foreground, with your permission. ShazamKit creates an audio signature and checks it with Apple’s Shazam service to identify the music. Passport does not save raw microphone recordings or send them to the Events in Providence or Local Robot websites. Recognition stops after a match, cancellation, interruption, backgrounding, or a short timeout.
Before listening and before saving a recognized play, Passport sends a recent location, its accuracy and capture time to Events in Providence, which forwards them to Local Robot to check that you are at Murmur. These venue checks are processed transiently and are not stored in your music history. They do not upload a travel route or enable continuous microphone listening.
Recognized song titles, artists, scan times and music-provider metadata, such as artwork and Apple Music links, are saved in Virtual Murmur’s shared music history on localrobot.com. These records contain no Passport identity. Anyone can see the latest song while a scan is less than three minutes old and browse recognized-play counts; unscanned music is not tracked.
Favorite songs are private preferences associated with your Passport account. You can remove favorites, and deleting your Passport profile removes its private favorites. Deleting favorites or a Passport profile does not delete the anonymous shared song history. Apple’s Shazam service and external music destinations follow their own privacy practices.
