MannaMila LLC
Skald: Odyssey — Privacy Policy
Version applicability: The no-app-telemetry, advertising-attribution, and content-delivery posture below begins with Skald: Odyssey 0.5.0. Earlier versions could share the historical telemetry described below. Versions before 0.5.0 contain no Meta SDK, send Meta nothing, and do not contact MannaMila's content-delivery service.
Who we are
Skald: Odyssey is a reader for Homer's Odyssey, with source-grounded retellings, historical editions, Greek text, maps, and art. The app is published by MannaMila LLC ("MannaMila", "we", "us", or "our").
For privacy or data requests, contact privacy@mannamila.com. For product support, contact support@mannamila.com.
At a glance
- What changed in 0.5.0: Earlier versions could send pseudonymous usage analytics to Amplitude and crash diagnostics to Sentry. Version 0.5.0 sends neither and creates no Analytics ID.
- Your reading stays on your device: Skald has no account and no MannaMila server holding your saved place, reading choices, or preferences.
- Two other app flows remain: On Android, Meta receives automatic install and app-open events, an SDK identifier, Google's advertising ID where available, and the Play install referrer for campaign measurement; it does not receive what you read. On every platform, Skald asks MannaMila's content service no more than once an hour whether the reviewed library has an update; that request carries no reading data.
- Data an earlier version already sent: If this installation still has its legacy Analytics ID, About & Privacy can prepare a deletion-request email.
- No ads and no reading profile: Skald displays no ads, sells no data, and builds no advertising profile from what you read.
App data
Skald stores your reading position and preferences on your device. The app has no account and no MannaMila server that syncs this reading data.
Beginning with version 0.5.0, Skald does not send usage analytics or crash diagnostics. It does not initialize Amplitude or Sentry, create an Analytics ID, or operate a telemetry upload queue. MannaMila does not receive reading activity or crash diagnostics from version 0.5.0.
Together, usage analytics and crash diagnostics are app telemetry: records about how the app is used and reports about errors or the device. The separate attribution and delivery flows below are not app telemetry and remain disclosed.
Previously shared data
Earlier versions of Skald could send pseudonymous usage analytics to Amplitude and crash or diagnostic records to Sentry. An installation upgraded from an earlier version may retain the random Analytics ID created at that time.
Version 0.5.0 reads that existing ID only to display or copy it in About & Privacy and, at your request, place it in a deletion-request email. The app does not transmit the ID or create a replacement. If no earlier ID exists, Skald displays “No Analytics ID exists on this installation. Version 0.5.0 never creates one.”
To request deletion of earlier Amplitude and Sentry records, use “Request deletion of previously shared data” in About & Privacy or email privacy@mannamila.com with the Analytics ID. Existing records remain subject to the provider retention described under Retention and deletion, and you can request deletion at any time. If no legacy ID is shown, you can still email the privacy address for help, but earlier provider records were pseudonymous and MannaMila may be unable to locate installation-specific records without that ID.
What the no-app-telemetry statement does not cover
“Skald does not send usage analytics or crash diagnostics” describes the app's own telemetry. Two other app flows remain: on Android, Meta's advertising SDK reports installs and app opens automatically; on every platform, Skald can make an hourly content-update check. Neither is controlled by a telemetry switch; version 0.5.0 has no telemetry switch. The Advertising attribution and Content-update requests sections describe these flows and their limits.
Separately, if you email support or privacy, submit the public feedback form, join the product-updates list, or obtain Skald through Apple's App Store or Google Play, those services may process information you choose to provide and routine technical or transaction information. The feedback and product-updates notices explain the corresponding MannaMila forms. Apple and Google handle their store services under their own privacy notices. None of those separate activities causes Skald 0.5.0 to send usage analytics or crash diagnostics.
The public Skald website is also separate from the app. Its hosting provider may process routine request information needed to deliver the site. Two pages — the Odyssey Art Atlas at /mosaic/ and the Odyssey Translation Atlas at /translations/ — use Google Analytics 4 to count page visits and interactions with content, store links, and outbound links. They set first-party analytics cookies prefixed skm_ on this site only, and analytics storage is off by default for visitors in the EEA, the United Kingdom, and Switzerland. The Translation Atlas also carries Amazon affiliate links, which are ordinary outbound links; Amazon processes any subsequent activity under its own privacy notice. No other page of this site deploys an analytics tag, and website measurement is not connected to the app, which sends no usage analytics or crash diagnostics.
Local reading data and platform backup
Skald stores your exact saved place and reading settings, such as the selected length, translation, and display options, in the app's private on-device storage. The app has no account, reading-progress backend, or app-operated cloud sync.
On Android, encrypted Google backup and device transfer carry only the file recording your purchase (datastore/skald_entitlement.preferences_pb). Reading progress, preferences, legacy telemetry identifiers, and content are excluded. Clearing app data or uninstalling removes the active local reading data; a later Google restore may restore only the purchase entitlement.
On iPhone and iPad, Apple's encrypted device or iCloud backup and device-transfer features may preserve app-container data according to your Apple settings. Paid access is re-granted from the App Store receipt. Uninstalling removes the active local copy, although a later Apple restore may restore app-container data.
Data version 0.5.0 never sends
Across app telemetry, attribution, and delivery, version 0.5.0 does not send:
- your reading position, selected book, tier, translation, or reading activity;
- product-interaction analytics, an Analytics ID, crash reports, stack traces, or device diagnostics; or
- your name, contacts, precise location, photos, audio, files, or activity in other apps.
Skald contains no advertising and does not build an advertising profile from what you read. Android advertising attribution and cross-platform content delivery are separate, narrowly described lanes rather than app telemetry.
Skald requests no location, camera, microphone, contacts, photos, or storage access. It collects no payment, health, or fitness data, and no lane described in this policy sends your contacts, precise location, photos, audio, or files.
Advertising attribution
This section describes Skald: Odyssey 0.5.0 and later. Earlier versions include no Meta SDK, send Meta nothing, and declare no SKAdNetwork identifiers. Skald does not display ads, but MannaMila advertises the app and measures which campaigns lead to an install.
On Android
The Android app includes Meta's advertising SDK, facebook-core 18.3.0. When you install and open Skald, the SDK sends Meta automatic install and app-open events for advertising attribution. It collects and sends Google's advertising identifier to Meta where the operating system makes it available. It also sends an SDK identifier and reads the Google Play install referrer — the campaign or link that led to the download. It does not report what you read, and Phase 1 sends no custom reading-funnel or purchase events.
The Android package carries the Play install-referrer permission, Google's AD_ID permission, and four Android Privacy Sandbox permissions for Attribution, Ad ID, Custom Audience, and Topics. Topics and Custom Audience are interest-based-advertising capabilities; Phase 1 does not exercise those APIs. These permissions are part of the Android package whether or not attribution is enabled for a particular release, so disabling initialization does not make the declared permission surface smaller.
On iPhone and iPad
SKAdNetwork is the only iOS attribution mechanism. The iPhone and iPad app links no Meta SDK or other advertising SDK, requests no tracking authorization, and does not use IDFA. The iOS app sends no data to Meta. Apple sends Meta an aggregated install postback itself; the app does not collect a new data type for this mechanism.
Attribution has no in-app opt-out on either platform. It is separate from app telemetry; version 0.5.0 has no telemetry switch and sends no usage analytics or crash diagnostics.
Content-update requests (MannaMila delivery)
Starting with version 0.5.0, Android, iPhone, and iPad can check for reviewed content updates at launch, no more than once an hour. The request goes over HTTPS to https://delivery.mannamila.com, a first-party MannaMila endpoint hosted on Cloudflare. This lane has no separate in-app switch and is separate from app telemetry and advertising attribution.
The endpoint processes the network IP transiently to enforce per-IP rate limits. The request and any resulting download concern public-domain literature and signed content packs. Skald sends no reading history, exact saved place, story passage, reading choice, Analytics ID, or advertising ID through this lane. If the service is unavailable or a request fails, the app continues with its bundled library without interrupting the reader.
How information is processed or shared
We do not sell your data.
- Meta receives the Android install-attribution data described above for its own advertising-measurement purpose.
- MannaMila's delivery service, hosted on Cloudflare, processes the transient request IP for rate limiting and serves public-domain content. Cloudflare provides the network infrastructure for this first-party lane.
MannaMila does not share story passages, reading choices, a legacy Analytics ID, or crash diagnostics with Meta. No data flows from the iPhone or iPad app to Meta, and we do not share data with data brokers.
International users and where data is processed
Skald is offered in the United States, Canada, Australia, and New Zealand. Meta may process the Android attribution data described above, and Cloudflare may process the transient delivery-request IP, in the United States or other countries under their respective terms. Legacy Amplitude and Sentry records sent by earlier versions may remain subject to those providers' processing locations until the records are deleted or expire.
MannaMila does not collect the name or account information needed to identify a reader directly through these app flows. A legacy Analytics ID can help locate earlier Amplitude and Sentry records; it does not identify Meta attribution records.
Information you choose to send separately
If you contact support or privacy, we receive the message, contact address, and other information you choose to include. Do not include a story passage, screenshot, log, or other personal information unless it is necessary for the request.
The feedback form and product-updates list have separate notices at the point of collection. Apple and Google independently process store-account, transaction, and routine technical information when they provide their store services. Their privacy notices govern that independent processing.
Retention and deletion
Records sent by earlier versions remain subject to Amplitude retention of up to 24 months from collection and Sentry retention of 90 days unless they are deleted sooner. These are the approved policy periods. Before release, the owner must recheck both provider consoles and retain dated evidence that the settings still match; if they do not, MannaMila will correct this policy. You do not have to wait for that check to request deletion.
Meta attribution data is retained by Meta under its own policies and schedules. It is not linked to Skald's legacy Analytics ID, so a deletion request to MannaMila using that ID cannot locate or remove Meta's records. Delivery request IPs are processed transiently for rate limiting and are not retained by Skald as a reader record or profile.
On-device reading data persists until you clear app storage or uninstall the app, subject to the platform-backup behavior described above. Retention for support messages, forms, website delivery, and store records is also pending the documented UK processing-inventory review.
Your choices
- On-device data: clear Android app storage or uninstall. On iPhone or iPad, uninstall the app; Apple backup or transfer may later restore app-container data.
- Previously shared data: use “Request deletion of previously shared data” in About & Privacy or email privacy@mannamila.com with the legacy Analytics ID, if one exists, to request deletion of earlier Amplitude and Sentry records. If no ID is shown, you may still contact the privacy address, but MannaMila may be unable to locate installation-specific provider records without it.
- Advertising attribution: there is no in-app opt-out. On Android, system advertising controls can reset or delete the advertising ID where the operating system offers that choice. A legacy Analytics-ID deletion request does not reach Meta's records. On iPhone and iPad, Apple's SKAdNetwork report is aggregated and cannot be linked back to you through Skald.
- Content delivery: there is no separate switch. The check is fail-silent, no more frequent than once an hour, and the bundled library remains usable offline.
Security
Version 0.5.0 has no app telemetry transport. Android distribution artifacts are scanned for retired Amplitude and Sentry runtime markers, credentials, upload endpoints, and telemetry-named payloads. The iPhone and iPad archive verifier separately rejects retired SDKs, telemetry keys, and unexpected privacy manifests before submission.
Network data described in the attribution and delivery sections is sent over encrypted HTTPS, and the Android app does not permit cleartext network traffic. On-device reading progress and preferences remain in the app's private storage. Android build tooling also adds an app-scoped signature permission used only to keep dynamic receivers non-exported; it is not a user-data permission. No security measure is absolute. If you think information you sent through a separate service has been affected by a security incident, contact privacy@mannamila.com.
Children
Skald is intended for a general/adult audience (18+). A parent or caregiver may use it for shared reading, but the adult is the intended operator. It is not directed to children under 13 and is not enrolled in Google Play's Designed for Families program.
The version 0.5.0 app has no account and sends no usage analytics or crash diagnostics. Separate support, form, website, store, attribution, and delivery services remain subject to the limits and notices stated above.
United Kingdom information — pending before UK distribution
MannaMila LLC is identified as the controller for information it receives directly through its privacy and support contacts. The privacy contact is privacy@mannamila.com. A publishable controller address has not yet been verified for this policy.
Before Skald is made available in the United Kingdom, the release record must contain dated, owner- or counsel-approved evidence for:
- UK territorial scope and establishment status;
- whether an Article 27 UK representative is required and, if required, the representative's identity, contact details, and written appointment;
- the ICO data-protection fee self-assessment and its receipt or documented exemption;
- the complete processing inventory for the app, support email, feedback form, product-updates list, stores, site hosting, and historical telemetry, including data categories, purpose, lawful basis, source, recipients, and retention;
- each party's role, processor terms, subprocessors, hosting locations, and any restricted-transfer mechanism and transfer-risk assessment;
- the responsible security and breach owner;
- the UK copyright and text-rights ledger for every shipped source;
- Apple and Google marketplace VAT basis, tax category, and UK price evidence;
- digital-content contract, delivery confirmation, refund, and faulty-content remedy evidence;
- an Online Safety Act scope assessment for the offline app with no user-generated content or search service;
- public Apple and Google GB storefront availability evidence; and
- a live policy hash, effective date, required representative disclosure, platform declaration snapshots, binary and site evidence, limitations, and next review date.
These items are currently pending, so the UK release gate remains blocked. No pending item is a claim that MannaMila has appointed a UK representative, completed an ICO assessment, executed a processor agreement, or selected a transfer mechanism.
If UK data-protection law applies to information processed through a separate service, you may have rights to request access, correction, deletion, restriction, objection, or portability, and to withdraw consent where consent is the basis. Contact privacy@mannamila.com to make a request. You may also raise a concern with the UK Information Commissioner's Office: make a data-protection complaint.
Changes to this policy
If our data practices change, we will update this document and revise the Last updated date. Material changes will be reflected in the app, store declarations, and hosted policy before the changed behavior is distributed.
Contact us
MannaMila LLC
Privacy and data requests: privacy@mannamila.com
Product support: support@mannamila.com
For deletion of records sent by an earlier app version, include the historical Analytics ID shown in About & Privacy, if one exists. Without it, MannaMila may be unable to locate installation-specific provider records. For other questions, include the platform and app version where relevant, but do not include unnecessary personal information.