Privacy Policy

Yomira is operated from Virginia, United States. This Privacy Policy explains how the operator of Yomira handles personal information in connection with the Yomira apps, website, accounts, public catalog, community and related services. The contact for privacy, account and data requests is [email protected].

1. Scope and important distinctions

This policy applies to information processed by Yomira's operator. It does not replace the policies of an external reading source, metadata provider, operating system, app store, email provider or other third party. Their practices can apply when you use their services, even if you reach them through a feature in Yomira.

The distinction between your device and our account infrastructure is important. The native reader can maintain a local library, local downloads and reader settings without a Yomira account. Account features such as reading sync, profile sharing and community participation require some information to be processed by our servers. Local storage and cloud storage are different; information you choose to sync is no longer exclusively on your device.

The public catalog is also different from your private account. It contains information about works, including identifiers, titles, descriptions, cover images and provider references. Those catalog records are not copies of your local books or a disclosure of your private reading history. Browsing a catalog page nevertheless involves a normal network request that can produce technical or security records.

Features differ by platform, release and service availability. Describing a category of information does not mean every feature is enabled for every user, or that all information in that category is collected in every interaction.

2. Who operates the service and how to contact us

In this policy, Yomira, we, us and our refer to the operator of the Yomira service, based in Virginia, United States. This policy does not represent that a metadata provider, publisher, reading source, Apple or Discord operates Yomira or endorses it.

Send privacy questions, requests to exercise data rights, reports of an account belonging to a child, and questions about our processing to [email protected]. Please describe your request and, where relevant, the account username or email associated with it. Do not send passwords, authentication codes, recovery codes, private keys or other login credentials.

We may ask for proportionate information to confirm that you are authorized to act for an account. A request from an unverified address does not by itself authorize disclosure of another person's data or changes to their account.

3. Local reading without an account

You can use supported local reading features and browse the public catalog without creating a Yomira account. Your device can store library entries, source configuration, downloaded reading material, imported files, bookmarks, reading positions and reader preferences.

Local reading material can include files you import or material your device retrieves from a source you choose. Yomira's cloud account infrastructure is not a public archive or upload service for complete manga chapters, comics, novels, PDFs or ebooks. Local files on your own device are not automatically uploaded merely because you install the app or sign in.

Local information remains subject to your device's security, your operating system's permissions and any backup or device-transfer features you independently enable. An operating-system backup is distinct from a Yomira cloud-account export or sync operation. You should understand your device settings if you want to control those copies.

Removing an app, signing out, turning off sync and closing an account can have different effects. None should be assumed to erase every local or remote copy unless the relevant control explicitly says it does so.

4. Account and profile information

When you create or manage an account, we process information such as your email address, username, display name, date of birth, password hash, account status, verification status and selected preferences. A date of birth is used for minimum-age and age-appropriate access controls and is not intended to be a public profile field.

You may provide profile material such as an avatar, banner, biography and other supported fields. Profile information can become visible according to the feature's visibility rules and your choices. An avatar shown beside a public post or profile can be available to people who are not signed in.

We do not store your account password as plaintext. Password hashing does not mean that every other account field is unreadable to the operator. Authorized access to account information can be necessary for support, security, moderation and legal obligations.

Some account changes are restricted or require verification. Those restrictions help protect the account and maintain the integrity of information such as age, email ownership and registered-device access.

5. Authentication, sessions and registered devices

We process the records needed to establish, maintain, refresh and revoke account sessions. These can include session identifiers, creation and expiry times, client and device information, trusted-session status, verification outcomes and records of access being revoked.

Supported native apps use the device Keychain for durable account credentials. Web sign-in uses protected cookies. We also process information needed for two-factor authentication, recovery and security challenges when those features are used. Authentication information should not be shared with support staff or included in a public ticket.

Native device-verification features can involve Apple attestation and cryptographic assertions. These support device and request verification; they do not give Yomira access to your photos, contacts, messages or unrelated device files. App permissions, if requested for another feature, have their own purpose.

Additional verification can be required after suspicious activity, account changes or other security events. An email recovery or challenge process can create records of the request, delivery and outcome. A successful challenge does not require us to expose the underlying verification code publicly.

6. Reading sync, activity and shared lists

When you use account-based reading features, your devices may send reading sessions, progress changes, title and source identifiers, chapter or page positions, completion information, timestamps and other information needed for that feature. The server can merge supported changes and return account information to your other devices.

This processing can support heatmaps, reading totals, progress continuity and shared lists. It does not require uploading a complete book merely to record a reading position. A title identifier, source identifier or reading timestamp can still reveal something about your interests and should be treated as account information when associated with you.

