Privacy Policy
1) Who we are
This website is operated by ODSOFT LLC (“we”, “us”, “our”). Kervado is a game studio within ODSOFT LLC.
Legal entity: ODSOFT LLC
Address: Proshyan str. 1/11 Yerevan, 0019 Armenia
Contact email: privacy@kervado.com
2) Scope
This Privacy Policy applies to the website available at kervado.com (the “Site”). It does not apply to third-party websites or services we link to (for example, game platforms, stores, social networks, or separate game websites). Those services have their own privacy policies.
3) Information we collect
Information you provide
- Contact information (such as your email address) and the contents of your message when you contact us via email.
Information collected automatically
When you visit the Site, our hosting and infrastructure may automatically process basic technical data (“log data”), such as IP address, device and browser information, pages accessed, timestamps, and referring/exit pages. This information is used to operate the Site securely and reliably and to mitigate abuse.
Information we do not intentionally collect
- We do not require account creation on this Site.
- We do not collect payment details on this Site.
- We do not provide analytics dashboards or tracking-based profiling on this Site.
4) How we use information
We may use the information described above to:
- respond to inquiries and communicate with you;
- operate, maintain, and secure the Site (including preventing abuse and fraud);
- monitor performance and fix bugs;
- comply with applicable laws and lawful requests, and protect our rights.
5) Cookies & tracking
The Site is designed to work with minimal tracking. We do not use analytics or advertising trackers.
Our hosting/security stack may set strictly necessary cookies or use similar technical measures required for basic functionality and security (for example, load balancing, bot protection, and abuse prevention).
If we ever add analytics or marketing tracking, we will update this Privacy Policy and, where required, provide appropriate choices/consent mechanisms.
6) Sharing & third parties
We may share information with service providers that help us operate the Site (for example, hosting, infrastructure, security services, or email service providers). They may process information on our behalf and under appropriate confidentiality and security obligations.
We may also disclose information if required by law or if we believe disclosure is necessary to protect our rights, users, or the public.
7) International transfers
Your information may be processed in countries different from your own depending on where you are located and where our service providers operate. Where required, we take steps intended to ensure an appropriate level of protection for cross-border transfers.
8) Data retention
- Email inquiries: retained as long as necessary to respond and keep reasonable records of our communications.
- Log data: retained for a limited period for security, diagnostics, and operational needs (duration may vary by provider).
9) Security
We use reasonable administrative, technical, and organizational measures designed to protect information. However, no method of transmission or storage is 100% secure, and we cannot guarantee absolute security.
10) Your rights & choices
Depending on your location and applicable law, you may have rights to access, correct, delete, or object to certain processing of your personal information, and to receive a copy of your information.
To make a privacy request, contact us at privacy@kervado.com. We may need to verify your identity before responding.
11) Children
The Site is not directed to children. We do not knowingly collect personal information from children. If you believe a child has provided us information, please contact us and we will take appropriate steps.
12) Changes to this policy
We may update this Privacy Policy from time to time. We will post the updated version on this page and update the “Last updated” date.
13) Public reviews of ODSOFT’s own games
Section added on 2026-09-18 from the ShardPilot privacy policy; it governs the public reviews of ODSOFT’s own games that the studio reads through ShardPilot. The full reviewer notice is at kervado.com/reviewer-privacy-notice.html.
Public reviews of ODSOFT’s own games — version 2026-10-16. Changed from version 2026-09-18: on Steam, public reviews are now copied through Valve’s official Steamworks interface for reading an app’s user reviews instead of the storefront feed, and the refunded indicator is now stored with a Steam review; see the reviewer notice for details. Version 2026-09-18 was corrected on 2026-09-26, with no change of processing: the reference to your right to object now points to the reviewer notice, where that right is set out. The publication date of this notice is shown in the reviewer notice; it is not a collection-start date for every game. For the initial Steam listing, the privacy-policy field carries the studio privacy policy whose public-reviews section links this notice. For later games, that same notice is provided through the store-page privacy-policy field or the game’s own announcement according to its recorded notice-delivery route, without a new notice version. Each game’s recorded delivery route is completed before its reviews are collected.
ShardPilot is ODSOFT LLC’s own platform for reading the public reviews of ODSOFT’s own games published on Steam, the Apple App Store and Google Play under ODSOFT’s publisher identities (Kervado on Steam). This notice covers every game ODSOFT publishes on Steam, the Apple App Store and Google Play under ODSOFT’s publisher identities (Kervado on Steam today). The publisher name on the store page tells you whether a game is ours. We start collection for a store only after that store’s notice channel is completed. While collection is enabled for a covered game, we copy its public reviews through Valve’s official Steamworks interface for reading an app’s user reviews (called with our publisher key) or through the Apple App Store and Google Play developer review APIs so authorised studio operators can read individual reviews, understand reception, improve the games and respond from the studio’s publisher accounts. Our replies are public on the relevant store and can be read by the reviewer and the public. Collection can copy a review again while it remains public; the 30-day review-copy period is not a promise that collection happens only once. You can object or ask about your information at privacy@kervado.com. Deleting our copy does not delete or change your review on the store where you posted it.
We have not appointed a data protection officer; our privacy contact handles requests.
We rely on our legitimate interests under Article 6(1)(f) of the GDPR and UK GDPR to understand and respond to reception of our own games, including criticism and reported problems, so that we can improve them. Our assessment is limited to that purpose and weighs it against your interests and rights, including your right to object, set out in the reviewer notice. Public availability is not your consent to this processing. We do not require a ShardPilot account from you to read your public review.
The internal display includes individual reviews and linked responses for authorised ODSOFT staff: no counts, no export and no individual reviewer profiles. Alongside reply drafting, we use sentiment and priority classification (including whether a review warrants a developer reply) and theme labeling across reviews of our own games. The derived labels, including the needs-reply result, are shown only to authorised operators inside the tool. Including derived labels in a drafting request to the configured LLM API provider or providers (Anthropic and/or OpenAI) is processor input inside the tool; the no-export limit means no publication and no transfer to any other recipient. This review-reading purpose does not include contact marketing or decisions with legal or similarly significant effects about you. For AI-assisted replies, review title and text are sent to OpenAI for embeddings and to the configured completion provider or providers (Anthropic and/or OpenAI) for classification, theme labeling and drafting, with the store provider, rating, locale (language) and app version also sent for classification and drafting and derived sentiment, priority and theme labels used in drafting; each reply is reviewed and edited by a studio operator before publication.
Review-copy retention details
While collection is enabled, it repeatedly checks each linked game listing under a connector for up to 100 recent reviews; the configured interval is 6 hours between passes, with timing varied slightly. Each review copy becomes eligible for removal after 30 days on its store-specific clock: Steam’s last review update, Apple review creation time, or Google user-comment update time, with the batched sweep configured at approximately hourly intervals. The Apple clock uses the supplied creation date; it is not a separately observed edit date. An update can extend that period where it changes the stored clock, and a public review can be collected again after a copy expires. This is not a 30-day maximum measured from the first collection.
Separately stored linked replies use 30 days from reply creation; their audit rows use 30 days from audit-event time, with earlier parent deletion also removing the linked rows. Replies stuck in the publishing state are excluded from the independent reply sweep and can remain beyond that period. The separate AI copy contains the reply draft, derived sentiment and priority labels and scores, and theme labels and confidence scores; it has a 30-day period from AI-copy creation and does not share the reply row’s clock, so later-created AI copies can outlive the source review and editing a draft does not restart that clock. Deleting an integrations review does not by itself delete that separate AI copy; provider-side copies have their own retention setting and are not covered by our local 30-day clock. Separate AI-processing run records keep request filters and caller metadata, review/enrichment/generation references, outcomes, screening/error information and timestamps, with a default 30-day period from run creation; erasure removes matching per-review results, while the remaining run record expires through its separate sweep.
Operational review sync records are kept for 90 days from the start of each collection run and are then deleted; deleting a review does not remove its selected ID or identifying error text from a run record before that record expires. Collection runs left in a running state are marked abandoned after 24 hours and then expire under the same 90-day period; workspace or connector offboarding removes these records earlier. We have not yet verified complete rights handling for identifying sync records; requests about them are handled through the contact channel in this policy.
Suppression and rights-case records
Our suppression policy keeps the matching information needed to prevent a deleted review or an upheld objection from being undone by later collection. Suppression markers have no age-based expiry: they are removed only when the suppression is permanently retired, with a count-only record of that removal. A copy kept outside the main store so the suppression survives a restore follows the marker’s lifetime; that copy is still to be implemented. The policy for the separate identity-free decision reference and count-only receipt is 6 years from the decision. For public Steam reviewers, our policy for the Article 15–21 rights-case record is a separate 6-year period from case closure; it covers the case and request identifiers, coded reviewer identifier and key fingerprint, right requested, state and dates, without a raw reviewer identifier or review content. For Apple App Store and Google Play reviewers, the minimal operator-mediated case file follows the 3-year period from case closure until a store-specific decision is recorded; exported data and unnecessary identity evidence do not inherit that case-file period. The decision-reference period and the Steam case period are accountability policies; neither sets an expiry for suppression markers.
Backups and other copies
Backup copies can outlive removal from the live store. The PostgreSQL backup period is 30 days, configured on 17 September 2026; the first expiry receipt for those backups is still to be recorded. The analytical ClickHouse backup period is 30 days; that is a separate store and does not establish the PostgreSQL limit. The copy policies also set 7 days for local write-ahead or spool copies, 72 hours for abandoned scratch database directories, one day for build artifacts, and 30 days for diagnostic logs and 14 days for traces; VM snapshots, host logs and export destinations remain under the owner’s custody. Those copy policies do not establish that every copy has expired or been removed. Backup copies are for recovery, not ordinary review reading, and erased, restricted or corrected information must be reconciled before restored data is used. Complete copy expiry and restore reconciliation are not yet verified. The separately gated analytical copies have recorded limits of 30 days for review text and 365 days for review facts; these are not the permitted internal review display or proof that analytical collection is active.
14) Contact
For privacy questions or requests, contact: privacy@kervado.com
Company: ODSOFT LLC (Kervado studio)
Address: Proshyan str. 1/11 Yerevan, 0019 Armenia