Privacy Policy

App: ReadAloud (Android, package com.bless.readaloud.app)
Publisher: Yramstech
Effective date: 8 May 2026
Last updated: 8 May 2026

1. Who we are

This app is published by Yramstech (the "operator"), based in Ghana. For any privacy-related questions or requests, contact us at support@yramstech.com.

For the purposes of the EU/UK General Data Protection Regulation (GDPR), Yramstech acts as the data controller for the limited information described below. Where we use third-party services (such as Google AdMob and Google Cloud Text-to-Speech), those providers act as separate controllers or processors, governed by their own privacy policies.

2. What information we collect

2.1 Information you provide

The app does not require an account. You may voluntarily provide information when you:

• Email us at support@yramstech.com — we receive whatever you write and your email address.
• Use the in-app "Report" feature, which opens your email client with a pre-filled message you can review and send.
• Open a file from your device storage or from Google Drive — we do not upload the file to our servers; it is processed on your device (with the exception of text you have read aloud, see §3.3).

2.2 Information we generate or collect automatically

Data	Purpose	Stored where
Device identifier — a random hashed string created on first launch and stored locally. It is not Google's Advertising ID and is not derived from hardware identifiers.	Authenticate API requests, distinguish installs for analytics and abuse prevention.	On your device (encrypted SharedPreferences) and on our server.
App version	Compatibility checks, debugging.	Sent with each API request.
Reading session statistics — number of pages read, time spent, document type. Does not include the document content or filename.	Aggregate usage analytics, premium quota enforcement.	Sent to our server and retained as described in §7.
Heartbeat data — periodic ping while the app is open, including timestamp.	Detect active installs, support load planning.	Sent to our server.
Technical request data — IP address, request timestamp, signature header. The IP is part of every internet request and is logged temporarily by our hosting provider.	Security, rate limiting, debugging.	Server logs, kept up to 30 days (see §7).

2.3 Information we do NOT collect

• Your name, email address (unless you write to us), phone number, or postal address.
• Your precise or approximate location (GPS, network-based, or otherwise).
• Your contacts, calendar, photos, microphone audio, or camera.
• The contents of the PDFs or documents you open, except for text you choose to read aloud (see §3.3 below).
• Google's Advertising ID for our own analytics (AdMob uses it under its own policy — see §3.1).

3. Third-party services

The app relies on the following third parties. Each has its own privacy policy that applies to data they receive from your use of the app:

3.1 Google AdMob (advertising)

The app displays ads through Google AdMob. AdMob may collect a device-level advertising identifier, coarse location signals (derived from IP), interaction events with ads, and similar information, in order to serve and measure ads. We do not receive this data directly. Google's policies:

• Google Privacy Policy
• How AdMob handles user data

On Android 12 and above you can reset or delete the advertising ID from Settings → Privacy → Ads.

3.2 Google Cloud Text-to-Speech

When you press play, the text you have selected is sent to Google Cloud Text-to-Speech to generate audio. The text is processed by Google under their service terms and is not used by us for any other purpose. If your document contains sensitive content, please review it before reading aloud.

Reference: Google Cloud Text-to-Speech data logging.

3.3 Google Drive (optional)

If — and only if — you choose to import a document from Google Drive, the app uses Google's Drive API to fetch that single file. We request the minimum scope required and we do not list, catalog, or upload your other Drive files. You can revoke this access at any time at myaccount.google.com/permissions.

3.4 Firebase Cloud Messaging (push notifications)

If you allow notifications, the app registers with Firebase Cloud Messaging (FCM) to receive push messages from us. FCM stores a registration token to deliver these messages. We use this only to send service announcements (e.g. version updates). You can revoke notification permission at any time in Android system settings.

3.5 Our own backend

The app talks to our admin/API backend at https://www.readaloud.yramstech.com/readaloud_admin/ for the purposes described in §2.2. Communication uses HTTPS and is authenticated by an HMAC signature derived from a secret bundled with the app. The backend is operated by Yramstech.

4. How we use the information

