Privacy Policy

1. Information We Collect Across Our Platforms

The scope of data we process depends entirely on which specialized business solution you deploy from our automation ecosystem:

A. Information You Provide Directly:

• 📧 Administrative Contact Credentials: Names, business emails, and organizational telephone contacts submitted via our web portals to request quotes, configure custom milestones, or schedule pilot programs.
• 💬 Support & Engineering Logs: Explanatory technical data and debugging records shared with our developer pool when requesting software adaptations or optimization analysis.

B. Information Automatically Processed via Specialized Platforms:

• 🎮 Mobile Apps & Interactive Curriculum Games: Anonymized mobile hardware metrics, Android™ OS build numbers, and display resolution parameters processed strictly to preserve application UI consistency and game state layouts.
• 🤖 Telegram Chat Automation: Numerical user IDs, group chat identification strings, public handles, and command parameters processed to route church bulletins, track educational leaderboard statistics, and handle trivia engagement logic.
• 📊 Institutional Workspace Metrics: Milestone calendars, celebration dates, student conduct indices, and academic matrices managed by deployment organizations.

2. Google Workspace™ Scopes, Protections & Data Boundaries

When organizations deploy components of our Google Workspace™ suite (such as the Student Conduct Tracker™, Student Birthday Notifications™, Celebration Engine™, Alumni Engagement Engine™, Academic Integrity Quest™, or Policy Reminder System™), our applications require restricted OAuth API permissions to execute workflows successfully. Our data handling boundaries comply with strict security mandates:

A. Detailed Scope Usage and Technical Functions

• 📊 Spreadsheet Processing (https://www.googleapis.com/auth/spreadsheets): Application engines read and write structured rows exclusively to update behavior log trends, find active birthday milestones, clear historical quiz cycles, and process organizational data. This operation is limited entirely to the designated sheet infrastructure established by your organization.
• ✉️ Gmail™ API Access (https://www.googleapis.com/auth/gmail.send): Automated engines utilize programmatic mailing boundaries solely to distribute structured warning notifications, birthday milestone wishes, parent notification alerts, and weekly integrity question briefs directly from your institutional domain.

B. Complete Sharing, Transfer, and Disclosure Prohibitions

PlayToShine does not share, transfer, lease, sell, or disclose Google user data to any third-party entities. All data elements parsed via your authorization paths remain bound to your institutional domain layers. No Google user data is accessible to advertising networks, external database caches, market trackers, or secondary data brokers. Furthermore, data processed via these API integrations is never used, reviewed, or aggregated to develop, optimize, or train artificial intelligence (AI) models or machine learning engines.

C. Advanced Data Protection Mechanisms

To protect sensitive metrics, we enforce the following data security controls:

• Isolated Ephemeral Memory Runtimes: Our codebase processes spreadsheet elements entirely within temporary, in-memory instances during execution triggers. Data is never cached externally or mirrored to any PlayToShine-hosted hardware.
• Cryptographic Authorization Infrastructure: System authentication relies entirely on Google's native OAuth 2.0 access token framework. PlayToShine never collects, views, or stores master enterprise passwords or access keys.
• Native Multi-Layer Security: Because our automation scripts execute strictly inside your company’s Google Apps Script runtime environment, all processed data is automatically encrypted at rest and in transit via Google's enterprise-grade TLS 1.3 infrastructure.

3. Telegram Bot Environment Data Architecture

Our custom chat automation systems parse group commands, quiz replies, and broadcast vectors. Numerical identification tokens are stored strictly to manage group game states, assemble leaderboard calculations, and run target announcement loops. PlayToShine never captures personal conversational matrices or scans wide account telemetry paths outside your configured channels.

4. Purpose of Processing and Intent Systems

We process data across our platform varieties strictly to facilitate core functional operations, including:

• ✅ Running background automated workflows, celebrating staff anniversaries, and generating behavioral alerts.
• ✅ Administering gamified learning dashboards and curriculum quiz tables.
• ✅ Inspecting debug trace lines to clean codebase performance parameters.
• ✅ Drafting structural service quotations, handling contracts, and managing general user support channels.

5. Third-Party Web Analytics, Ad Networks & Commerce Services

To evaluate performance, ensure secure payment routing, and understand site usage, our properties interface with trusted service networks:

• 📊 Web Analytics Integration: Our central landing platforms utilize Google Analytics cookies (Tracking IDs: G-NT5MKGTNWX and G-WBK7VG7BC9) to monitor user behavior, traffic trends, and service interactions. This data is handled in accordance with Google's technical disclosure protocols.
• 💳 Secure Commercial Infrastructure: All regional commercial pricing and transaction parameters are cleared directly through verified architectures including Paystack and Google Play™ Commerce. PlayToShine never collects, archives, or observes personal credit card digits, authorization pins, or private banking details.

6. Child Privacy Safeguards & Educational Data Laws

Our educational modules are constructed for learning spaces. For public store distribution apps, we collect no personally identifiable details from children under thirteen (13), upholding international Children's Online Privacy Protection Act (COPPA) guidelines. For private institutional platforms, the client organization serves as the primary Data Controller, supervising user clearance levels and consent metrics within their sovereign domain.

7. Data Storage Boundaries & Structural Safety Isolation

Your operational records are segmented inside native boundaries:

• 📱 Local Device Sandboxing: Personal app configurations, level paths, and gaming assets are managed directly within your local hardware storage cache.
• ☁️ Enterprise Cloud Isolation: Custom enterprise tracking frameworks, reminder schedules, and spreadsheet inputs live directly in your organization's secure Google Drive™ cloud system.

8. Commercial Data Retention Limits

We keep standard corporate logging files only as long as required to maintain client relationships or satisfy regulatory guidelines. Account configuration items are kept for the duration of your active service subscription, while standard customer support transcripts are permanently purged twelve (12) months after case resolution.

9. User Rights and Compliance Governance

Individual end-users and institutional organizations retain full governance over their technical profiles under Ghana's Data Protection Act (Act 843). You can revoke active OAuth tokens at any time, clear device application histories, or file formal data access balance queries by contacting our security team at contact@playtoshine.com.

10. Policy Amendments

We may update this legal document to preserve compliance with changing cloud storefront policies and platform guidelines. Any changes will adjust the updated effective date at the top of this documentation page.