How ArtisanClo protects your campaigns, access, and data.
This page describes the technical safeguards, access controls, and monitoring we use to protect ArtisanClo.
We focus on real safeguards: transport encryption, request validation, isolated databases, monitoring, and team seat controls.
Security controls are built into our dashboard, decision API, database isolation, staff access controls, and server workflows.
We maintain risk-based safeguards designed to prevent unauthorized access, keep response times fast, and keep data private.
We protect the server infrastructure and APIs; you manage your team's credentials, 2FA keys, and permissions.
The core principles behind our security architecture
Several layers work together: transport encryption, API key validation, rate limits, isolated environments, and active logging.
Internal admin permissions are limited to the authorized staff who need them for maintenance and support.
We regularly audit dependencies, patch software, and refine our filters to defend against new web threats.
A detailed look at our current safeguards
Application & API Security
Our platform uses strict input validation, access control checks, and secure session management to guard against common web vulnerabilities.
Decision API endpoints use signed requests, secret tokens, timestamp validation, and rate limiting to prevent replay and brute-force attacks.
We keep tuning our security logic to block malformed requests without adding latency for real users.
Infrastructure & Environment Security
Our cloud infrastructure runs in top-tier data centers worldwide, with built-in network firewalls, DDoS protection, and automated health checks.
Production databases and customer workspaces are logically isolated. Direct administrative access is limited to key staff over encrypted connections.
Staging and development environments are kept strictly separate from live production traffic, so bugs found in testing can't affect performance.
Encryption & Log Safeguards
In production, all web traffic and decision API calls are encrypted in transit with HTTPS/TLS.
Sensitive values in traffic logs, such as visitor IP addresses, are automatically masked or hashed, so standard reports don't expose raw IP lists.
We recommend keeping sensitive personal details out of flow rule notes and campaign descriptions as much as possible.
Account Access & Team Security
You are responsible for keeping your team's account passwords, 2FA keys, and API tokens safe.
If a team member leaves or an API token is exposed, rotate your keys right away in your dashboard settings.
Use roles from the role builder to give employees only the access level they need.
Monitoring & Incident Response
We monitor system latency, error spikes, and unusual API request patterns around the clock.
In the rare event of a security issue, our team contains it, isolates the affected parts, and quickly restores normal service.
If a security incident affects your account, we will promptly notify you by email or with a dashboard alert, with clear details.
Third-Party Service Providers
We use trusted cloud vendors for server hosting, payment processing, email delivery, and analytics.
We choose vendors for their reliability, technical excellence, and strict data security standards.
Customer traffic data processed on external infrastructure remains subject to our security guidelines.
Security Disclaimer & Responsibilities
We use multiple layers of safeguards, but no internet platform can promise 100% protection from every threat.
This page describes our standard operational practices and is not a contractual SLA.
You remain responsible for choosing strong passwords, keeping your own devices secure, and setting up appropriate flow rules.
Security events you should report to us
If you find a security issue or notice activity on your account you don't recognize, message support right away.
Security is an ongoing commitment
We regularly update our security practices as new web threats emerge and the platform changes.
Continued use of ArtisanClo after an update means you acknowledge the revised Security page. If you do not agree with the updated version, you should stop using the service and close your account in accordance with the applicable Terms.