Legal

LuzRD Privacy Policy

Last updated: September 6, 2026 · Effective date: September 6, 2026

LuzRD (“we”) operates https://luzrd.com and the official Android app on Google Play. This policy explains what personal data we process, why, who we share it with, and your rights. By using LuzRD you accept this policy. If you disagree, do not use the service.

1. Who is responsible

LuzRD is the controller of the personal data described here. The service is offered primarily in the Dominican Republic and is governed, among other rules, by Law 172-13 on Personal Data Protection.

  • Trade name: LuzRD
  • Website: https://luzrd.com
  • Android app: https://play.google.com/store/apps/details?id=com.nathan.luzrd
  • Privacy and support email: eipelnatacedeno@gmail.com

We are not EdeEste, EdeSur, EdeNorte, or any official electric utility. Maps and reports are community information, not an official utility notice.

2. Scope

This policy covers:

  • The website luzrd.com and its routes (map, reports, statistics, community, and legal pages).
  • The official LuzRD Android app on Google Play.
  • Accounts created with “Continue with Google” to use community chat.
  • Technical data needed to render the map, look up a sector, and protect the service from abuse.

It does not cover third-party sites or apps we link to (for example WhatsApp or Google Play). Those services have their own policies.

3. Data we collect

We only collect or generate what we need to run LuzRD. Depending on how you use the service, we may process:

A) Account data (if you sign in with Google)

  • The email address of your Google account.
  • An internal user ID assigned by our authentication provider.
  • The username you choose for chat (we do not show your Google name on posts).
  • Community role (for example user, moderator, or admin) and first-seen / last-seen timestamps.
  • If applicable: suspension or ban status for community-rule violations.

B) Location data (only if you allow it)

  • On the web: the browser may send latitude and longitude so we can resolve your sector (neighborhood/province). We do not publish your coordinates.
  • In the app: we may use device location to attach an outage report to a map cell and, if you save them, to favorite places.
  • You can deny or revoke location permission in the system. Without it you can still view the map and, on the web, pick a sector manually.

C) Content you post or report

  • Community chat messages, including replies and the associated sector.
  • Reports of inappropriate content (reason, a short snippet, and your username if you are signed in).
  • In the app: outage or grid reports you submit from your device.

D) Technical and security data

  • Authentication session tokens stored on your device.
  • Local preferences: chosen sector, message drafts, muted authors, or hidden posts.
  • IP address on a limited basis to rate-limit abuse (for example geocoding searches) and, in the app, for report and device integrity.
  • In the app: a push-notification token and device registry data if you enable alerts.
  • Aggregated site metrics (page views, performance) via Vercel Analytics. We do not use Google Analytics.

You can browse the map and statistics without an account. A Google account is only required to write in chat, report content, or use app features that need to identify you.

4. How we use data

  • Show the live outage map and statistics.
  • Attach a message or report to the correct sector, not to your exact home address.
  • Authenticate you, keep your session, and display the username you chose.
  • Moderate spam, abuse, impersonation, and harmful content.
  • Count active users in aggregate.
  • Send app alerts if you enabled them.
  • Protect infrastructure (rate limits, fraud detection, and security).
  • Comply with law and valid authority requests when required.
  • Improve the service with aggregated metrics, not advertising profiles.

We do not use your data for personalized ads, we do not sell databases, and we do not build a commercial profile for third parties.

5. Sign in with Google

If you tap “Continue with Google”, Google shows its consent screen and lets us receive at least your email and basic profile data needed to create or restore your session.

  • We use Google only to authenticate you. We do not publish your Google name or photo in chat.
  • Chat shows the username you choose.
  • We do not read your Gmail, contacts, Drive, Calendar, or other Google services.
  • You can revoke LuzRD access from your Google Account settings at any time.
  • Signing out of LuzRD does not automatically delete your account; to erase data you must request it (section 13).

Google Limited Use: LuzRD's use and transfer to any other app of information received from Google APIs will adhere to the Google API Services User Data Policy, including the Limited Use requirements. We do not sell this data and we do not use it for advertising.

6. Location

Location is requested for a specific purpose: knowing which sector you are in so we can tag your message or report. The website is not a continuous tracker.

  • In the browser, the request happens when you use “Use my location” or, on some devices, if you already granted permission.
  • Coordinates are sent to our backend to resolve the nearest sector. The result (sector/province name and slug) may be stored on your device so we do not ask again on refresh.
  • We do not show your GPS point to other users.
  • If you pick a sector manually, we do not need GPS.
  • On iPhone, the system may require a tap before showing the permission prompt. That is an Apple rule, not extra tracking.

7. Community chat