Lists and activity have their own visibility controls. A list you publish is different from private synced progress. Choosing private visibility limits ordinary public access; it does not make server-held information end-to-end encrypted against Yomira's operator.

Turning off future synchronization stops the supported future transfer behavior; it is not necessarily a request to delete records already received. If you want previously synced information removed, use the available deletion controls or contact us.

Network failures, concurrent device changes and different app versions can affect when a change appears. This policy describes information handling and does not promise instantaneous or lossless synchronization in every circumstance.

7. Public catalog, metadata and aggregators

The catalog can use information from metadata aggregators such as MangaBaka, underlying databases, publisher references and community or editorial corrections. This can include titles, alternate names, creators, publication information, classifications, descriptions, covers, provider identifiers and external references.

A catalog entry is not a claim that Yomira owns the referenced work or the third-party metadata. Metadata can contain factual information as well as expressive material protected by copyright or other rights. Aggregator-originated data and upstream-provider data can have different terms and attribution requirements.

We may store and serve catalog images and descriptions through Yomira's infrastructure for consistent presentation. Those stored metadata assets are distinct from full chapter pages or books supplied by external reading sources. This policy does not describe third-party artwork as ownerless or promise that every catalog field is in the public domain.

An individual catalog visit, search, image request or error can create technical records even when browsing without an account. The presence of a title in those records is not the same as intentionally publishing an account's reading activity.

8. Uploaded avatars, banners and image history

When you upload a supported image, we receive the image file and technical information needed to validate, store and serve it. Depending on the feature, we may process its format, size, dimensions, storage reference and upload time. Animated images can contain multiple frames; all frames are part of the uploaded file.

An uploaded image can itself reveal personal information or include embedded information. Use an image you have permission to use, and avoid uploading material that reveals sensitive information you do not intend to disclose. This policy does not promise that every possible image format's embedded information is removed.

Avatar history is limited by the allowance configured for the service and shown through available account controls. Older versions beyond that allowance can be scheduled for removal. We do not offer unlimited avatar history, and replacement does not necessarily delete the previous image in the same instant.

Changing the current avatar can leave permitted earlier versions available for restoration until their retention ends. Publicly displayed copies may also have been cached by another person's browser or a network delivery service.

9. Community contributions, moderation and support

We process the reviews, lists, reports, tickets, profile material and messages you submit through supported service features. Public contributions can be visible to other users and visitors. Support correspondence and internal moderation records are different from public posts.

Authorized staff may review relevant account information, reports and support material to investigate a problem, enforce rules, protect users or resolve a request. Access is limited by the responsibilities and permissions assigned to staff. We do not represent that private support information is invisible to staff who need it to handle the matter.

Moderation or account decisions may create records of actions, reasons and related evidence. You should avoid putting passwords, recovery codes or unnecessary sensitive documents into a support request. If additional information is needed, we will explain the request rather than ask you to disclose authentication secrets.

10. Technical, security and operational information

Requests to our service and infrastructure can involve IP addresses, request paths, times, browser or app information, response outcomes and related technical data. Some security and request-limit identifiers are pseudonymized or derived from request information. Pseudonymization reduces direct exposure but is not a promise that all information is anonymous.

We use technical information to deliver responses, diagnose faults, enforce limits, investigate unauthorized access and manage service capacity. Security records can include failed sign-in attempts, verification failures, unusual request patterns and administrative events.

Hosting and delivery providers may also process request information for their own infrastructure operation and security responsibilities. It is not possible to retrieve a web response or image without the receiving infrastructure processing some request information.

We do not use these records to create advertising profiles or sell private reading interests. Operational use is separate from public profile visibility.

11. Email, account notices and notification features

We use email for verification, recovery, account-security events, supported account changes and service communications. Sending a message requires processing a recipient address and relevant message information. Delivery providers can return outcomes such as delivery, bounce, complaint or suppression information.

Delivery and abuse-prevention records can be retained separately from a message's sensitive payload. Verification links, codes or recovery details can expire before delivery records are removed. A security notice should not be assumed to be a marketing subscription.

Where supported, notifications can involve delivery identifiers and preferences. An optional server-backed alert can require selected information to be processed by the server; an on-device alert can operate differently. The available feature and its controls determine what is sent.

Operating-system permissions control supported notification delivery to your device. Disabling optional notifications does not automatically delete your account or stop communications necessary to secure and operate it.

12. Optional Discord connections

If you choose Discord sign-in or account linking, Discord can provide an identifier, display information and, when the requested permission allows it, an email address and verification status. We use that information to establish or manage the connection and support the selected account feature.

