Privacy Policy
Last updated: May 16, 2026
OMEGATECH ("we," "us," or "our") operates the OMEGATECH DayZ Editor platform at omegaeditor.com. This Privacy Policy describes how we collect, use, store, and protect your information when you use our service.
Our core principle: We hold your server files only as long as you're actively using them. Inactive working copies are deleted automatically on a published schedule — see Section 7 below. We never share your data with third parties for advertising or marketing purposes.
1. Information We Collect
Account Information: When you register, we collect your name, email address, and password (stored as a bcrypt hash — we never store plaintext passwords).
Payment Information: Payments are processed by Stripe. We never see, store, or have access to your full credit card number. Stripe provides us only with a customer ID and basic subscription status. See Stripe's Privacy Policy for details.
Server Connection Credentials: If you choose to connect via SFTP, we store your host, port, username, and password. SFTP passwords are encrypted at rest using AES-256-CBC encryption (Laravel's encryption system). These credentials are used solely to connect to your server on your behalf.
Server Configuration Files: To edit your server configs we need a copy of them in a place our editor can read. How long we hold that copy depends on the connection method you choose:
- ZIP upload/download: You upload a ZIP of your mission and/or profiles folders. The extracted files are stored in a working copy on our servers and stay there until you either clear them manually, delete the project, or the auto-purge schedule removes them after the retention window (see Section 7).
- SFTP pull/push: Files are pulled from your server into a working copy on our platform when you initiate a pull, edited in the browser, and pushed back when you initiate a push. Auto-purge applies to the same working copy.
- Server Host (companion app): Files sync between your server machine and our platform only when you initiate a pull or push. Your server files stay primarily on your server; we hold a working copy while you're editing.
In every case the files we hold are DayZ server configuration files (XML, JSON, CFG) — not personal data.
Usage Data: We log actions you take within the platform (file edits, pulls, pushes, server commands) in an activity log. This is for your benefit — it provides an audit trail of who changed what and when.
Technical Data: Standard web server logs including IP address, browser type, and pages visited. Used for security monitoring and debugging only.
2. How We Use Your Information
- To provide, maintain, and improve the OMEGATECH DayZ Editor service
- To process payments and manage your subscription
- To connect to your DayZ server on your behalf (using credentials you provide)
- To send transactional emails (account verification, password resets, billing receipts)
- To detect and prevent abuse, fraud, or security incidents
- To provide customer support when you contact us
We do not use your information for targeted advertising, sell your data to third parties, or share it with data brokers.
3. Data Storage & Security
- Hosting: Our platform is hosted on secure cloud infrastructure with encrypted storage and automated backups.
- Encryption: SFTP passwords are encrypted at rest using AES-256-CBC. All connections to our platform use TLS/SSL encryption in transit.
- Access Control: Server infrastructure is secured with SSH key-only authentication, firewalls, and restricted admin access.
- Passwords: User passwords are hashed with bcrypt and cannot be reversed or viewed by anyone, including our team.
- API Tokens: Server Host API tokens are hashed in the database.
- Upload scanning: User-uploaded ZIP files are scanned for malware using ClamAV before extraction. Files identified as malicious are rejected and never written to a working copy.
- Upload safety checks: ZIPs are also screened for path-traversal, ZIP-bomb, and decompression-ratio attacks before any contents are written to disk.
4. Server File Handling
Your files, your control. We hold a working copy of your server configs only while you're using the editor, and we do not analyze their contents for any purpose other than providing the service, nor share them with anyone. You can clear your working copy manually at any time from the project's Edit page, and it will also be cleared automatically on the retention schedule in Section 7.
- ZIP uploads arrive on our servers when you upload; pushes and pulls for SFTP/Agent happen only when you initiate them
- File version history is stored to enable rollback functionality
- Project snapshots capture file states at points in time for backup/restore
- When you delete a project, or when the auto-purge schedule runs on an inactive project, all associated cached files, versions, and snapshots are removed
- You can download the full working copy at any time as a ZIP using the Download Working Copy button on the project's Edit page
5. Server Host (companion app)
If you install the OMEGATECH Server Host on your server machine, it communicates with our platform via outbound HTTPS only — no inbound ports need to be opened on your network. The Host:
- Sends heartbeat status updates (server running/stopped, CPU, memory, uptime, mod state)
- Executes only commands you explicitly initiate from the browser (file sync, RCON, server start/stop, mod updates, backups)
- Stores its configuration locally on your machine in
%LOCALAPPDATA%\OmegaAgent\config.json — we have no remote access to your server beyond what you authorise the Host to do
- Authenticates with our platform using a per-Host API token, hashed in our database (we cannot recover a token, only revoke it)
- Can be uninstalled at any time via Windows Add/Remove Programs, immediately severing the connection — uninstalling on the machine also revokes the Host on the platform side after our stale-host check (60 seconds)
The Host binary is signed and runs entirely under your control. It does not transmit any files except those you explicitly pull/push, and does not access user accounts or files outside the configured DayZ server folder.
6. Third-Party Services
We use the following third-party services:
We do not use analytics tracking services, advertising networks, or social media tracking pixels.
7. Data Retention
- Account data: Retained as long as your account is active. Deleted upon account deletion request.
- Server files (working copy): Auto-purged after 30 days of inactivity on a project. You receive a warning email at 23 days of inactivity so you can extend, download, or clean up before files are removed. Any scan, upload, mission selection, or edit resets the clock. Manually clearing the working copy or deleting the project removes the files immediately.
- File version history & project snapshots: Removed together with the working copy on auto-purge or project deletion.
- Activity logs: Retained for up to 12 months for audit purposes.
- Payment records: Retained as required by tax and financial regulations.
8. Your Rights
You have the right to:
- Access your personal data at any time through your account settings
- Update your account information through your profile page
- Delete your account and all associated data by contacting us
- Export your data by downloading your project files (ZIP download feature)
- Revoke server access at any time by removing SFTP credentials or uninstalling the Agent
9. Children's Privacy
OMEGATECH DayZ Editor is not directed at children under 13. We do not knowingly collect personal information from children under 13. If you believe a child has provided us with personal information, please contact us and we will promptly delete it.
10. Changes to This Policy
We may update this Privacy Policy from time to time. We will notify registered users of significant changes via email. The "last updated" date at the top of this page reflects the most recent revision.
11. Contact Us
If you have questions about this Privacy Policy or your data, contact us at: