Pabble is built around a simple promise: unlimited forms, unlimited responses, no arbitrary caps. That promise is genuine and we intend to keep it. This Fair Use Policy exists not to walk it back, but to protect it. When a small number of accounts behave abusively, it degrades infrastructure for everyone. This policy describes what abusive behaviour looks like, how we detect it, and what happens when we find it.
1. What "Unlimited" Means
Both Hobby and Scale plans include unlimited form creation and unlimited response collection. There are no monthly submission quotas, no overage charges, and no surprise pauses when your forms get busy. You can publish a form and let it run without watching a counter.
The only hard limits on the platform are tied to file storage, which reflects real infrastructure cost: Hobby plans include 100 MB of cloud storage with a 20 MB per-file cap; Scale plans include 20 GB with a 200 MB per-file cap. Everything else is unlimited by design.
2. What This Policy Protects Against
Unlimited does not mean unmonitored. The following patterns undermine platform integrity regardless of plan tier and will be treated as abuse:
Bot-Generated Submissions
Using automated scripts, bots, or programmatic tools to flood your own forms or another user's forms with fake submissions is prohibited. This includes:
- Running bots to stress-test submission volume against our infrastructure without prior written consent.
- Inflating response counts to manipulate analytics or misrepresent engagement.
- Submitting forms on behalf of individuals who did not initiate or consent to the submission.
Spam and Unsolicited Outreach via Flow Automations
The Flow Builder is designed to automate meaningful follow-ups based on genuine form submissions. It is not a broadcast channel. The following uses are prohibited:
- Sending bulk email to lists of contacts who have not submitted a form or otherwise opted in to receive communication from you.
- Constructing self-triggering or circular flow automations that execute indefinitely without a valid respondent action at the origin.
- Using flow-triggered emails to send phishing content, malware links, or deceptive messages to respondents.
Storage Misuse
File upload fields exist to collect attachments from respondents, not to serve as general-purpose cloud storage. The following are outside the intended scope of the Service:
- Using Pabble as a file host or CDN for assets unrelated to form data collection.
- Uploading files containing malware, exploits, or prohibited content.
- Circumventing per-file size limits through compression, splitting, or encoding tricks.
Deceptive and Harmful Forms
The platform must not be used to deceive or harm the people who fill your forms. Specifically prohibited:
- Forms that impersonate another company, organisation, or individual to extract credentials or sensitive data.
- Forms that collect personal information under false pretences without disclosing the actual use.
- Forms targeting minors to collect data without verifiable parental consent.
- Forms designed to harvest payment card details, social security numbers, or equivalent sensitive data outside a compliant, regulated context.
Infrastructure Attacks
Any attempt to interfere with the availability, integrity, or performance of the platform is treated as an attack regardless of intent. This includes probing for vulnerabilities, load testing without prior written approval, attempting to access data belonging to other accounts, or exploiting bugs rather than reporting them responsibly. To report a security issue or request approval for authorised testing, contact us at harshkanjiya001@gmail.com.
3. How We Detect Abuse
Our systems monitor submission patterns, automation execution rates, storage access behaviour, and account activity in real time. Signals that commonly indicate abuse include:
- Sudden spikes in submission volume from non-human traffic patterns.
- Identical or near-identical submissions at machine-speed intervals.
- Automation flows executing at rates inconsistent with genuine human form submissions.
- Uploaded files flagged by our malware scanning pipeline.
- Multiple accounts sharing infrastructure indicators and exhibiting coordinated behaviour.
We do not read the content of your forms or responses unless specifically required to investigate a reported abuse complaint or a legal obligation.
4. Consequences of Abuse
We aim to give accounts a chance to correct behaviour before taking permanent action. The typical escalation is:
- Warning: an email notification explaining what was detected and what needs to change. Most cases end here.
- Feature restriction: if a specific capability is being abused, it may be disabled for your account while the rest of the Service remains accessible.
- Account suspension: continued or escalating violations result in full account suspension. You will be given a window to export your data before it is purged.
- Permanent ban: accounts involved in fraud, coordinated attacks, or illegal activity will be permanently banned with no restoration path. In serious cases we reserve the right to share relevant information with law enforcement.
We reserve the right to skip to suspension or a permanent ban without prior warning when the abuse is severe, ongoing, or poses an immediate risk to the platform or to other users.
5. Appeals
If you believe your account was actioned in error, email harshkanjiya001@gmail.com with the subject line "Fair Use Appeal" and a description of your use case. We review every appeal and respond within 5 business days. We take false positives seriously and will reverse actions that were made in error.
6. Updates to This Policy
As the platform evolves and new abuse patterns emerge, this policy will be updated to reflect them. Changes will be communicated via email and in-app notice before taking effect.