PerchIQX

Appearance

Disclaimer ​

Effective Date: January 16, 2025 Last Updated: January 16, 2025

General Disclaimer ​

PerchIQX ("we", "us", or "our") provides database schema analysis tools and documentation for educational and professional use.

By using PerchIQX, you acknowledge and agree to the following disclaimers:

1. No Professional Advice ​

Not Database Administration Advice ​

PerchIQX provides automated analysis and recommendations, but:

  • We are not database administrators (DBAs)
  • We are not responsible for your database decisions
  • Recommendations are algorithmic suggestions, not expert consultation

You are solely responsible for:

  • Validating all SQL recommendations before execution
  • Understanding the impact of schema changes
  • Testing in non-production environments first
  • Maintaining proper database backups

Nothing on PerchIQX constitutes legal or compliance advice regarding:

  • Data protection regulations (GDPR, CCPA, etc.)
  • Industry-specific compliance (HIPAA, SOX, PCI-DSS)
  • Data retention policies

Consult qualified professionals for compliance requirements.

2. Database Risk ​

No Guaranteed Results ​

PerchIQX provides ICE-scored recommendations, but:

  • ❌ We cannot guarantee performance improvements
  • ❌ We are not responsible for data loss or corruption
  • ❌ We do not control your database environment or configuration

Database operations involve risk, including:

  • Schema migration failures
  • Production downtime
  • Data corruption
  • Query performance degradation
  • Unexpected side effects

Use at Your Own Risk ​

By using PerchIQX:

  • You accept full responsibility for database changes
  • You acknowledge that recommendations are opinions, not guarantees
  • You understand that testing is mandatory before production deployment
  • You will maintain proper backups before executing changes

Always follow the deployment safety pattern:

Development → Staging → Production
    ↓           ↓           ↓
  Test       Validate    Deploy

3. Data Accuracy ​

Third-Party Data Sources ​

PerchIQX integrates with:

  • Cloudflare D1 API (primary data source)
  • Your database schema metadata
  • SQLite introspection queries

We do not guarantee:

  • ✅ Data accuracy or completeness
  • ✅ Real-time schema synchronization
  • ✅ Availability of Cloudflare APIs
  • ✅ Absence of errors or bugs

Statistical Analysis ​

Our tools use:

  • ICE scoring methodology (Insight × Context × Execution)
  • Observable schema properties
  • Heuristic pattern detection

These are:

  • Analytical, not deterministic
  • Opinionated, based on design decisions
  • Subject to error, as with all software

Always verify critical recommendations with:

  • EXPLAIN QUERY PLAN for performance claims
  • Test queries in staging environments
  • Manual review of generated DDL statements

4. No Affiliation with Cloudflare ​

PerchIQX is not affiliated with, endorsed by, or sponsored by:

  • Cloudflare, Inc.
  • Cloudflare D1 team
  • Anthropic (Claude AI) or OpenAI
  • Any database vendors or service providers

PerchIQX is an independent, open-source project created for the developer community.

5. Software Disclaimer ​

Open Source License ​

PerchIQX is released under the MIT License and provided "AS IS" without warranties of any kind.

We do not guarantee:

  • ❌ Bug-free operation
  • ❌ Compatibility with your environment
  • ❌ Security or data protection
  • ❌ Continued maintenance or support
  • ❌ Backward compatibility across versions

Use Responsibly ​

When using PerchIQX:

  • Secure your credentials: Protect your Cloudflare API tokens
  • Respect rate limits: Don't abuse D1 APIs
  • Test thoroughly: Validate all recommendations in dev/staging
  • Maintain backups: Before any schema modifications
  • Review generated SQL: Don't blindly execute DDL statements

6. User Responsibility ​

Database Management Decisions ​

You are responsible for:

  • ✅ Understanding your database schema and dependencies
  • ✅ Testing schema changes in isolated environments
  • ✅ Maintaining database backups and disaster recovery plans
  • ✅ Monitoring performance after optimizations
  • ✅ Complying with your organization's change management policies

PerchIQX cannot account for:

  • Custom application logic dependent on schema structure
  • Database triggers, views, or stored procedures
  • External systems integrated with your database
  • Organization-specific naming conventions or standards

Cloudflare D1 Limits ​

You must understand and comply with:

PerchIQX recommendations may exceed D1 limits in some cases (e.g., large migrations). You are responsible for:

  • Breaking large migrations into smaller batches
  • Monitoring resource usage
  • Upgrading Cloudflare plans if needed

7. Limitation of Liability ​

To the maximum extent permitted by law:

PerchIQX and its contributors are NOT liable for:

  • Data loss, corruption, or deletion
  • Production downtime or service interruptions
  • Incorrect recommendations or analysis errors
  • Failed migrations or schema changes
  • Performance degradation
  • Security breaches
  • Financial losses
  • Consequential, incidental, or punitive damages

Your use of PerchIQX is at your sole risk.

Critical Warning ​

⚠️ NEVER execute schema changes directly in production without thorough testing.

Schema migrations can:

  • Lock tables and cause downtime
  • Break existing application code
  • Corrupt data if rolled back improperly
  • Exceed database resource limits

Best Practice Checklist:

  • [ ] Backup database before migration
  • [ ] Test in development environment
  • [ ] Validate in staging with production-like data
  • [ ] Review all generated DDL statements
  • [ ] Have rollback plan ready
  • [ ] Monitor after deployment
  • [ ] Execute during maintenance windows

8. Experimental Features ​

Some PerchIQX features may be marked as:

  • Experimental - Under active development
  • Beta - Testing phase, may change
  • Preview - Early access, feedback welcome

Experimental features:

  • May produce incorrect results
  • May change without notice
  • Should not be relied upon for production decisions
  • Are provided for evaluation and feedback only

Always check feature stability status before relying on recommendations.

9. Security Considerations ​

Local Execution ​

PerchIQX MCP server runs locally on your machine, not in the cloud.

Security implications:

  • Your Cloudflare API tokens are stored locally (never transmitted to PerchIQX servers)
  • Schema data is analyzed locally (we don't see your database structure)
  • SQL recommendations are generated client-side

API Token Security ​

You are responsible for:

  • Keeping Cloudflare API tokens confidential
  • Not committing tokens to version control (use .env files)
  • Rotating tokens if compromised
  • Following Cloudflare's security best practices

PerchIQX cannot protect you from:

  • Token exposure through insecure storage
  • Social engineering attacks
  • Compromised development environments

10. Changes to This Disclaimer ​

We may update this Disclaimer from time to time. Changes will be posted on this page with an updated "Last Updated" date.

Continued use of PerchIQX after changes constitutes acceptance of the updated Disclaimer.

11. Severability ​

If any provision of this Disclaimer is found to be unenforceable, the remaining provisions will remain in full effect.

12. Contact ​

Questions or concerns about this Disclaimer?

Final Word: PerchIQX is built with care for database intelligence and AI-native development. We want to help you optimize your database, but the ultimate responsibility for schema changes rests with you.

Use these tools as decision support, not decision replacement.

Test thoroughly. Deploy carefully. Monitor actively.

Deep Insights. Database Intelligence. Your Responsibility. 🗄️