Last updated: 2026-07-20 | Effective: 2026-07-20
Acceptable Use Policy
This policy defines acceptable and prohibited uses of DevStackIO tools and services. By using DevStackIO, you agree to comply with this policy.
Scope: This policy applies to all users of DevStackIO tools, website, API, and services. It supplements our Terms of Service and Privacy Policy. Violations may result in suspension or termination of access.
1. General Principles
DevStackIO provides free, browser-based developer tools for formatting, converting, generating, and analyzing data. Our tools process data entirely in your browser — nothing is uploaded to our servers. This architecture reflects our commitment to privacy and security.
By using DevStackIO, you agree to use our tools responsibly, ethically, and in compliance with all applicable laws and this policy.
Core Principles
- Lawful Use: Use tools only for lawful purposes.
- Respect Privacy: Do not process others' private data without consent.
- No Harm: Do not use tools to create, facilitate, or distribute harmful content.
- Respect Resources: Do not abuse, overload, or attempt to circumvent our infrastructure.
- Attribution: Respect intellectual property rights and licensing requirements.
2. Prohibited Activities
The following activities are strictly prohibited:
2.1 Illegal Activities
- Processing, generating, or facilitating illegal content, activities, or instructions
- Generating code, configs, or data for malware, exploits, ransomware, or cyberattacks
- Creating tools for unauthorized access, privilege escalation, or data exfiltration
- Generating content for fraud, identity theft, phishing, or social engineering
- Processing data for sanctions evasion, money laundering, or terrorist financing
2.2 Harmful Content
- Generating content that promotes violence, self-harm, or terrorism
- Creating content that exploits minors or vulnerable populations
- Generating hate speech, harassment, or discriminatory content
- Creating deepfakes, impersonation content, or non-consensual intimate imagery
- Producing disinformation, election interference, or manipulation campaigns
2.3 Security Violations
- Attempting to reverse-engineer, decompile, or extract source code from our tools
- Probing, scanning, or testing our infrastructure for vulnerabilities without authorization
- Attempting to bypass rate limits, quotas, or access controls
- Injecting malicious code, scripts, or payloads into tool inputs
- Attempting to extract, exfiltrate, or access other users' data (architecturally impossible but prohibited)
2.4 Abuse and Overload
- Automated scraping, crawling, or bulk API calls without explicit permission
- Running tools in automated loops, bots, or scripts that degrade performance
- Distributed or coordinated usage to circumvent limits
- Using tools for cryptocurrency mining, password cracking, or resource-intensive brute forcing
- Intentional generation of malformed inputs to crash or freeze tools
2.5 Intellectual Property Violations
- Using tools to remove copyright notices, watermarks, or attribution
- Generating content that infringes patents, trademarks, trade secrets, or copyrights
- Removing license headers, copyright notices, or SPDX identifiers from generated code
- Using tools to circumvent DRM, license checks, or copy protection
2.6 Privacy Violations
- Processing personal data without lawful basis or consent (GDPR Art. 6)
- Inputting others' private data (PII, credentials, keys, tokens) into tools
- Using tools to de-anonymize, re-identify, or link anonymous data
- Generating synthetic PII that resembles real individuals
3. Tool-Specific Restrictions
Certain tool categories have additional restrictions:
Security & Cryptography Tools
- Do not use for generating production secrets without proper entropy review
- Do not use generated keys/certs in production without independent validation
- JWT tools: Do not use for token forging, privilege escalation, or bypassing auth
- Hash tools: Do not use for password cracking, rainbow tables, or credential stuffing
Network & Infrastructure Tools
- DNS/IP tools: Do not use for reconnaissance, enumeration, or attack planning
- Certificate tools: Do not use for MITM, spoofing, or impersonation
- Subnet/IP tools: Do not use for network scanning or unauthorized access planning
Encoding/Decoding & Data Tools
- Base64/URL/HTML tools: Do not use for obfuscating malicious payloads
- Data converters: Do not use for data exfiltration formatting
- Binary/hex tools: Do not use for shellcode generation or exploit development
Generators (UUID, Password, QR, etc.)
- Do not generate credentials for unauthorized access
- QR codes: Do not encode malicious URLs, phishing links, or exploit payloads
- Password generator: Use for legitimate account security only
Formatters & Validators
- Do not use for formatting obfuscated malware code
- SQL formatter: Do not use for SQL injection payload formatting
- Regex tester: Do not use for ReDoS pattern development
4. API Usage (Current and Future)
DevStackIO currently provides a web interface. If/when a public API is released, the following will apply in addition to this policy:
Rate Limits
Respect published rate limits. Do not circumvent via multiple keys, IPs, or accounts.
Authentication
Use only your own API keys. Do not share, sell, or transfer keys.
Data Handling
Do not submit PII, secrets, or confidential data via API unless explicitly supported.
Attribution
Display "Powered by DevStackIO" or equivalent attribution in API-driven applications.
A separate API Terms of Service will govern API access upon release.
5. Security and Integrity
5.1 Vulnerability Disclosure
We encourage responsible security research. If you discover a vulnerability, please report it via:
Email: contact@devstackio.com
PGP: Available on request
We commit to acknowledging reports within 48 hours and providing a timeline for remediation. Do not publicly disclose vulnerabilities before a fix is deployed.
5.2 No Warranty on Security
While we implement strong security measures (CSP, HSTS, SRI, client-side architecture), no system is completely secure. You use tools at your own risk. Verify outputs independently for security-critical applications.
5.3 Client-Side Architecture
Our tools run entirely in your browser. This means:
- Your data never leaves your device (except for optional analytics with consent)
- We cannot access, monitor, or control your tool usage
- Security of your browser environment is your responsibility
- Keep your browser, OS, and extensions updated
6. Intellectual Property
DevStackIO name, logo, brand, website design, and tool implementations are our intellectual property. You retain all rights to your input data and tool outputs.
Permitted Uses
- Personal and commercial use of tools and outputs
- Incorporation of tool outputs into your projects, products, or services
- Sharing tool outputs with colleagues, clients, or in documentation
Restricted Uses
- Redistributing, reselling, or rebranding the DevStackIO tools themselves
- Creating derivative works of our tool implementations (not outputs)
- Using our brand, logo, or name to imply endorsement without permission
- Reverse engineering, decompiling, or extracting our source code
Open source components within our tools remain under their respective licenses (MIT, Apache-2.0, etc.). See individual tool credits for details.
7. User Conduct
7.1 Account-Free Usage
DevStackIO requires no account. This means we cannot enforce per-user bans. Instead, we may:
- Block abusive IP ranges or ASNs
- Implement CAPTCHA or proof-of-work challenges
- Rate limit by fingerprint or behavioral patterns
- Restrict access to specific tools or features
7.2 Shared Responsibility
If you share access to DevStackIO (e.g., in a team, classroom, or organization), you are responsible for all use under your session. Ensure all users comply with this policy.
7.3 Educational and Research Use
Academic, educational, and security research use is permitted and encouraged. When using tools for vulnerability research, malware analysis, or security education:
- Clearly label research outputs
- Do not test on production systems without authorization
- Follow responsible disclosure practices
- Cite DevStackIO as the tool source in publications
8. Enforcement and Consequences
We enforce this policy through technical measures and, where necessary, legal action:
Progressive Enforcement
- Warning: Automated notice for first minor violation
- Temporary Restriction: Rate limiting, CAPTCHA, or feature limits (24h-7d)
- Extended Restriction: IP/ASN blocking, feature suspension (7d-90d)
- Permanent Block: Persistent or severe violations
- Legal Action: For criminal activity, IP theft, or significant harm
Appeals
To appeal a restriction, contact contact@devstackio.comwith your IP, the restriction details, and explanation. We review appeals within 5 business days.
9. Reporting Violations
Help us keep DevStackIO safe. Report violations to:
Abuse/Security: contact@devstackio.com
Copyright/DMCA: contact@devstackio.com (see DMCA Policy)
General Policy: contact@devstackio.com
Security Issues: contact@devstackio.com (see Security Policy)
Include: Description of violation, URL/tool involved, screenshots if applicable, and your contact info. Anonymous reports accepted but may limit follow-up.
10. Changes to This Policy
We may update this Acceptable Use Policy from time to time. Changes will be posted on this page with an updated "Last updated" date. Material changes will be announced via:
- Website banner or notice
- Blog post or changelog entry
- Email to registered API users (when applicable)
Continued use of DevStackIO after changes constitutes acceptance. If you disagree with changes, you must cease using our services.
Related Documents
Contact
Questions about this Acceptable Use Policy? Contact us atcontact@devstackio.comor use our contact form.