Privacy Policy

Account data: When you register, we collect your email address, a hashed password (we never store the plaintext), and an optional display name.

Usage data: We record the number of simulation runs consumed per month to enforce tier quotas. This is a counter — not a log of your simulation inputs or results.

Model data: Reliability block diagrams, component types, simulation results, and templates you create are stored in our database and associated with your account. This data belongs to you.

Payment data: If you subscribe to a paid plan, Stripe collects and processes your payment details. We receive only a subscription status and customer ID — we never see or store card numbers.

Log data: Our servers log standard request metadata (IP address, browser type, pages visited, response codes) for security and operational diagnostics. Logs are retained for 30 days.

Emails you send us: If you contact us at hello@ramly.io or sales@ramly.io, we store the content of your message to respond to you. We do not use inbound emails for marketing.

We use your data to:

• Provide, operate, and improve the Ramly service
• Enforce usage quotas and tier limits
• Send transactional emails (email verification, password reset, trial lifecycle notices) — not marketing without your explicit consent
• Respond to support and sales enquiries
• Detect and prevent fraud, abuse, and security incidents
• Comply with legal obligations

We do not sell your personal data to third parties. We do not use your model data to train machine learning models.

We use the following third-party processors. Each operates under its own privacy policy:

• Railway (hosting): Our application and database run on Railway's infrastructure in the us-east-1 region (AWS). Your data is stored in the United States. Railway Privacy Policy
• Stripe (payments): Stripe processes subscription payments. We do not store card details. Stripe is PCI-DSS certified. Stripe Privacy Policy
• Resend (transactional email): Outbound emails (verification, password reset, trial notices) are sent via Resend. Your email address is shared with Resend solely for delivery. Resend Privacy Policy

We use a single session cookie (ram_session) to keep you signed in. This cookie is HttpOnly, SameSite=Lax, and expires after 30 days of inactivity. We do not use advertising or tracking cookies.

Your account data is retained for as long as your account is active. Model data (RBDs, simulation results) is retained until you delete it or your account is closed.

Server logs are purged after 30 days. Expired sessions are deleted automatically.

If you close your account, we will delete your personal data within 30 days, except where retention is required by law.

Depending on your jurisdiction, you may have rights to:

• Access the personal data we hold about you
• Correct inaccurate data
• Request deletion of your data ("right to erasure")
• Export your model data in JSON format
• Object to certain processing activities
• Withdraw consent where processing is based on consent

To exercise any of these rights, contact us at the address below. We will respond within 30 days.

Passwords are hashed with bcrypt before storage. All data in transit is encrypted via TLS. Access to production systems is restricted to authorised personnel.

No system is perfectly secure. If you believe your account has been compromised, contact us immediately at security@ramly.io.

We may update this policy as the service evolves. We will notify registered users of material changes by email at least 14 days before they take effect. Continued use of the service after that date constitutes acceptance.

Privacy questions, data requests, or complaints: privacy@ramly.io

Ramly LLC, a limited liability company organised under the laws of the Commonwealth of Pennsylvania, USA.