Overview
We operate the platform our customers use to sell, get paid, and serve their own customers. This page summarizes how we protect it.
Practices aligned with recognized frameworks
Our security and privacy practices are aligned with the GDPR and CCPA frameworks. Card payments are processed by a PCI DSS certified provider: card data never touches our servers.
Encryption in transit and at rest
Every connection uses TLS. Stored data and backups are kept encrypted.
Continuous monitoring
We watch our infrastructure continuously, with centralized event logging and alerts so we can detect and respond in time.
Backups with off-site replication
Periodic backups replicated to a separate location, with restore testing, so operations can be recovered after any incident.
Data we process
Transparency about what data flows through our platform — and what does not.
| Data type | Do we process it? | Detail |
|---|---|---|
| Personal data of customers and employees | Yes | What is needed to operate the contracted services (accounts, contacts, business operations). |
| Payment card data | No | Payments are processed directly in the environment of our PCI DSS certified payment provider. Our servers never receive or store card numbers. |
| Health data | No | Our platform is not designed for health data and we do not process it. |
Documentation on request
Security policy, incident response plan, continuity plan, and penetration test summary, available to customers and evaluators.
View resources →Controls by category
Infrastructure, organization, product, internal procedures, and data & privacy.
View controls →Third parties that support us
The short, verifiable list of providers involved in operating the platform.
View subprocessors →Resources
Our security documentation is available to customers and to teams evaluating us. If you have a sajet.us account, click “Request” on the document and we will email the download link to your account address; the copy carries a delivery mark tied to your account. If you don't have an account, request it at [email protected]. The penetration test summary is shared under a non-disclosure agreement (NDA).
Information Security Policy
How we govern security: responsibilities, access, encryption, backups, and change management.
Incident Response Plan
How we detect, contain, and resolve incidents, and how we notify affected customers.
Continuity & Recovery Plan
Backups, off-site replication, and the procedure to restore operations after a contingency.
Penetration Test Summary
Executive summary of our penetration testing and red team assessments: scope, methodology, and remediation status. Shared under NDA.
Controls
The controls we apply, organized by category. This is the same list we share in our security assessments.
Infrastructure
Organization
Product
Internal procedures
Data & privacy
Subprocessors
The third parties involved in operating the platform. Changes to this list are published on this page.
| Provider | Function | Location |
|---|---|---|
| Jeturing's own infrastructure | Platform hosting and operations | United States |
| Cloudflare | Content delivery network and perimeter security | Global |
| PCI DSS certified payment processing provider | Card payment processing | United States |
| Microsoft 365 | Corporate email and productivity tools | United States |
Frequently asked questions
Straight answers to what evaluating teams ask us most.
Product
What does this trust center include?
A public summary of our security and privacy practices, our controls by category, the list of subprocessors, and the way to request full documentation and to report vulnerabilities.
How do I get the full security documentation?
From the Resources section: if you have a sajet.us account, click "Request" on the document and we will email the download link to your account address. Without an account, request it at [email protected]. We share the security policy, the incident response plan, the continuity plan, and the penetration test summary; the latter requires accepting a non-disclosure agreement (NDA) before receiving the link.
Security & compliance
Are you SOC 2 or ISO 27001 certified?
No: we do not hold those certifications and we do not advertise them. Our practices are aligned with recognized frameworks such as GDPR and CCPA, and payment processing is performed by a PCI DSS certified provider. We would rather show you our real practices and documentation than a badge we do not have.
How are card payments processed?
They are processed directly by our payment provider, which is PCI DSS certified. Card data never reaches our servers: we do not receive it, transmit it, or store it.
Do you run penetration tests?
Yes. We run periodic penetration tests and red team exercises against our own infrastructure. The executive summary is available on request under a non-disclosure agreement.
How do you notify customers of a security incident?
We have a documented response plan: detect, contain, resolve, and notify affected customers without undue delay, with the information available at each moment.
Data & privacy
Where is data hosted?
On our infrastructure in the United States, with encryption in transit (TLS) and at rest, and backups with off-site replication.
What happens to my data if I cancel the service?
When the relationship ends, customer data is deleted from our systems after the applicable retention period. You can request deletion by writing to [email protected].
Do you sell or share my data for advertising?
No. We process data only to provide the contracted service and with the subprocessors listed on this page.
Report a vulnerability
If you found a security issue in our products or infrastructure, we want to know. We practice responsible disclosure: good-faith reporters face no consequences for reporting.
Channel
Write to [email protected] with the subject "Vulnerability report". If your report contains sensitive information, ask for an encrypted channel in that same email first.
What to include
- Affected product or URL.
- A clear description of the issue.
- Steps to reproduce it.
- The impact you estimate.
- Evidence: screenshots, logs, or a minimal proof of concept.
What to expect
- Acknowledgement of receipt from our team.
- Assessment and risk classification.
- Remediation prioritized by impact.
- Public recognition if you wish and the report is valid.
Good-faith rules
- Do not access or modify third-party data.
- Do not interrupt the service or degrade its availability.
- Stop testing as soon as you have demonstrated the issue.
- Give us reasonable time to fix it before disclosing.