Privacy Policy GÇö Ray Guardian
App Name: Ray Guardian
Last Updated: April 29, 2026
Contact: support@rayguardian.in
Website: [https://rayguardian.in]
1. Introduction
Ray Guardian ("we," "our," or "us") is a parental control application that helps parents monitor and manage their minor child's digital activity. This Privacy Policy explains what data we collect, why we collect it, how it is used, and your rights over that data.
This application is strictly designed for the parental monitoring of minor children (under 18 years of age) with full parental authority. It is not intended for monitoring adults.
2. Who This Policy Applies To
This policy applies to:
- Parents / Guardians who create an account and manage the app (the "Parent")
- Minor Children whose devices are enrolled by their parent or legal guardian (the "Child")
2.1 Parental Consent and Responsibility
By using Ray Guardian, the Parent confirms that:
- They are the legal guardian of the child whose device is being monitored.
- They have informed the child (where appropriate and required by law).
- They have obtained all legally required consent under applicable laws.
Ray Guardian must not be used for unauthorized surveillance of any individual.
3. Data We Collect
3.1 From the Parent's Device
- Email address and password (for account creation and login)
- Account session tokens
3.2 From the Child's Device
| Data Type |
What We Collect |
Why |
| Location |
Precise GPS coordinates, accuracy, altitude, speed |
Allows parent to locate child's device in real time |
| App Usage |
App name, package name, daily usage time in minutes |
Enforces screen time limits set by parent |
| Device Status |
Battery level, Android OS version, online/offline status |
Ensures the app is functioning and device is reachable |
| Device Identifier |
Android ID (hardware identifier) |
Links child device to parent account |
| FCM Token |
Firebase Cloud Messaging token |
Enables instant remote lock commands from parent |
| Security Events |
Admin removal attempts, VPN usage, app installs/uninstalls |
Sends tamper alerts to parent |
| Browser Activity |
Actively loaded URLs and page titles |
Checked against a predefined blocklist to detect and block explicit adult content |
| Sensor Data |
Accelerometer readings (impact events only) |
Sends a "device drop or hard impact" alert to the parent when sudden impact above 3G is detected |
3.3 What We Do NOT Collect
- Personal messages, SMS, or call content
- Passwords or keystrokes typed by the child
- Photos, videos, or files stored on the device
- Social media message content
- Financial information of any kind
- Browsing history (only the current URL/title is checked in real-time and immediately discarded if safe)
3.4 What IS Stored vs What Is NOT
| Data |
Stored in Database? |
Retention |
| GPS coordinates (last known location) |
G£à Yes GÇö parent needs this to see child's location |
30 days |
| App usage times |
G£à Yes GÇö required for screen time reports |
30 days |
| Security alerts |
G£à Yes GÇö required for parent to review incidents |
90 days |
| Browser history / visited URLs |
G¥î No GÇö only checked in real-time, never stored |
Not stored |
| Messages, keystrokes, files |
G¥î No GÇö never collected |
Never |
| Accelerometer raw data |
G¥î No GÇö only a text alert is sent on hard impact |
Not stored |
Location note: If the child's location permission is turned off, the app will stop collecting GPS data immediately. The last known location already stored in the database remains visible to the parent until it is automatically deleted after 30 days.
4. How We Use the Data
We use collected data exclusively to:
- Provide the parental control features described in the app
- Send real-time alerts and notifications to the parent
- Enforce restrictions configured by the parent (app blocks, screen time, bedtime)
- Allow the parent to locate the child's device
- Maintain security and prevent unauthorized removal of the app
We do not use your data for advertising, profiling, or sale to third parties.
5. How We Store and Protect Data
- All data is transmitted over HTTPS/TLS encrypted connections
- Data is stored on Supabase (hosted on AWS), a SOC 2 compliant platform
- Database access is protected by Row Level Security (RLS) GÇö only the authenticated parent can access their child's data
- FCM tokens and location data are stored only as long as the device is paired
- We do not store browser history beyond real-time content matching for adult content detection
6. Sensitive Android Permissions
Ray Guardian requires the following sensitive permissions. We are fully transparent about their use:
Accessibility Service
Used for: Detecting which app is in the foreground to enforce app blocks and screen time limits; detecting adult content in browser URL bars when a page loads.
Not used for: Reading personal messages, capturing screen content, recording passwords or keystrokes.
Device Administrator
Used for: Allowing the parent to remotely lock the child's device screen; preventing unauthorized uninstallation of Ray Guardian by the child.
Background Location (ACCESS_BACKGROUND_LOCATION)
Used for: Sending the child's GPS location to the parent dashboard even when the app is minimised or the screen is off.
Required disclosure: Location is collected in the background to support the "Locate Child" feature. This collection stops immediately if the device is unpaired or the app is uninstalled.
Usage Stats (PACKAGE_USAGE_STATS)
Used for: Tracking daily foreground usage time per app to display screen time reports and enforce daily limits.
Post Notifications
Used for: Displaying the persistent "Guardian Active" foreground service notification required by Android for background services.
Receive Boot Completed
Used for: Automatically restarting the Ray Guardian protection service after the device is rebooted, ensuring continuous parental controls remain active without requiring manual intervention.
7. Data Retention
| Data Type |
Retention Period |
| Location logs |
30 days, then automatically deleted |
| Activity logs (app usage) |
30 days, then automatically deleted |
| Security alerts |
90 days |
| Account data |
Until account is deleted by the parent |
| FCM tokens |
Until device is unpaired or app is uninstalled |
8. Data Sharing
We do not sell, rent, or share user data with third parties except:
- Supabase (database and edge function hosting) GÇö bound by their Data Processing Agreement
- Google Firebase (FCM push notifications) GÇö only the FCM token and command payload are sent for lock commands and security alerts; no personal data
- Law enforcement GÇö only if required by valid legal process
9. Children's Privacy (COPPA / DPDP Compliance)
Ray Guardian is a tool for parents to protect children GÇö it is not a service directed at children. The child does not create an account. All child data is collected under the authority and consent of the parent or legal guardian who set up the account.
Parents may delete all child data at any time from the Parent Dashboard by deleting the child's device profile or the entire account.
10. Your Rights
As a parent/guardian using Ray Guardian, you have the right to:
- Access all data collected about your child's device
- Delete your account and all associated data at any time
- Export your activity data on request (contact us)
- Correct any inaccurate profile information
- Withdraw consent by unpairing the child's device and deleting your account
To exercise any of these rights, contact us at: support@rayguardian.in
11. Third-Party Services
12. Changes to This Policy
We will notify registered users by email if this policy changes materially. Continued use of the app after notification constitutes acceptance of the updated policy.
13. Contact
If you have questions or concerns about this Privacy Policy:
Email: support@rayguardian.in
Website: [https://rayguardian.in/docs/PRIVACY_POLICY.md]
14. Data Breach Notification
In the event of a data breach, affected users will be notified within a reasonable timeframe as required by applicable laws.
15. Jurisdiction
This Privacy Policy is governed by the laws of India. Any disputes shall be resolved in the courts of Belagavi, India.
This privacy policy was last reviewed on April 29, 2026.