Privacy Policy for InOut

Last Updated: February 20, 2026

1. Introduction

Welcome to InOut. This Privacy Policy explains how we collect, use, and protect information within the InOut mobile application. InOut is a tool designed for Teachers, Administrators, and Inventory Managers to track the distribution and return of electronic devices (laptops, phones, etc.).

2. Scope of Service

InOut serves as a logging interface. It is intended for use by institutional users to manage assets assigned to end-users.

3. Information We Collect

To provide the core functionality of device log, the app collects the following data points:

• Authentication Data: We use Supabase Authentication. When a User signs up, we collect their email address and unique User ID (UID) to secure their specific device database.
• Inventory Data: We store information provided by the User regarding assets, including Device Name, Device Type, and Device Owner Name.
• Log Data: We record the Timestamp of when a device is "Taken" or "Returned" to calculate usage duration and compliance with schedules.
• Camera Access: The app requires permission to use the Camera solely for scanning QR codes to identify devices. We do not store or transmit photos or videos.

4. How We Use Information

The data collected is used strictly for the following purposes:

• Inventory Monitoring: Allowing User to see which devices are currently out.
• Security & RLS: We utilize PostgreSQL Row Level Security (RLS) to ensure that a user can only view and manage the devices and logs they created.
• Accountability: Generating history logs to identify late or devices not returned.

5. Data Storage and Third-Party Services

• Database: Our backend infrastructure is powered by Supabase (PostgreSQL). Data is stored in a secure PostgreSQL database.
• Row Level Security (RLS): We implement strict RLS policies ensuring that data is "siloed." A user can only see and manage devices and logs that they personally created. No user can access another user's data.
• Encryption: Data is encrypted in transit via HTTPS/SSL.
• Local Storage: The app may store small amounts of data locally (cache) to improve performance and store user sessions.

6. Data Retention and Deletion

Users have full control over their data.
InOut does not sell, rent, or trade user or student data.
We only share data with third-party service providers necessary for app functionality:

• Retention: Data is kept as long as the User account is active.
• Deletion: Users can delete specific device records within the app, it will also delete any associated logs from the database. If a User chooses to delete their account, all associated device and log data will be purged from the Supabase database.

7. Security

We implement industry-standard security measures, including:

• Encrypted Payloads: QR code data is encrypted to prevent unauthorized manual logging.
• Authenticated Requests: All database interactions require a valid JWT from Supabase.

8. Children's Privacy

While InOut tracks devices used by end-users who might be students/children (who may be under 13), the app is primarly designed for use by Teachers and Administrators.It does not collect personal information directly from students/children. Users are responsible for ensuring they have the right to log student names within their institutional framework.

9. Contact Information

If you have questions regarding this Privacy Policy, please contact us at:
Email Address: megatenlike@gmail.com
Phone Number: +62 882-3222-0652
Whatsapp: +62 882-3222-0652
Instagram: @me_moowi