Please wait while we prepare your content.
Last Updated:
Effective Date: October 27, 2025
Jurisdiction: State of Arkansas, United States
This policy governs how BookGur monitors, limits, and enforces fair use of its systems, AI generation tools, storage resources, and automation features. The purpose is to maintain stability, ensure equitable access, and prevent technical or financial harm to the platform and its community.
BookGur supports active professional use, including high-volume creative projects, but must prevent resource monopolization, automated abuse, and misuse of platform features. This policy ensures that all users receive consistent performance while discouraging excessive or malicious activity.
Usage thresholds are dynamically scaled based on account type, current system load, and subscription tier. Examples include (values illustrative only):
BookGur may adjust these thresholds at any time to maintain operational integrity. Users consistently exceeding limits may be flagged for review.
BookGur automatically monitors:
Monitoring is conducted for system security and optimization, not content surveillance.
Depending on severity and pattern, BookGur may apply:
Temporary slowdown or queueing of requests until usage normalizes.
Immediate suspension of specific actions (e.g., AI generations, uploads, or exports) for a defined cooldown period.
Automatic review when a user repeatedly triggers throttles beyond acceptable tolerance.
Persistent overuse may lead to rate-limited API access, higher-tier plan requirement, or manual approval for future expansions.
| Type | Description | Action |
|---|---|---|
| Resource Abuse | Excessive automated usage or intentional system load testing | Throttling, warning, or suspension |
| Quota Circumvention | Use of multiple accounts or proxies to bypass limits | Account termination and data review |
| Unauthorized Automation | Bots or scripts generating or exporting content without proper authentication | API revocation and permanent ban |
| Data Extraction | Scraping of metadata, manuscripts, or assets for resale | Immediate termination and legal action |
| Financial Manipulation | Attempts to exploit billing, tokens, or refund systems | Account freeze, investigation, and restitution demand |
Users will be notified when throttling occurs except in cases of clear abuse or imminent system risk. Notifications may include cooldown periods, upgrade suggestions, or contact instructions for review. For severe violations, accounts may be disabled without prior notice if continued use would damage infrastructure or violate law.
If you believe your account was throttled or suspended in error:
Repeated appeals without new evidence may be dismissed.
Accounts exhibiting repeated or egregious abuse may face:
BookGur reserves the right to pursue civil or criminal remedies for deliberate misuse or attacks against its systems.
BookGur may employ automated tools including:
These measures operate to protect infrastructure and are not subject to user override.
Usage and throttle logs are retained for operational and security purposes.
Access to logs is restricted to authorized system administrators and compliance staff.
High usage that is legitimate, authorized, and within the bounds of paid service plans will never result in penalty. Users engaged in commercial or enterprise activity may request expanded limits through written authorization. BookGur supports creative projects, bulk publishing, and heavy AI experimentation provided activity remains lawful and system-friendly.
This policy functions as a component of the BookGur Terms and Conditions. Violations may result in account action independent of other policies. BookGur maintains sole discretion in interpreting "high usage" or "abuse" and enforcing appropriate measures.
This policy may be revised periodically to reflect system capabilities, technology evolution, or updated law. Users will be considered to have accepted changes upon continued use after an update.
By using BookGur, you acknowledge that the platform may impose throttles, limits, or suspensions to preserve stability and fairness and that these actions do not constitute a breach of service or entitle you to compensation.
Effective Date: October 27, 2025
Jurisdiction: State of Arkansas, United States
This appendix establishes the process for detecting, documenting, investigating, and resolving incidents of excessive use, throttling, automation abuse, or other forms of system misuse on the BookGur platform. All incidents must be documented with sufficient detail to support internal review or external legal inquiry.
To maintain system integrity, protect fair use, and provide a defensible audit trail for all enforcement actions taken under the High Usage, Throttling, and Abuse Policy. All incidents must be documented with sufficient detail to support internal review or external legal inquiry.
| Category | Description | Examples |
|---|---|---|
| A. Performance Load | Activity causing abnormal strain on infrastructure | Excessive AI generations, continuous uploads, mass exports |
| B. Automation Abuse | Unapproved scripting or API exploitation | Bot traffic, token farming, macro loops |
| C. Data Misuse | Unauthorized extraction or distribution of data | Scraping user content, copying system metadata |
| D. Account Manipulation | Quota circumvention or impersonation | Multiple accounts to bypass limits, fake identities |
| E. Financial Exploitation | Attempts to game billing or token systems | Refund abuse, false transactions |
| F. Malicious Intent | Direct attacks or willful damage | DDoS attempts, injection payloads, tampering with security |
Each incident log entry must contain the following core fields:
| Field | Definition |
|---|---|
| Incident ID | Unique sequential identifier generated automatically |
| Date and Time | UTC timestamp of first detection |
| User Identifier | Account ID or API key involved |
| IP / Endpoint | Source address or route signature |
| Trigger Type | Automated alert, manual flag, or external report |
| Category Code | A–F classification from Section 2 |
| Summary Description | Concise factual explanation of event |
| Detected By | System module, service, or staff member responsible for detection |
| Initial Severity Level | Minor, Moderate, Major, or Critical |
| Immediate Action Taken | Throttle, Warning, Suspension, Ban |
| Investigation Reviewer | Name or ID of assigned compliance officer |
| Final Determination | Confirmed Violation, False Positive, Under Appeal |
| Resolution Summary | Brief outcome notes including corrective steps |
| Retention Status | Scheduled purge date per policy (90 days, 1 year, etc.) |
| Severity | Definition | Response Window |
|---|---|---|
| Minor | Low impact or accidental trigger | Within 48 hours |
| Moderate | Persistent overuse or clear violation without harm | Within 24 hours |
| Major | Patterned abuse or deliberate circumvention | Immediate review within 12 hours |
| Critical | Security threat or criminal behavior | Immediate containment and escalation to executive oversight |
All retained data must be encrypted and stored separately from production systems. Access is restricted to security, compliance, and executive staff on a need-to-know basis.
Each account accumulates an Incident Score derived from severity and frequency. Thresholds triggering permanent restrictions:
These triggers initiate permanent account closure and blacklisting of associated payment methods and IP ranges.
This appendix is reviewed annually or following any significant legal, security, or operational update. Changes take effect immediately upon adoption by BookGur's compliance division.
BookGur retains exclusive authority to interpret, modify, and enforce this policy. Decisions made under this appendix are final and not subject to external arbitration beyond what is outlined in BookGur's general Terms and Conditions.
Effective Date: October 27, 2025
Jurisdiction: State of Arkansas, United States
This appendix outlines the procedures for identifying, reporting, investigating, and mitigating security breaches and data incidents that may compromise the confidentiality, integrity, or availability of BookGur's systems, infrastructure, or user data.
BookGur is committed to maintaining a secure environment that protects user information, creative assets, and operational data. This policy establishes standardized procedures for:
| Term | Definition |
|---|---|
| Security Breach | Any unauthorized access to BookGur's digital systems or physical data assets that results in actual or potential compromise of confidential information. |
| Data Incident | Any event that threatens or disrupts system integrity, including but not limited to failed access attempts, malware infections, or service disruptions. |
| Personal Data | Any user-related information stored or processed by BookGur, including account credentials, project data, or metadata. |
| Containment | Actions taken to isolate affected systems, prevent escalation, and preserve evidence. |
| Remediation | Steps implemented to restore system integrity and prevent recurrence. |
| Level | Description | Examples |
|---|---|---|
| Low | No confirmed data exposure; minimal disruption | Suspicious login, automated scan, failed intrusion attempt |
| Moderate | Possible unauthorized access or temporary data loss | Limited database exposure, compromised user credentials |
| High | Confirmed data exfiltration or unauthorized disclosure | Access to user files, private metadata, or payment data |
| Critical | Large-scale data breach or system compromise with high risk to users | Database dump, ransomware, server root access, or data destruction |
Any employee, contractor, or user who suspects unauthorized access must immediately report the event to the Security or Compliance team.
The Security Response Team (SRT) performs an initial assessment to verify legitimacy, determine scope, and classify severity level.
Containment must begin within one (1) hour of confirmed detection for all Moderate, High, or Critical incidents.
All findings must be recorded in a formal incident report and assigned a unique Security Case ID.
Senior management, compliance, and affected system owners must be notified immediately upon confirmation.
If user data is affected, BookGur will notify impacted users promptly, providing:
Where legally required, BookGur will notify applicable data-protection authorities within the mandated timeframe (generally within 72 hours of confirmation).
Following containment and investigation:
A final remediation report must document each corrective measure and responsible personnel.
Public statements regarding breaches must be approved by senior leadership and legal counsel to ensure accuracy and regulatory compliance. Unauthorized disclosure of incident details by staff is prohibited and may result in termination.
Within 14 days of closure, the Security Response Team must conduct a Post-Incident Review (PIR) to evaluate:
Results feed directly into the Security Risk Register for continuous improvement.
This appendix will be reviewed annually or immediately following a major security event. It must remain aligned with emerging privacy laws, cybersecurity standards, and industry frameworks such as NIST CSF, ISO/IEC 27001, and applicable data protection acts.
All breach investigation data, internal communications, and forensic materials are confidential and protected as trade secrets of BookGur. Unauthorized access or distribution constitutes grounds for termination and may result in civil or criminal penalties.
The Chief Security Officer and Legal Affairs Division hold final authority for breach classification, disclosure decisions, and communication with regulators. All determinations made under this appendix are binding within the organization.