Rain Alert Terms of Service

1.0 / 2026-10-17

Rain Alert provides supplementary classroom-event notifications. Pay particular attention to account authorization, the actual effect of ordinary check-in requests, and the limits of push delivery.

1. Scope, provider, and acceptance

These terms apply to the Rain Alert Web App and reminder instance maintained under Sparkle by 唐梓耀 / AdrianSparkle and 丁铭 / EliasSparkle. Read them before connecting, authorizing an account, or enabling reminders. Do not take those actions if you disagree. Continued use alone does not establish separately required consent or guardian authorization.

2. Independent tool and official channels

Rain Alert is not an official product of Rain Classroom, a school, or a teacher. This page claims no partnership, agency, or endorsement by Rain Classroom, WeChat, Apple, or browser vendors. Schools, teachers, and official Rain Classroom records determine schedules, assignments, attendance, and grades.

The product supplements official clients, classroom announcements, manual checking, and your own attendance responsibilities. It does not currently provide comprehensive reminders for all pre-class or post-class assignments, examinations, or school announcements.

3. Eligibility and trusted connections

You must be authorized to use the account and device and follow school, teacher, and platform rules. Do not connect unauthorized accounts, borrow sessions, or distribute administrator connection codes. Minors require guardian authorization as required by law; children under 14 should not connect accounts.

Confirm only official QR logins you initiated. Do not give passwords to maintainers, web forms, or strangers. A reminder-service connection code does not itself grant access to a Rain Classroom account.

4. Authorized processing

After QR confirmation, the server needs to store and use official login credentials to query account details, courses, ongoing classes, and necessary classroom events and notify registered devices. The Privacy Policy explains data, recipients, Hong Kong hosting, and retention.

Understand that scope before enabling reminders. Authorization is not permission to read unrelated material, publish your courses, perform marketing, or train AI models.

5. In-class reminders and check-in effects

Enabling exercise, random-selection, rapid-answer, or comment-availability reminders allows the service to obtain classroom authorization according to platform rules. Where the platform explicitly identifies an ordinary check-in, the service may automatically send a classroom-entry request. That request can create entry or check-in records on the official platform. The service is not entirely read-only.

For dynamic QR, location, or unconfirmed check-in modes, monitoring waits for required actions in the official client. It does not fake location, defeat QR restrictions, replace required personal confirmation, answer questions, respond to roll calls, or enter rapid answers for you. Do not enable related in-class reminders if your school or teacher prohibits automatic entry. The platform determines official records.

6. Switches, testing, and notification content

Five reminder types are controlled per device. System permission and individual reminder switches are different settings. Push testing sends five clearly labeled simulated messages even if corresponding switches are off, without changing them. Successful testing does not verify the live classroom event source.

Random-selection notifications may show names and student numbers announced to the class. Other notifications show course and event summaries. Manage previews and shared devices and do not publicly forward classmates’ information. If no trustworthy start time is supplied by the platform, displayed detection time is not the class start time.

7. Timing and reliability

Polling at approximately five seconds under normal conditions works alongside classroom-event connections. This is not a delivery deadline or service-level guarantee. Platform changes, networks, maintenance, power saving, permissions, push vendors, browser policies, invalid login, or expired pairing can delay, omit, repeat, or stop messages.

“Accepted by push service” confirms acceptance of a request. A device receipt confirms system handling, not that a person read or heard the notification. Continue checking official channels; do not rely solely on this tool for attendance, exams, or important deadlines.

8. Devices, expiry, and origin migration

Device connections normally last 30 days and can be manually renewed. Review associated devices and revoke unfamiliar ones. Changing the connection code does not revoke existing devices. Expired official authorization or pairing affects monitoring and reminders.

The main and retained legacy entry points are distinct browser origins. A single-use, five-minute credential migrates the account, settings, and necessary history; notification permission must be granted again on the new origin. A migration link confers temporary access and must not be shared. Deactivation of the old subscription depends on successful registration of the new one.

9. Acceptable use

Do not bypass school or platform controls, falsify attendance, steal or share credentials, collect unrelated people’s data, harass or infringe rights, abuse push delivery, attack interfaces, or resell unauthorized access. Do not use courses, names, student numbers, or learning activity for advertising profiles or public exposure.

Ordinary use must still satisfy platform and school rules; the product cannot obtain third-party permission for you. If you find an unfamiliar device or incorrect delivery, disable relevant reminders, revoke devices, and contact maintainers.

10. Availability, fees, support, and changes

The service is currently in public testing. Permanent availability, permanent free access, fixed response times, and specific capacity are not promised. Any charge, subscription, or material new condition should be clearly disclosed before taking effect and follow required procedures. These terms alone create no payment obligation.

Maintenance, security, capacity, and upstream changes may require adjustment or suspension. Where reasonably foreseeable, appropriate explanations and guidance for migration, export, or discontinuation should be provided. Urgent risks may require necessary action first and an explanation when appropriate, without removing legal duties.

11. Sign-out, suspension, and termination

You may disable reminders, sign out, revoke devices, or stop using the service. Unlinking the last valid device releases login credentials. The Privacy Policy separately explains remaining profiles, history, and backups; discontinuation does not automatically delete an entire account.

Clear abuse, infringement, or security risk may justify restricting relevant connections to the necessary extent, with reasons and an opportunity for feedback or correction where appropriate. Applicable confidentiality, intellectual-property, and data-protection duties survive termination.

12. Rights, warranties, and responsibility

You retain rights in your information. Course materials belong to their rights holders. Processing does not grant the service unrestricted use or sublicensing rights. Product licensing and component terms appear in the Software License and Third-party Notices.

To the extent permitted by law, service is provided in its available condition without a promise of error-free, continuous operation or timely delivery of every message. Responsibility depends on facts, fault, and applicable law. Liability for intentional misconduct, gross negligence, personal injury, unlawful personal-information processing, and other non-excludable matters remains, as do mandatory consumer remedies.

13. Disputes, interpretation, and revisions

Contact maintainers about questions or disputes. You remain free to seek relief from a court or regulator with lawful jurisdiction, without mandatory arbitration, a designated foreign court, or waiver of statutory rights. An unenforceable provision does not invalidate independently effective provisions.

Material revisions will be dated and follow required notice or consent procedures. Language versions aim to be equivalent; translation differences do not exclude local legal protection.

14. Contact

For privacy questions, rights requests, support, or infringement reports, contact maintainer 唐梓耀 / AdrianSparkle on QQ at 2410710390. The developer’s public profile is https://github.com/Tang1206cc. Identify the product, version, and your request. Do not include passwords, login cookies, connection codes, entire recordings, or unnecessary personal information in your initial message.