Privacy Policy

1. Summary of Key Points

This Privacy Policy explains how SIIWARE ("we," "us," or "our") handles information when you use Veelops, our secure remote terminal service.

• Content-blind relay: We cannot see your terminal content. All commands and output are encrypted end-to-end.
• No user accounts: Veelops does not require registration. There are no usernames, passwords, or profiles stored on our servers.
• Minimal data collection: We only process routing metadata necessary to deliver the service.
• App store payments: All payments are handled by Apple App Store or Google Play Store. We never see or store your payment information.

2. What Information We Collect

To provide the relay service, we process minimal technical data:

• Device identifiers: Randomly generated IDs used for routing messages between your paired devices.
• Connection timestamps: When devices connect and disconnect from the relay.
• Message metadata: Message sizes and routing information, not message content.
• IP addresses: For rate limiting and abuse prevention.

3. What We Do Not Collect

We explicitly do not collect or have access to:

• Terminal commands or output
• File contents or system information from your machines
• Usernames, passwords, or authentication credentials
• Personal information such as name, email, or phone number
• Location data beyond what IP addresses may reveal
• Usage analytics or behavioral tracking

4. Payment Data

Veelops subscriptions are purchased exclusively through:

• Apple App Store for iOS devices
• Google Play Store for Android devices

All payment processing, subscription management, and billing is handled entirely by Apple and Google. We do not receive, process, or store any payment card information, billing addresses, or financial data.

For information about how Apple and Google handle your payment data, please refer to Apple Privacy Policy and Google Privacy Policy.

5. Third-Party Services

We use minimal third-party services:

• Apple App Store / Google Play Store: For app distribution and payment processing.
• Cloud infrastructure providers: For hosting the relay server. They only see encrypted traffic.

We do not use third-party analytics, advertising networks, or tracking services.

6. Security Architecture

Veelops is built with security as a fundamental principle:

• Noise IK Protocol: Provides mutual authentication and forward secrecy for the encrypted channel.
• ChaCha20-Poly1305: Industry-standard authenticated encryption for all payload data.
• Content-blind relay: The relay server only handles routing. It cannot decrypt message contents.
• Device allowlist: Only devices you explicitly pair can connect to your sessions.
• Perfect forward secrecy: Ephemeral keys ensure past sessions remain secure even if long-term keys are compromised.
• Device-bound pairing: Only paired devices with valid keys can request session access.

7. Data Retention

We retain data only as long as necessary:

• Connection metadata: Retained temporarily during active sessions, then deleted.
• Rate limiting data: IP-based rate limit counters reset after short periods.
• Server logs: Minimal operational logs may be retained for up to 30 days for debugging and security purposes.

Since terminal content is never accessible to us, there is nothing to retain or delete.

8. Your Rights

Depending on your location, you may have certain rights regarding your data under GDPR, CCPA, or other privacy laws.

However, because Veelops does not require user accounts, does not store personal information, and cannot access encrypted content, there is minimal personal data to access, correct, or delete.

To stop all data processing: Simply uninstall the Veelops app from your device. This removes all local data including your encryption keys and paired device information.

If you have questions about your privacy rights, please contact us.

9. Children's Privacy

Veelops is intended for users who are at least 18 years old. We do not knowingly collect information from children under 18. The Services are designed for professional and technical use.

10. Updates to This Policy

We may update this Privacy Policy from time to time. We will notify you of any material changes by updating the "Last updated" date at the top of this page.

We encourage you to review this Privacy Policy periodically.

11. Contact Us

If you have questions or concerns about this Privacy Policy or our practices, please contact us: