SiegeMarch is operated by DigiReply Ltd. This policy explains what personal data we collect when you play, why we collect it, how we protect it, and your rights over it. We keep this short and plain because we believe you deserve to understand it.
Contents
1. Data We Collect
Account Data
When you create an account you provide:
- Username — displayed to other players in-game (choose carefully; do not use your real name)
- Email address — used for address verification, account recovery, password-change alerts, and critical service notices; never shown publicly
- Password — stored as a salted bcrypt hash; we cannot read it
Automatically Collected Data
When you connect to our servers we automatically record:
- IP address — recorded at signup and each login for security and abuse prevention
- Login timestamps — when you last signed in
- Authentication event logs — successful and failed login attempts, used to detect brute-force or credential-stuffing attacks
Gameplay Data
All in-game actions — village state, buildings, armies, resources, trade, combat, and explored map tiles — are stored in our database to maintain your persistent game world. Chat messages sent in-game are stored for moderation purposes. If you report a message, we store your report (the reason, any details you add, and a copy of the reported message) for our moderators. If you block a player, we store your block list.
Device & Technical Data
When you use the web or mobile app, standard HTTP request metadata is processed (browser type, operating system, referrer). We do not run third-party analytics SDKs and we do not track you across other websites.
Android App
The SiegeMarch Android app collects the same account and gameplay data as the website, plus:
- Push notification token — if you allow notifications, Google Firebase Cloud Messaging gives the app a token that identifies your device for notifications. We store it on our server with your account so we can alert you when you are away from the game: attacks and bandit raids on your settlement, trades, captured captains, and court orders. You can turn notifications off at any time in Android Settings → Apps → SiegeMarch → Notifications. The token is deleted from our server when you log out, when you delete your account, or when Google reports it is no longer valid.
- Session token on your device — the app keeps your login session in its private storage on your phone, as described in Sessions & Cookies.
The app does not access your contacts, photos, location, microphone, or camera, and it contains no advertising SDKs and no analytics SDK such as Google Analytics. Firebase Cloud Messaging may report notification delivery statistics to Google. Bot protection, push notifications and AI advisor briefings involve the third parties listed in Third Parties.
2. Why We Collect It
We collect data only for specific, legitimate purposes:
- Providing the service — running your persistent game world, authenticating your session, delivering real-time gameplay via WebSocket
- Security — detecting and blocking account abuse, credential stuffing, and bot registrations (including Cloudflare Turnstile verification on login, signup, password reset and account deletion)
- Account recovery — your email allows us to help you regain access if you forget your password
- Notifications — in the Android app, alerting you to events in your game while you are away
- Advisor briefings — writing your in-game advisor's daily briefing from your settlement's game state
- Moderation — reviewing chat reports and keeping chat safe
- Service communications — critical notices about the game service (downtime, season resets, security alerts); we do not send marketing emails
- Legal compliance — retaining records as required by applicable law
We do not sell your data, share it for advertising purposes, or use it for profiling.
3. How It Is Stored
Data is stored on servers hosted within the European Union (EU). Specifically:
- PostgreSQL database — account records, gameplay state, login logs
- Redis — active session tokens; these expire automatically after 7 days of inactivity
- Email security records — single-use verification and password-reset token hashes, delivery status, and encrypted pending link secrets; raw action tokens are not stored in plaintext
- Server access logs — standard nginx logs retained for up to 30 days, then deleted
Backups are encrypted at rest. We do not store payment information — SiegeMarch currently has no paid features.
4. Third Parties
We use a minimal set of third-party services:
- Cloudflare Turnstile — a privacy-respecting bot-detection check shown on the login, registration, password-reset and account-deletion forms, on the website and in the Android app. Cloudflare receives your IP address, browser and device characteristics, and the challenge result to verify you are human. Cloudflare's own Privacy Policy applies to this data.
- Google Firebase Cloud Messaging (Android app only) — delivers push notifications. Google receives the app's push token and the text of each notification in order to deliver it to your phone. See Android App for how to turn notifications off. Google's Privacy Policy applies to this data.
- DeepSeek (AI advisor briefings) — once a day, when AI briefings are enabled, our server sends DeepSeek, an AI model provider whose servers are in China, a snapshot of your settlement's game state so it can write your in-game advisor's briefing. The snapshot contains game information only: resource stocks, buildings, population, territory size, stationed armies, your captains (named by the game), nearby bandit camps, the size and distance of nearby settlements, recently completed trades, in the Ottoman realm your court standing and imperial orders, and the language of the briefing. It contains no username, email address, IP address, device information, chat messages, or clan or character names chosen by you or other players, so it does not identify you. DeepSeek returns the briefing text, which we show only to you. If DeepSeek is unavailable, the game writes a simpler briefing itself.
- Transactional email provider — processes your email address and the verification, recovery, or security message required to deliver account emails. We do not use this service for advertising.
- Google Fonts — the landing page loads fonts from Google's CDN. Google may receive your IP address as part of this request. You can avoid this by using the game directly at /game.html which does not use Google Fonts.
We do not use Facebook Pixel, Google Analytics, or any other behavioural tracking services.
6. Security
We take reasonable technical measures to protect your data:
- All connections are encrypted with TLS (HTTPS/WSS)
- Passwords are hashed with bcrypt (cost factor 10) — we cannot recover your plaintext password
- API endpoints are rate-limited (5 auth requests per minute per IP) to resist brute-force attacks
- Bot detection via Cloudflare Turnstile on all auth endpoints
- Login failures are logged and can trigger automated IP blocking
No method of transmission over the internet is 100% secure. If you discover a security vulnerability please contact us at security@digireply.com before disclosing it publicly.
7. Data Retention
- Account data — retained for as long as your account exists. When you delete your account, your email address and username are removed immediately and your chat messages are hidden. Your password hash, IP addresses, login records and chat text are kept for 90 days for security and abuse investigations, then erased automatically. Deleted accounts cannot be restored.
- Login logs — retained for 12 months, then automatically purged
- Push notification tokens — kept until you log out of the app, delete your account, or Google reports the token is no longer valid
- Moderation records — chat reports and automatic chat-moderation records are kept while needed to keep the community safe; when an account is deleted, the text of its messages in these records is erased 90 days later
- Gameplay data — game worlds reset at the end of each season; historical season summaries (username, rank, score) may be retained indefinitely for leaderboard purposes. After account deletion they remain under an anonymous label.
- Server access logs — 30 days
You can delete your account and associated personal data at any time, in the game under Settings → About → Delete Account, or on the web at siegemarch.com/delete-account.
8. Your Rights
Depending on where you live, you may have the following rights regarding your personal data:
- Access — request a copy of the personal data we hold about you
- Rectification — ask us to correct inaccurate data (e.g. your email address)
- Erasure — delete your account and personal data yourself, in the game or at siegemarch.com/delete-account, or ask us to do it
- Restriction — ask us to limit how we use your data while a dispute is resolved
- Portability — receive your account data in a structured, machine-readable format
- Objection — object to processing based on legitimate interests
To exercise any of these rights, email privacy@digireply.com from the address registered to your account. We will respond within 30 days.
If you are in the EU/EEA and believe we have not handled your data lawfully, you have the right to lodge a complaint with your local data protection authority.
9. Children
SiegeMarch is not directed at children under 13 (or under 16 in the EU). We do not knowingly collect personal data from children. If you believe a child has created an account, please contact us at privacy@digireply.com and we will delete the account promptly.
10. Changes to This Policy
We may update this policy as the service evolves. When we make material changes we will update the effective date at the top of this page and, where appropriate, notify registered players by email. Your continued use of SiegeMarch after any change constitutes acceptance of the updated policy.
11. Contact
For privacy-related questions or requests:
- Email: privacy@digireply.com
- General: contact@digireply.com
DigiReply Ltd — Operator of SiegeMarch