Privacy Policy

Faith-Stack MDM / JF Android Tablet Device Management Portal

Last updated: March 2026

1. Introduction

This Privacy Policy describes how we collect, use, and protect information in connection with our Android device management (MDM) service. Our service uses Google’s Android Management API (AMAPI) to manage enrolled devices on behalf of your organization.

2. Data We Collect and Store

In addition to data processed by Google’s Android Management API, we store the following in our systems:

• Account data: Admin email addresses, hashed passwords, and role (admin/viewer) for portal access.
• Device mapping data: Custom device identifiers (e.g. ECM numbers), links to Google device names, distribution center, enrollment time, and policy assignments.
• Enrollment and cache data: Pending enrollment tokens, device cache records (device name, model, compliance status, last sync time, enterprise source) to improve performance and avoid excessive API calls.
• Audit logs: Actions performed in the portal (e.g. policy changes, device lock/wipe, group changes) for security and compliance.
• Session data: Session identifiers for logged-in users (stored in cookies and/or server-side store).

3. Data Provided by Google (AMAPI)

When devices are enrolled, Google’s Android Management API provides device and policy information. We use this data only for management purposes, including:

• Device identity (name, model, hardware info)
• Policy and compliance status
• Application allowlists and install states
• Commands we may send (e.g. lock, wipe) when an admin explicitly requests them

Location data is not collected or stored by our backend unless your organization enables location-related policy settings via the Android Management API; any such data is governed by Google’s policies and your device policies.

4. How We Use Data

We use the data above to:

• Operate the MDM portal and authenticate administrators
• Enroll devices and assign them to distribution centers and groups
• Apply and update device policies (apps, restrictions, security settings)
• Execute management actions (e.g. lock, wipe) when an admin initiates them
• Display device lists, compliance status, and reports
• Maintain audit trails and troubleshoot issues

We do not use device lock, wipe, or factory reset as a penalty for non-payment or for purposes unrelated to device management.

5. Transparency: Management Capabilities

By enrolling devices in this MDM, your organization grants the MDM the ability to:

• Wipe or factory reset devices (when an admin triggers the action)
• Lock devices remotely
• Apply policies that may include location-related settings (when enabled by your policy)
• Manage applications (install, uninstall, allowlist/blocklist)
• Configure device restrictions (e.g. camera, storage, network)

End users see Android’s standard “This device is managed” notification. Our management is for enterprise device administration only, not for surveillance.

6. Data Retention and Security

We retain device mapping, cache, and audit data as needed to operate the service and meet compliance requirements. Account data is retained until the account is removed. We use industry-standard measures (e.g. HTTPS, hashed passwords, secure session storage) to protect your data.

7. Your Rights and Contact

If you have questions about this Privacy Policy or wish to exercise your rights regarding your data, contact your organization’s MDM administrator or the operator of this portal (FaithStack.Dev / JF ADC).