• To run the app and enforce abuse limits. The device identifier and HMAC headers verify that requests come from a legitimate ReadAloud install.
• To understand aggregate usage. Reading-session statistics tell us how long the average session is, which helps us prioritise improvements.
• To deliver premium features and quotas when applicable.
• To respond to your support requests.
• To detect and prevent abuse (e.g. block devices that exceed rate limits or violate the terms).
• To comply with applicable law when properly compelled.

Under GDPR, our legal bases for processing the limited data above are: legitimate interests (security, abuse prevention, service improvement), contract (delivering the app's core features you requested), and consent where required (notifications, ads personalisation).

5. Permissions the app requests

Permission	Why
INTERNET	Communicate with our backend, AdMob, and Google Cloud TTS.
READ_EXTERNAL_STORAGE / WRITE_EXTERNAL_STORAGE	Open PDF files you choose and save audio you export. On modern Android this maps to scoped storage / MediaStore.
FOREGROUND_SERVICE / FOREGROUND_SERVICE_MEDIA_PLAYBACK	Continue audio playback while the app is in the background, so you can lock your screen during reading.
POST_NOTIFICATIONS	Show the playback notification and (if you allow) service announcements.
READ_PHONE_STATE	Pause audio playback when a phone call comes in. We do not read your phone number, IMEI, SIM serial, contacts, or call history.

6. Sharing and disclosure

We do not sell your personal information. We do not share it with third parties except:

• With the third-party services in §3, to deliver the features they provide.
• With our hosting provider, which processes server traffic on our behalf as a data processor.
• If required to comply with a lawful subpoena, court order, or other legal obligation.
• To protect our rights, property, or safety, or that of our users or the public, where we have a good-faith belief that disclosure is necessary.
• In the event of a merger, acquisition, or asset sale, the same protections in this policy will continue to apply.

7. Data retention

• Device identifier and reading statistics: retained while your install is active and for up to 12 months after last heartbeat, after which they are deleted or anonymised.
• Server access logs (including IP): up to 30 days, then deleted.
• Support emails: retained for as long as needed to handle your issue and resolve any related disputes, typically up to 24 months.

8. International data transfers

Our server is hosted with a third-party provider whose infrastructure may be located outside your country of residence. By using the app you understand that your information may be transferred to and stored in countries that may have different data protection laws. Where data is transferred out of the European Economic Area, we rely on the European Commission's Standard Contractual Clauses or a comparable mechanism via the third-party provider.

9. Your rights

Subject to applicable law, you have the right to:

• Access the personal data we hold about you.
• Correct data that is inaccurate.
• Delete your data ("right to be forgotten").
• Object to or restrict certain processing.
• Portability — receive a copy of your data in a structured format.
• Withdraw consent at any time where we relied on consent.
• Lodge a complaint with your local data-protection authority.

To exercise any of these rights, email support@yramstech.com with the device identifier shown in the app's Settings → About screen, or describe your install enough that we can locate the records. We will respond within 30 days.

California residents (CCPA / CPRA)

Residents of California have additional rights, including the right to know what personal information is collected, the right to delete it, the right to opt out of the "sale" or "sharing" of personal information (we do not sell or share it as defined under CCPA, but we disclose this categorically), and the right not to be discriminated against for exercising these rights.

10. Children's privacy

ReadAloud is intended for users 13 years of age or older. We do not knowingly collect information from children under 13, and the app is not designed for or directed at children. If you believe a child under 13 has provided us with information, please contact support@yramstech.com and we will delete it promptly.

11. Security

We use HTTPS for all communication with our backend and HMAC-SHA256 signatures to authenticate API requests. The device identifier is generated locally and stored in encrypted SharedPreferences. No method of transmission over the internet or method of electronic storage is 100% secure, however, and we cannot guarantee absolute security.

12. Changes to this policy

We may update this policy from time to time. When we do, we will revise the "Last updated" date at the top of this page. For material changes that affect your rights, we will provide a more prominent notice (such as an in-app message). Your continued use of the app after the change indicates your acceptance of the updated policy.

13. Contact

Questions, concerns, or requests under this policy:
Email: support@yramstech.com
Postal address: available on request via the email above.