• Pricing
Sign inStart free
Start free
Effective
May 16, 2026
Last updated
October 12, 2026

Report a vulnerability

security@ortely.com

We acknowledge within 3 business days.

security.txt

Contents
  • 1. Purpose
  • 2. Scope of systems
  • 3. Scope of vulnerabilities
  • 4. How to submit
  • 5. Your expectations of us
  • 6. Safe harbor
  • 7. Changes
  • Contact

Responsible Disclosure Policy

Effective date: May 16, 2026Last updated: October 12, 2026

Report a vulnerability

security@ortely.com

We acknowledge within 3 business days.

security.txt

Ortely values the work of independent security researchers. This policy explains how to report a vulnerability you find in Ortely's systems and what you can expect in return.


1. Purpose

Ortely commits to:

  • Acknowledge your report within 3 business days
  • Investigate every good-faith report
  • Keep you updated on the status as we fix the issue
  • Recognize your contribution (with your permission) once the fix is deployed

In exchange, we ask you to follow the guidelines below.


2. Scope of systems

This policy covers:

  • ortely.com and all subdomains operated by Ortely
  • The Ortely web application
  • The Ortely API
  • Customer subdomain tenants on *.ortely.com
  • Cloudflare Turnstile integration on the Ortely signup form
  • /.well-known/security.txt and adjacent metadata endpoints

This policy does not cover:

  • Third-party services Ortely uses (Anthropic, Stripe, Railway, Neon, Resend, Cloudflare, OpenCage, Deepgram) — please report vulnerabilities in those services to those vendors' own programs
  • Social engineering of Ortely staff or customers
  • Physical attacks against Ortely facilities or its sub-processors
  • Customer-managed tenant configurations (each customer is responsible for their own users, RBAC, and integrations)

3. Scope of vulnerabilities

We are most interested in:

  • Authentication and authorization issues (account takeover, privilege escalation, tenant boundary crossing)
  • Server-side request forgery, command injection, SQL injection
  • Cross-site scripting (XSS), CSRF, clickjacking with real-world impact
  • Exposed credentials, tokens, or sensitive data
  • Business-logic issues that allow bypassing payment, quotas, or access controls
  • AI safety issues (prompt-injection escalation that lets an attacker exfiltrate other-tenant data, manipulate billing, or compromise the platform)

We are less interested in (typically out of scope or low priority):

  • Missing security headers without a demonstrated exploit
  • Rate-limit gaps on unauthenticated public endpoints
  • Denial-of-service or volumetric attacks
  • Self-XSS that requires the victim to paste attacker content into their own console
  • Reports based solely on outdated software versions without a working PoC
  • Reports from automated scanners without manual validation
  • Open redirects without a chained vulnerability
  • Email-spoofing reports against domains without DMARC enforcement
  • Clickjacking on pages without sensitive actions
  • Social engineering, phishing, vishing
  • Issues in third-party libraries already patched but pending our update window

4. How to submit

Email security@ortely.com with:

  • A description of the vulnerability and where you found it
  • Steps to reproduce, ideally with a proof-of-concept
  • The impact: what an attacker could do with this
  • Your name or handle (for credit; pseudonyms are fine)
  • A PGP key if you'd like an encrypted reply (we'll publish a key at /.well-known/security.txt once we have one to publish)

We acknowledge within 3 business days. If you do not hear back, the email may have been filtered; please try again or contact support@ortely.com referencing the original message.


5. Your expectations of us

When you report responsibly we will:

  • Acknowledge receipt within 3 business days
  • Triage and update you within 10 business days
  • Coordinate disclosure timing with you. We default to disclosure after the fix is deployed across all customer tenants
  • Credit you publicly on Ortely's security page (with your permission)
  • Not take legal action for good-faith research that follows this policy

We do not currently pay bounties. A paid bug bounty program may follow. Reports submitted under this policy may be eligible for retroactive credit if a paid program launches.


6. Safe harbor

If you make a good faith effort to research and disclose vulnerabilities in accordance with this policy, Ortely will not pursue legal action against you for your research or responsible disclosure.

"Good faith" means you:

  • Identify vulnerabilities without accessing, modifying, or destroying customer data beyond what's necessary to demonstrate the issue
  • Do not exfiltrate data; if you stumble across customer data, stop and report
  • Do not perform denial-of-service, brute force, or load tests against production
  • Do not pivot from one finding to attack other systems
  • Do not socially engineer or phish Ortely staff, customers, or sub-processors
  • Comply with applicable law

If you have any doubt whether your activity is in scope, email security@ortely.com and ask before testing.

This safe harbor does not protect you from third-party claims (e.g., a customer's own claim if you accessed their tenant), so please err on the side of caution and stop as soon as you have proof of a vulnerability.


7. Changes

Ortely may update this policy. The "Last updated" date at the top reflects the most recent revision. Material changes will be summarized in the change log on this page.


Contact

  • Vulnerability reports: security@ortely.com
  • General security questions: security@ortely.com
  • Customer support: support@ortely.com
Ortely

AI-first freight software for forwarders, freight brokers, cargo GSAs and logistics teams.

hello@ortely.com
Product
Product overviewWhat our AI doesAgentsSOPsPricing
Solutions
For freight forwardersFor freight brokersFor cargo GSAsFor logistics teamsFor air carriersIntegrations
Resources
Help centerGet startedWhat's newBlogSecurity
Company
AboutPartner with usAccessibilitySitemap
Legal
DPACookiesAcceptable useSub-processorsResponsible disclosureAI actions
© 2026 Ortely. All rights reserved.
Terms|Privacy
Signing you in…