Security

Security matters to us both as a technology company and as a partner handling automation and integration work for our clients. This page summarizes how we approach security for www.cubicflows.com and, at a high level, for client engagements.

1. Website Infrastructure

This Site is hosted on Cloudflare's global network, which provides:

• HTTPS/TLS encryption for all traffic between your browser and the Site;
• DDoS protection and web application security at the network edge;
• A static-site architecture with no application database directly exposed to the internet.

2. Data We Handle on This Site

The Site does not process payment card information, and it does not require visitors to create an account or log in. The only personal information collected through the Site is what you voluntarily submit via our contact form (name, email, industry, and message). See our Privacy Policy for details on how that information is used.

Results from the Automation Assessment tool are stored only in your browser's local session storage and are never transmitted to our servers unless you choose to include them in a contact form submission.

3. Client Engagement Security

[MAN&Cubs LLC: complete this section with your actual practices — for example, how client credentials and API keys are stored during integration projects, whether access follows least-privilege principles, how client data is segregated between engagements, and any relevant certifications or frameworks you follow.]

4. Vulnerability Reporting

If you believe you've found a security vulnerability affecting this Site or our services, please report it to [email protected]. Please include enough detail for us to reproduce the issue, and avoid accessing, modifying, or deleting data that isn't yours in the course of testing. We will acknowledge reports in a reasonable timeframe. [MAN&Cubs LLC: add a formal responsible-disclosure policy or bug bounty program here if one is established.]

5. Incident Response

[MAN&Cubs LLC: describe your incident response process — e.g., how affected clients or users would be notified in the event of a data incident, and expected timelines.]

6. Changes to This Page

We may update this page as our practices evolve. Material changes will be reflected by updating the effective date at the top of this page.

7. Contact Us

Security questions can be sent to [email protected].