Izinnnn...

Terms of Service & Privacy Policy

Summary (short)

We operate a Telegram bot that provides weather (BMKG), prayer times (myQuran), todo reminders and motivational messages. This page explains what data we store, where it is stored, and how we use it. We value transparency and professional handling of user data.

Data we store

To provide the service we persist a small set of records associated with your Telegram account:

  • Users: your name, Telegram id (telegram_id), generated API key (api_key) used for authenticating the web app, and timestamps.
  • Todos: title, timestamps and a reference to your Telegram id (user_id).
  • Per-user notification settings: which notifications are enabled, preferred reminder times, selected city/region identifiers.

We do NOT mirror full Telegram chat histories. The bot communicates via Telegram; chat content remains in Telegram unless you explicitly send data to the bot which we then store as part of normal app data (for example when you create a todo via bot command).

Database & storage

The application stores data in a SQLite database hosted on Cloudflare D1. The internal schema and migration details are considered implementation details and are not displayed here. We store only the minimal fields required to run the service (user identifiers, todos, and notification preferences) and use indexes/migrations to keep queries efficient.

How we use your data

  • Authentication: we use api_key and telegram_id to identify your account when you open the web dashboard.
  • Delivering reminders: notification settings determine which automated jobs run for your account.
  • Features like todos are stored so the bot and web UI can show and manage them.

Third-party data sources

Some content is pulled from third-party APIs:

  • Prayer times: myQuran API v3 (<https://api.myquran.com/>).
  • Weather: BMKG (<https://api.bmkg.go.id/>).

We display and link to these sources where appropriate and credit them in the UI.

Security & access

We host the SQLite database on Cloudflare D1. Access to the database is restricted to the application runtime; credentials/secrets are stored using environment variables and not committed to source. We follow standard best-practices: least privilege for services, HTTPS for all external calls, and minimal retention of personally identifiable data.

Data sharing & selling

We do not sell your data. Data is used only to provide the services you've enabled. We may need to share limited data with third-party providers to fetch content (e.g., BMKG/myQuran) but we do not provide your personal data to advertisers or brokers.

Retention & deletion

You can delete your account via the bot or dashboard; that will remove your records from the database (users, todos, and notifications). For audit and safety reasons some logs may be retained for a short period according to our operational needs.

Contact

If you have questions or requests about your data, contact the bot owner via the Telegram bot or the contact method in the project README.

Acceptance

Using the bot or dashboard implies acceptance of these terms. We aim to be transparent and professional; if you have concerns, please reach out.