Messages you publish are visible to other people in the national or sector feed. Do not post data you do not want public (phone number, exact address, ID documents, and similar).

  • We filter abusive language and reserve staff names (for example admin) for authorized accounts.
  • You can mute authors or hide posts on your device. That does not delete them from the server.
  • Reporting inappropriate content requires sign-in, to prevent mass anonymous reports.
  • Moderators may delete messages or suspend accounts that break the rules.

8. Map, outage reports, and search

The map shows aggregated grid-status cells (for example a confirmed outage or a pending notice). That public layer does not include your name or email.

  • If you search a place in the directory, we send the search text to a geocoding service (Mapbox; fallback Nominatim/OpenStreetMap) to center the map.
  • We rate-limit those searches by IP to prevent abuse. We do not use that IP to identify you publicly.
  • App outage reports are aggregated by zone (neighborhood consensus). The goal is sector status, not exposing a person.

9. Cookies and device storage

LuzRD does not use a marketing-cookie banner because we do not place third-party advertising cookies. We do use necessary technical storage:

  • Supabase Auth session (Google sign-in) in the browser’s local storage.
  • Chat preferences: sector, GPS/manual mode, message draft, muted authors, and hidden posts.
  • Vercel Analytics, which may use cookies or technical identifiers to measure visits and performance.
  • The map (Mapbox) may cache technical assets to load tiles.

You can clear site data in your browser settings. That will sign you out of the website and forget local preferences.

10. Who we share data with

We do not sell personal data. We share information only with vendors that help us run the service, under their terms and security controls:

  • Supabase (authentication, database, and backend functions). Google sign-in completes through LuzRD’s auth project.
  • Google (OAuth / sign-in and, on Android, Google Play services and notifications).
  • Mapbox (map tiles and, when used, search geocoding).
  • OpenStreetMap/Nominatim (fallback geocoding).
  • Vercel (website hosting, analytics, and frontend delivery).
  • Competent authorities, if a valid law requires a specific disclosure.

These vendors may process data on servers outside the Dominican Republic. By using LuzRD you accept that international transfer as needed to provide the service.

11. How long we keep data

  • Account and community profile: for as long as the account exists or until you request deletion, unless we must keep a minimal record for security or law.
  • Chat messages: while they remain published or are needed for moderation and feed integrity.
  • Abuse reports: for a reasonable time to investigate and prevent repeat abuse.
  • Geocoding rate-limit data: short-lived and in memory.
  • Browser preferences: until you clear them or storage expires.
  • App notification tokens and device registry: while the device is active or you disable alerts / uninstall.

13. Your rights

You may request, reasonably and after we verify your identity:

  • Access: what data we hold about you.
  • Rectification: correct inaccurate data (for example change your username if it is available).
  • Erasure: delete your account, messages, and related data, except legal holds.
  • Objection: object to non-essential processing.
  • Withdrawal of consent: turn off location, notifications, or Google access.
  • Information: a copy of this policy and how we process your data.

Email eipelnatacedeno@gmail.com with the subject “LuzRD Privacy” and say whether you want access, correction, or deletion. We will respond within a reasonable time. Signing out is not the same as deleting the account.

You may also lodge a complaint with the competent data-protection authority in the Dominican Republic.

14. Children

LuzRD is not directed at children under 13. We do not knowingly collect data from children. If you are a parent or guardian and believe a child gave us data, contact us and we will delete it.

Community chat and Google sign-in are intended for people who can consent to processing. If you are between 13 and 17, use the service with an adult’s supervision.

15. Security

We apply reasonable technical and organizational measures: HTTPS in transit, OAuth/PKCE authentication, public keys separated from admin privileges, post rate limits, content filters, and moderation controls.

No system is 100% secure. If you find a vulnerability or an incident affecting personal data, notify us immediately at eipelnatacedeno@gmail.com.

16. Automated decisions

We use automatic rules to filter inappropriate text, limit posting frequency, and aggregate outage reports by zone. This is not credit scoring and does not produce legal effects about you. Community sanctions (deletion or suspension) can be reviewed by a moderator.

17. Third-party links

The site may link to Google Play, WhatsApp, Mapbox, Google, or utility pages. We do not control those platforms. Review their policies before sharing data there.

18. Changes to this policy

If we change this policy in a material way, we will update the “Last updated” date at https://luzrd.com/privacidad. For substantial changes we will try to notice it on the site. Continued use after the new date means you accept the updated version.

19. Contact

Controller: LuzRD

  • Email: eipelnatacedeno@gmail.com
  • Web: https://luzrd.com
  • Privacy policy: https://luzrd.com/privacidad
  • App: https://play.google.com/store/apps/details?id=com.nathan.luzrd

To exercise your rights or ask a question, email eipelnatacedeno@gmail.com