Where configured, role synchronization can involve account eligibility, a linked Discord identity and the role or server information needed for the operation. A role or connection is not a public disclosure of your entire reading library unless a separate feature and your choices provide for that disclosure.

Discord controls its own accounts, servers, permissions and privacy practices. Unlinking an identity from Yomira and disconnecting an application in Discord are separate actions. Unlinking does not automatically erase public Discord messages or records retained by Discord or a server's administrators.

13. Sources of information

We receive information directly from you, from devices and browsers interacting with the service, from supported account integrations, from infrastructure and delivery providers, and from people who submit reports or support material about activity on the service.

Catalog information can come from aggregators and other public or provider-supplied records. Receiving a person's name in a creator credit is distinct from creating a reader account for that person. If a public record incorrectly identifies you or exposes information that should be corrected or removed, contact us with the relevant Yomira URL and an explanation.

14. Purposes and applicable processing bases

We use information to provide requested account and reading features; protect accounts and infrastructure; enforce age, access and visibility controls; serve uploaded images; operate community and support functions; communicate about the service; meet legal obligations; and resolve disputes or investigate abuse.

Where a law requires a processing basis, the relevant basis can include performing a requested service or agreement, our legitimate interests in secure and reliable operation, compliance with legal obligations, and consent where that is required. We do not treat agreement to a privacy policy as permission for every possible future use.

When processing depends on consent, withdrawing that consent affects future processing based on it, subject to applicable law. It does not automatically invalidate earlier lawful processing or processing that must continue under another lawful basis.

15. Information we do not sell or use for advertising

We do not sell personal information, rent private reading histories, provide private account information to data brokers, or use account and reading information to build behavioral advertising profiles. We do not use advertising cookies or cross-site advertising trackers on the basis described in this policy.

This commitment does not mean that necessary service providers never receive information, that public posts cannot be viewed by others, or that an external source you visit has the same practices. The provider and sharing sections explain those different circumstances.

16. Visibility, recipients and public copies

Information can be disclosed to the audience of a public profile, post or list, to the limited audience allowed by a supported visibility setting, to authorized staff handling operational matters, and to providers that deliver the relevant service.

Public content can be indexed by search engines, appear in link previews, be cached or be copied by other people. We cannot promise to retrieve every third-party copy after you change a setting or delete a contribution. Do not publish information that you need to keep confidential.

We may disclose relevant information to comply with applicable law or valid legal process, or when reasonably necessary to protect users, the service or others from harm or abuse. A transfer of the business or service can involve transferring records, subject to applicable law and any required notice.

17. Infrastructure and service providers

Current infrastructure providers include Cloudflare for traffic delivery, security and object storage; Resend for email delivery; and Contabo for server hosting. Apple supports app distribution and native device-attestation services. Discord is involved when you use supported Discord connection features.

The information a provider receives depends on its function. An email provider needs recipient and message information; a delivery or security provider processes network requests; object storage holds supported assets or artifacts; and a hosting provider supplies the systems on which our service operates.

A provider's inclusion here does not mean it receives every category of account information. Providers can change as the service develops. We will update this policy or provide other required notice when a change materially affects information handling.

18. External sources and websites

A source, publisher, database or other site outside Yomira can receive information when your device or a supported server feature makes a request to it. Depending on how a feature operates, it can see your device's request information or the information of the server making the request, together with requested identifiers or content.

Source-specific sign-in, cookies or permissions are separate from a Yomira account. Providing credentials to an external source is not the same as providing credentials to Yomira. Review that source's terms and privacy practices before using it.

A link, Connector Profile or metadata reference does not place the external site under Yomira's control or guarantee its security, availability or privacy practices.

19. Storage, access and security safeguards

We use safeguards appropriate to the service, including password hashing, protected authentication, access controls, request limits, verification checks and security auditing. Sensitive operations can require stronger verification than ordinary browsing or token refresh.

Server-held account information is not promised to be end-to-end encrypted against the operator. Some sensitive records use additional protection, but we do not claim that every field, log, image or backup is encrypted in a way that prevents all operational access.

No network, device or service can guarantee absolute security. You can help protect your information by securing your devices, using supported two-factor authentication, reviewing registered access and avoiding disclosure of authentication secrets.

20. Retention and expiry by category

We keep information for the purposes described in this policy, considering the feature, whether an account is active, security needs, applicable law and legitimate operational requirements.

