DemoRadar is designed around guest-first discovery. Many features work before sign-in, and some private data stays local unless you choose to use an account-backed experience.
1. Who We Are
Unlimitive Media operates DemoRadar. If you have privacy questions or requests, you can contact us at contact@unlimitive.com.
2. Information You Provide Directly
Depending on how you use DemoRadar, you may provide:
- your email address and password when you create an account or sign in;
- profile details such as display name, city, topics, theme, locale, and notification preferences;
- event submissions, including title, date, time, location, source link, organizer/source name, and contact email;
- organizer or admin content such as updates, checklist actions, review notes, and edited event details;
- abuse reports, moderation notes, organizer block actions, and related safety details you submit in-app;
- messages you send us directly, such as support or privacy requests.
3. Information Stored Locally on Your Device
DemoRadar stores some information locally so the app can stay useful before sign-in and remain responsive. Local storage may include:
- onboarding completion state;
- appearance mode, theme selection, language preference, and haptics preference;
- selected city and topic filters;
- saved events, reminders, and private attendance state;
- followed organizers;
- locally applied organizer blocks used to hide blocked public content instantly on your device;
- private progress such as XP and achievements;
- draft or locally stored submissions, imported review items, and cached public content.
4. Information Synced When You Sign In
If you sign in, DemoRadar may sync certain private data to its backend so it can persist across sessions and devices. Based on the current app behavior, this may include:
- your profile record and role assignment;
- saved event links;
- private reminder rows;
- private attendance state;
- followed organizer links;
- submissions you create;
- terms-acceptance metadata such as accepted version, acceptance time, and acceptance source;
- content reports and organizer block records linked to your account or device when used;
- organizer or admin content entered through restricted tools when your role allows access.
DemoRadar currently uses Supabase for authentication and backend data services. Organizer and admin rights are assigned server-side rather than unlocked by client-only actions.
5. Optional Location and Notifications
DemoRadar may request access to your device location to calculate nearby results and distance-based event sorting. Based on the current implementation, this location lookup is optional and used in-app for those features rather than stored as a persistent account field.
DemoRadar may also request notification permission so it can schedule local event reminders such as 24-hour or 2-hour alerts. Reminder scheduling is tied to your saved actions and device notification settings.
6. Analytics and Crash Reporting
DemoRadar logs product analytics events and crash diagnostics to help improve reliability and understand feature usage. This includes Firebase Analytics event data and Firebase Crashlytics error reports in supported release environments. These signals may include app version, device-level technical context, feature events, and non-content diagnostic information needed to understand failures or usage patterns.
7. Public Event and Organizer Source Data
DemoRadar displays public event and organizer information sourced from reviewed submissions, internal curation, and third-party imports such as DemokraTEAM. This public-source information may include titles, descriptions, times, locations, summaries, source links, organizer names, public contact links, images, and other event context that is already intended for public discovery.
8. External Sharing, Calendar, and Link Handoffs
If you use DemoRadar to share an event, open a route, add an event to your calendar, send email, or open an external source link, related event details may be passed to your device operating system or the selected third-party app or website. Those services operate under their own privacy rules.
9. How We Share Information
We may share information with service providers and infrastructure partners that help operate DemoRadar, including:
- Supabase for account, authentication, and backend data storage;
- Firebase Analytics and Crashlytics for product analytics and diagnostics;
- device and platform services such as notifications, calendar integration, email, maps, and sharing;
- external sites and public event sources when you choose to open them.
We may also disclose information when reasonably necessary to comply with law, protect rights and safety, investigate abuse, or maintain service integrity.
10. Retention
Local data remains on your device until you remove it, clear app storage, or uninstall the app. Synced backend data may be retained while your account or related records remain active, and for a reasonable period afterward where needed for security, moderation, abuse prevention, legal obligations, or dispute handling.
11. Your Choices and Rights
You can choose whether to sign in, grant location access, or allow notifications. Depending on applicable law, you may also have rights to request access, correction, deletion, or restriction of certain personal data we hold.
You can contact contact@unlimitive.com for privacy-related requests. We may need to verify your identity before completing sensitive requests.
12. Account Deletion Requests
DemoRadar does not yet provide a dedicated self-serve account deletion page. For now, account or synced data deletion requests should be sent to contact@unlimitive.com using the email address associated with your DemoRadar account when possible.
13. Changes to This Policy
We may update this Privacy Policy as DemoRadar evolves. When we do, we will revise the date at the top of this page and may take additional notice steps when appropriate.