Privacy Policy & Data Safety | MOC OFFICE

MOC OFFICE is built on a strict privacy-first, on-device-first architecture. Read our full data safety declarations and Google Play Safety disclosures.

Last Updated: August 16, 2026

Publisher: RebelRoot

App Name: MOC OFFICE

Package Name: com.rebelroot.mocoffice

This document sets forth the Privacy Policy and Data Security disclosures for MOC OFFICE. MOC OFFICE is engineered on an offline-first, privacy-by-design architecture. The application does not collect, monitor, track, store, or sell any personal data, document content, or usage telemetry.

1. Privacy Policy & Architectural Commitments

1.1 Zero Telemetry, Analytics, and Tracking

No Telemetry SDKs: MOC OFFICE contains no third-party tracking libraries, advertising networks, device fingerprinting code, or background telemetry services (such as Firebase Analytics, Adjust, or AppsFlyer).
No Remote Document Ingestion: Your documents (PDF, Word, Excel, PowerPoint) are processed, rendered, edited, and saved entirely on your local device. RebelRoot operates no remote backend servers or databases that store your document files.
Local-First Storage: Recent file indices, favorite markers, bookmarks, reading themes, and user preferences reside exclusively within Android internal app storage on your physical device.

1.2 AI Processing and Data Transmission Disclosures

MOC OFFICE provides both on-device and optional cloud-based Artificial Intelligence features for document summarization, extraction, and interactive analysis:

Local On-Device Inference: When utilizing local AI mode on supported 64-bit devices, inference runs directly through our embedded native engine (LLaMA.cpp). No document text or prompts ever leave your device.
User-Initiated Cloud AI: When you choose to utilize Cloud AI services (such as Google Gemini, Groq, OpenRouter, Cerebras, or Mistral), the application transmits only the specific text excerpt or document context explicitly selected for that request directly to the chosen AI provider API.
No Model Training: Document contents sent via standard API integrations are processed for single-turn inference responses and are not retained or utilized to train public foundation models.
Secure API Key Storage: All user-provided API keys are encrypted client-side using Android Keystore and Jetpack Security Preferences. Keys are never transmitted to RebelRoot.

1.3 Android Permissions & Data Safety Declarations

MOC OFFICE requests permissions strictly required to execute core document viewing, editing, and utility functions:

Permission	Functional Purpose	Data Safety & Scope Context
INTERNET	Enables user-initiated requests to Cloud AI providers (Gemini, Groq, etc.) and checking for software updates.	No background network polling, telemetry, or document uploads occur. Operates on HTTPS only.
MANAGE_EXTERNAL_STORAGE (Android 11+)	Enables discovering, indexing, opening, and saving PDF and Office documents across user storage.	Required for full document management functionality. File access is limited to document reading and writing operations initiated by the user.
READ_EXTERNAL_STORAGE & WRITE_EXTERNAL_STORAGE (Android 10 & below)	Legacy file read and write operations for opening and saving documents.	Operates on user-selected files only with Scoped Storage compatibility.
REQUEST_INSTALL_PACKAGES	Allows installing application updates when downloaded directly by the user.	Only invoked when the user explicitly triggers an in-app software update.

1.4 Open Source Engine & Third-Party Libraries

MOC OFFICE utilizes industry-standard open-source libraries to deliver high-performance document handling:

PDF.js & iText 7: Used for standards-compliant PDF parsing, vector rendering, text extraction, and non-destructive in-place editing. All processing is 100% on-device.
Apache POI: Used for local parsing and manipulation of Microsoft Word (.docx), Excel (.xlsx), and PowerPoint (.pptx) file structures.
LLaMA.cpp: High-performance C++ engine for private, offline on-device neural network execution.
Google ML Kit (Offline Mode): Optical Character Recognition (OCR) operates purely using local on-device models without network calls.

1.5 Data Retention and Deletion

Because RebelRoot does not store or process your documents on remote servers:

You retain complete, unrestricted ownership and custody of all files.
Deleting a file within the application permanently removes the physical file from your device storage.
Uninstalling MOC OFFICE removes all associated application settings, cache, and local preferences immediately.

2. Technical Security Implementations

Byte-Level Truncation & Non-Destructive Saving: In-place PDF saves employ atomic file replacement and strict byte-level truncation protocols to eliminate file corruption risks.
Keystore-Backed Cryptography: All sensitive configurations and credentials remain protected behind hardware-backed encryption keys (TEE/StrongBox).
R8 Optimization & Log Stripping: Release production binaries undergo comprehensive ProGuard and R8 bytecode optimization, stripping debug logging, exception stack traces, and internal identifiers.
No Cleartext Network Traffic: Network security configurations strictly forbid cleartext HTTP transmissions.