• Account and synced data: maintained while needed to operate the account and requested features, subject to closure, deletion and applicable retention requirements.
• Public contributions: maintained while published or otherwise needed for the supported feature, with possible limited retention for moderation, disputes or legal obligations.
• Avatars and uploaded assets: maintained while referenced or within permitted history; obsolete assets can be scheduled for removal and may not disappear from every cache immediately.
• Account exports: generated export files expire after 24 hours from the export request. An export request does not create a permanent backup service.
• Verification and recovery records: expire or are revoked according to their security purpose; delivery and audit records may outlast the usable link or code.
• Email and support records: retained as needed to deliver messages, resolve requests, prevent abuse, manage delivery problems and meet applicable obligations.
• Operational and security records: retained according to their function, investigation or legal requirements. Not every operational record has the same fixed expiry.
• Backups and retained evidence: may follow a different retention or deletion cycle from active records and can remain where preservation is legally required.

We do not state a universal deletion period because different records and providers operate differently. Contact us if you need information about a particular request or category.

21. Account closure, deletion and anonymization

You can request account closure through supported account controls or by contacting [email protected]. We may verify your identity before closing an account or disclosing its records.

The closure process revokes supported access and deletes or anonymizes account information and reading records. Stored artifacts can be removed asynchronously. Anonymization is different from deleting every database row: records that no longer identify the closed account can remain for legitimate aggregate or operational purposes.

Some information may remain where needed to meet legal obligations, investigate abuse, resolve disputes or preserve evidence. Copies held by other people, independent sources, your own devices or other providers are not automatically erased by closing a Yomira account.

Deleting the cloud account does not automatically erase local reading files. Conversely, uninstalling the app does not automatically notify us to close the cloud account. Use the relevant control for the result you intend.

22. Access, correction, export and other rights

Depending on the law that applies to you, you may have rights to access information, correct inaccuracies, obtain a copy, request deletion, restrict certain processing, object to processing, withdraw consent, appeal a decision or complain to a regulator.

Available account controls can handle some of these actions directly. For other requests, email [email protected] with enough information to identify the request. We will respond within the period required by applicable law. Rights can have exceptions, including another person's privacy, security, legal preservation or inability to verify authority.

If an authorized representative acts for you, we may request evidence of their authority and confirmation of your identity where permitted. We will not require you to send a password or a two-factor code as a condition of a privacy request.

We do not deny legally required service rights merely because you make a valid privacy request. A request to delete information necessary for an account may nevertheless mean that the account or a requested feature cannot continue operating.

23. Location, international processing and regional protections

Yomira's operator is based in Virginia, United States. Infrastructure, service providers and users can be located elsewhere. Information can be processed in countries other than your own, with different legal protections.

Applicable legal requirements and any required transfer safeguards apply. This policy does not promise that all providers store data only in Virginia, only in the United States, or under one uniform retention rule. Contact us if you need information about processing relevant to a particular legal request.

Where regional law grants mandatory rights, this policy does not waive them or make them conditional on accepting Virginia law in the Terms of Service. Available rights depend on the applicable law and circumstances, not merely on a general statement that all laws apply to everyone.

24. Cookies, local storage and device permissions

We use supported cookies and local storage to maintain sign-in, protect sessions, remember preferences and operate the website. Infrastructure providers can use necessary security mechanisms. Blocking essential storage can affect sign-in, preferences or other functionality.

App permissions are used for the feature that requests them, such as selecting a profile image or enabling supported notifications. Refusing an optional permission can limit that feature without necessarily preventing local reading.

Browser privacy signals and device settings can affect third-party behavior as well as our service. We do not represent that a browser setting automatically deletes information already held in a Yomira account.

25. Children and restricted material

Yomira accounts require users to be at least 13 years old. The service is not directed to children under 13, and we do not knowingly collect their personal information. Users must satisfy any higher minimum age or parental-permission rule that applies where they live.

Age and content controls are distinct. A minimum account age does not authorize access to adult material. Blurring a cover or hiding a category is a presentation control and does not remove legal age restrictions or make inaccurate age information acceptable.

If you believe a child under 13 has provided personal information, contact [email protected] with enough information for us to investigate. Do not publicly identify the child or disclose unnecessary sensitive information in a community post.

26. Future features and policy changes

We can change the service and this policy. A new optional feature can require additional information, controls or notice. We will identify the effective version and provide notice or obtain consent for material changes where required by law.

A policy update is not automatic permission to use previously collected information for an unrelated purpose that requires a different legal basis. Earlier processing remains subject to the requirements that applied to it.

27. Contact and request routing

For privacy, data rights, account closure, correction of personal information or a question about this policy, contact [email protected]. Include a clear subject, such as Privacy request, Account deletion or Data correction, and describe the relevant account or URL.

The same address receives general legal and copyright inquiries under the Terms of Service. Sending a message does not require you to give up applicable privacy rights, and you should not include authentication secrets.