Prakasham parakkatte..
currentundo?
BACK
LEGAL - TERMS & PRIVACY

Terms & Privacy

Effective 2026-05-15. This page combines the Terms of Service, Privacy Notice, Acceptable Use Policy, API Terms, and support contribution policy.

For Google Play and App Store privacy forms, this service may process optional foreground location, user-generated reports/chat, saved pincode or district preferences, saved KSEB consumer details, optional mobile number, coarse foreground location, push notification tokens, approximate device/app metadata, cookies/local storage, diagnostics, and privacy-friendly analytics for app functionality, abuse prevention, service health, and user-requested alerts.

SUMMARY

currentundo is independent and not affiliated with KSEB. Reports and chat are user-generated and not verified official information. Use at your own risk, follow the rules, and contact currentundo@gmail.com for privacy, legal, abuse, takedown, or payment-support issues.

  1. 01

    WHAT THIS IS

    currentundo is an independent personal project for community-powered Kerala electricity status updates. It includes the currentundo.com website, installed web app/PWA, Android app, iOS app, voluntary reports, district chat messages, pincode status checks, weather context, notification opt-in features, and developer API integrations.

  2. 02

    NO KSEB OR GOVERNMENT AFFILIATION

    currentundo.com is not affiliated with, endorsed by, or connected to the Kerala State Electricity Board (KSEB), any electricity distributor, or any government agency. Information on this service is not official. For verified outage, billing, safety, or emergency information, contact KSEB or the relevant authority directly.

  3. 03

    USER-GENERATED INFORMATION

    Outage reports, availability confirmations, district chat messages, and some API power events are submitted by users or their devices. We do not verify them against official sources. They may be inaccurate, delayed, duplicated, malicious, or affected by local network and device conditions.

  4. 04

    EV CHARGING STATION STATUS

    EV charging station locations, connector details, and power/availability status shown on the map are provided through ChargeMOD API data. currentundo does not own, operate, maintain, verify, or control those charging stations. ChargeMOD data may be delayed, incomplete, unavailable, or different from the physical station condition, and should be treated as informational only.

  5. 05

    NO WARRANTIES OR SAFETY RELIANCE

    The service is provided AS-IS and AS-AVAILABLE, without warranties of accuracy, uptime, fitness, or reliability. Do not rely on currentundo for safety, medical, business continuity, power restoration, emergency, legal, financial, or infrastructure decisions. For official outage information, contact KSEB on 1912 or another official channel.

  6. 06

    ACCEPTABLE USE

    • Submit web reports only for your own current area or a location you are honestly checking.
    • Do not submit knowingly false, misleading, automated, replayed, or bulk reports outside approved API use.
    • Do not flood, scrape, probe, reverse engineer, bypass limits, or manipulate public counts, maps, or chat rooms.
    • Do not post chat or feedback content that is unlawful, abusive, harassing, defamatory, hateful, sexual, private, impersonating, infringing, spammy, or harmful to children.
    • Do not upload secrets, private phone numbers, addresses, payment details, medical details, or other sensitive personal information.
    • We may remove content, hide chat messages, block requests, revoke API keys, or restrict access when needed for abuse, security, legal compliance, or service stability.
  7. 07

    REPORTS AND LOCATION DATA

    Reports may use GPS/native location or pincode-based lookup. Location permission is optional and is requested only when you use a feature that needs it, such as reporting an outage or confirming power status from your current area. Manual pincode reporting still works without location permission.

    When GPS/native location is used, your device asks for foreground location permission and location is read for that user-initiated action. currentundo does not request background location permission and does not continuously track your device. Android and iOS may let you grant approximate or precise location, and you can revoke permission in system settings.

    Pincode and area information may be derived with OpenStreetMap Nominatim. Stored report coordinates are coarsened before saving, and public views expose only sanitized report fields such as district, pincode, area, report type, approximate coordinates, and time.

  8. 08

    MOBILE APPS AND DEVICE PERMISSIONS

    • The Android and iOS apps load currentundo.com inside a native app shell and add native capabilities such as status bar handling, sharing, network awareness, geolocation fallback, and notification opt-in.
    • The app may request foreground location permission only for user-triggered reporting/location lookup features.
    • The app may request notification permission only if you turn on outage alerts, confirmation reminders, or a similar alert feature. Notifications are optional and can be turned off in the app or system settings.
    • The app may store app-local settings such as theme, language, saved pincode, saved KSEB consumer number and section contact details, install/native-app markers, push opt-in state, and cooldown hints on your device.
    • System permission prompts are controlled by Android or iOS. If you deny a permission, related features may be unavailable or may use manual fallbacks.
  9. 09

    NOTIFICATIONS AND PUSH TOKENS

    currentundo may include notification support in the Android and iOS apps. We do not require notifications for normal browsing, reporting, pincode status checks, or chat. Notification permission is requested only after you choose to enable alerts.

    If you opt in, the app may register a Firebase Cloud Messaging or Apple Push Notification token and send it to currentundo with limited metadata such as platform, app version/build, selected pincode, district/area, coarse foreground location shared through app features, saved KSEB consumer/section details, optional mobile number if you provide one, enabled/disabled status, and last-seen time. This data is used to prepare and manage local outage/status alerts and gentle confirmation reminders for the area you selected, not for global spam. For example, currentundo may occasionally ask opted-in users in an affected area to confirm whether power is still out or has returned.

    Notifications should be limited to relevant local status updates, outage/restoration alerts, and occasional confirmation reminders. You can opt out from the app settings or revoke notification permission in system settings. Opting out marks the stored device token disabled where possible. Push providers and mobile operating systems may also process notification tokens under their own terms and privacy practices.

  10. 10

    RATE LIMITS

    To reduce abuse, web reports are limited by anonymous browser cookie and network signals. In normal use, a browser can submit one outage report and one availability or restoration report per signal window of about 10 minutes, with additional network-level abuse caps. Chat messages and developer API calls have their own documented limits. Repeated, bursty, malformed, or abusive requests may receive HTTP 429, be blocked, or have access revoked.

  11. 11

    COOKIES, LOCAL STORAGE, AND ANALYTICS

    currentundo uses an anonymous browser cookie named cu_id to rate-limit reports and chat. The server stores salted hashes of this cookie and IP-derived values for abuse prevention; it also stores limited user-agent strings for diagnostics. The app may store your saved pincode, saved KSEB consumer number and section contact details, optional mobile number, district/area context, coarse foreground location from user-triggered app features, theme, language, install/native-app state, push opt-in state, notification token references, and cooldown hints in browser local storage or native app storage. Privacy-friendly analytics may record page views and events such as report submissions, shares, language choices, app/native usage, notification-setting actions, donation dialog actions, and API documentation usage.

  12. 12

    DISTRICT CHAT

    District chat messages are public within the selected room and are shown with generated aliases rather than real names. Messages are limited, rate-limited, filtered for plain text, and may be profanity-masked or hidden. Recent chat is intended to remain visible for about 48 hours, after which pruning may delete it. We may preserve removed content and associated records if needed for abuse review, legal requests, security, or evidence preservation.

  13. 13

    DEVELOPER API TERMS

    • API keys are bearer tokens. Keep them secret, rotate them if exposed, and create separate keys for separate integrations.
    • You are responsible for reports sent by your devices, automations, servers, and operators.
    • The API is for current Kerala power-event integrations and pincode status reads, not scraping, resale, mass polling, historical replay, or emergency alerting.
    • Respect documented scopes, payload rules, device identifiers, and rate limits. HTTP 429 responses must be backed off.
    • We may suspend, revoke, or limit API access for abuse, leaked keys, security risk, unreliable data, excessive traffic, or legal compliance.
  14. 14

    FEEDBACK AND CONTACT DATA

    Bug reports and feedback may include your message, optional email address, current page URL, rating, hashed IP-derived value, and user-agent string. This is used to understand issues, respond when contact details are provided, improve the service, and prevent abuse.

  15. 15

    SUPPORT CONTRIBUTIONS

    Support payments are voluntary contributions to support an independent personal project. They do not buy goods, services, priority support, official data, or guaranteed uptime, and they are not represented as tax-deductible charity donations. Payments are handled by the payment checkout provider, payment network, bank, and any payment method you choose. For mistaken or duplicate payments, email currentundo@gmail.com with transaction details; also use your bank or payment provider dispute process where appropriate. Refunds are not guaranteed.

  16. 16

    ADS AND SPONSORSHIPS

    currentundo does not currently show third-party ads in the service. We may introduce ads, sponsorships, promoted placements, or similar support features later. If that happens, we will update this policy and any required app-store disclosures before or when those features are enabled, and we will describe any ad-related data use or consent options that apply.

  17. 17

    THIRD-PARTY SERVICES

    The service may rely on Supabase for database, authentication, and realtime features; OpenStreetMap Nominatim for geocoding; Open-Meteo for weather data; Firebase Cloud Messaging and Apple Push Notification service for optional app notifications; Rybbit analytics; Cashfree and payment providers for support payments; ChargeMOD for EV charging station status data; app stores; and hosting, CDN, email, or security providers. Their own terms and privacy practices may apply when your request is routed through them.

  18. 18

    DATA RETENTION

    Reports older than 30 minutes may stop appearing in the live feed but can remain in the database for analytics, historical mapping, service health, and abuse review. Chat is designed for short retention and is pruned around the 48-hour window. Developer account and API token metadata remain while the account or token exists and may be retained after revocation where needed for security, audit, or legal reasons. Mobile device push tokens and alert preferences may remain while alerts are enabled and may be kept after opt-out for a limited period where needed to prevent duplicate registration, troubleshoot delivery, audit consent, or protect the service. Feedback, logs, hashes, and abuse records are kept only as long as reasonably useful unless law or security needs require longer retention.

  19. 19

    PRIVACY REQUESTS

    You can email currentundo@gmail.com to request access, correction, deletion, withdrawal of consent where applicable, or other privacy help. Because many reports and chat messages are intentionally anonymous or pseudonymous, we may need enough information to verify that a record relates to you, and some data may be impossible to link back to a specific person without the browser cookie, account, token, or transaction details.

  20. 20

    GRIEVANCE, TAKEDOWN, AND ABUSE CONTACT

    For legal, privacy, abuse, takedown, impersonation, unlawful-content, payment-support, or data-rights requests, email currentundo@gmail.com. We aim to acknowledge grievances within 24 hours and resolve ordinary requests within 15 days. Urgent privacy, impersonation, or illegal-content reports will be reviewed as quickly as reasonably possible. We may ask for details needed to identify the content, report, chat room, transaction, account, or API key involved.

  21. 21

    LIMITATION OF LIABILITY

    To the fullest extent allowed by law, currentundo and its operator are not liable for losses from inaccurate reports, missed outages, delayed updates, chat content, API integrations, third-party providers, payment issues, downtime, data loss, or your reliance on the service. Your sole remedy is to stop using the service.

  22. 22

    CHANGES TO THESE TERMS

    These terms and privacy practices may change without notice. The current version is always available at currentundo.com/terms. Continued use of the service after a change means you accept the updated terms.

  23. 23

    GOVERNING LAW

    This service is operated from India and governed by Indian law. Any dispute will be resolved in the courts of Kerala, unless applicable law requires a different forum.

BACK TO STATUS