edoro

Start Free 14-Day Trial
Document Directory
    Add a header to begin generating the table of contents
    Scroll to Top

    edoro Fair Use and Acceptable Product Policy

    EFFECTIVE DATE: JULY 01, 2026

    Policy Introduction

    At edoro, we are entirely committed to providing an exceptionally fast, highly reliable, and deeply flexible environment for your creative and production teams. Our utility-based sliding scale model, native third-party integration library, and agentic AI systems are designed to scale smoothly with your workflow demands.

    To protect the performance of our infrastructure, system velocity, and data security for all our partners, we maintain clear boundaries on how our software, servers, and processing engines may be used.

    This Fair Use and Acceptable Product Policy outlines our operational guardrails. While we always aim to handle workspace management cordially, edoro reserves the absolute right to enforce these rules firmly—including account blocking or permanent termination with no refunds or data recovery—to preserve the platform’s integrity.

    1. User Seats & Account Management (Our Advisory)

    • Our pricing model allows you to scale your team seat sliders exactly as your organization grows.
    • The Friendly Note on Seat Sharing: We strongly advise against sharing a single "Team Member" seat among multiple individuals via credential transfers, active session-mirroring tools, or custom dashboard configurations that route multiple workers through a single account.
    • Why It Matters: When multiple team members work out of a single seat, it disrupts edoro’s behavioral reporting layer. It skews your Value Realization Dashboard metrics, making it impossible to accurately track stage bottlenecks, user workload distribution, and true time-to-value.
    • Our Leniency Stance: To maintain maximum flexibility for your creative operations, we will not block accounts, suspend subscriptions, or penalize workspaces for seat sharing. While we choose leniency here, we strongly recommend assigning independent seats to keep your operational analytics accurate and pristine.

    2. Outbound System Email Misuse (The Communication Guard)

    • edoro provides high-speed, automated notification pipelines, custom proof invitations, and event-driven alerts at the review stage to keep your stakeholders aligned.
    • Prohibited Communication Blasts: Using edoro's automated outbound notification boxes or review invitation systems to send unsolicited cold sales outreach, mass marketing blasts, spam campaigns, or deceptive affiliate links is strictly prohibited.
    • Domain Reputation Protection: We closely monitor our shared mail-routing subdomains. Any workspace behavior that triggers an abnormally high bounce rate, invalid recipient errors, or spam complaints that threaten to land edoro on international email blacklists (such as Spamhaus or Barracuda) will result in an immediate and permanent block of your workspace email features.
    • Deceptive Content & Phishing: You may not use creative canvas description cards, markups, or comment threads to host phishing links, harvest user credentials, or trick internal or external reviewers into sharing sensitive structural data.

    3. Media Ingestion & Content Boundaries (The Storage Guard)

    • We built edoro to accommodate massive high-resolution files, complex video files, and comprehensive publication layouts. However, our storage system must be used responsibly.
    • Creative Intent Requirement: edoro's storage environment is optimized for active content orchestration, proofing, and publishing loops. Using our platform as an unmanaged, cold backup for non-project files or disconnected raw media archives violates the spirit of fair use.
    • Malicious File Ingestion: Uploading files embedded with viruses, trojans, tracking scripts, ransomware, or executable macros disguised within creative extensions (such as infected layout scripts buried in a zipped Adobe InDesign or LaTeX package) is an absolute security breach.
    • Severe Liability Content: You may not use edoro to upload, process, render, or distribute materials that constitute severe targeted harassment, hate speech, or systemic, industrial-scale media piracy. Any actions that expose our hosting infrastructure to severe legal liability or repeated, valid DMCA takedown actions will cause your workspace to be isolated immediately.

    4. Integration, Automated Engines, & Co-Pilot Exploits

    • edoro connects deeply with external clouds, custom typesetting engines, and preflight tools. We expect users to interact with these nodes within reasonable performance parameters.
    • Bring Your Own Storage (BYOS) Stability: If you connect external cloud storage buckets to your edoro workflow, you are responsible for ensuring they are correctly configured. Misconfigured external buckets that continuously hammer our servers with malformed API requests or corrupted sync loops will be detached automatically to maintain platform stability.
    • Typesetting Overload: Flooding our background automated typesetting engines (InDesign Server, TeX/LaTeX clusters) with deliberately corrupted scripts, endless recursive loops, or unoptimized data inputs designed to freeze or crash the rendering nodes is strictly prohibited.
    • File-Based Integration Abuse: Weaponizing connected external modules (such as automated preflighting nodes like PitStop, Asura, or Switch) to systematically push high-risk, unvetted, or destabilizing file structures into edoro’s optimization pipelines is banned.
    • Co-Pilot Flooding: Our plain-English, context-aware AI Co-Pilot window is built to empower administrators with clear operational answers. Deploying script bots or rapid-fire macros to artificially flood the AI database querying interface with thousands of simultaneous prompts will result in immediate suspension of AI features.

    5. Infrastructure Integrity & Reverse Engineering

    • Scraping & Mining: You may not deploy automated bots, scrapers, web spiders, or unauthorized API scripts to systematically extract edoro's underlying codebase, proprietary media compression algorithms, or system metadata layouts.
    • Rogue Vulnerability Probes: Running independent security penetration tests, stress tests, or high-volume load testing against edoro’s endpoints without the explicit, advance written authorization of our Technical Operations Director is a violation of our terms.
    • Exploit Exploitation: If your team discovers an operational bug, a system loophole, or a data glitch in our sliding-scale resource counters, you must report it to edoro support immediately. Weaponizing a zero-day layout exploit to gain free resources or bypass checkout gates is strictly forbidden.

    6. Payment & Subscription Integrity

    • Free Trial Farming: Repeatedly generating short-term "Free 14-Day Trials" using temporary alias routing, disposable email addresses, or rotating payment methods for the explicit purpose of processing commercial client work without transitioning to a legitimate paid scale is considered theft of service.
    • Chargeback Misuse ("Friendly Fraud"): We make canceling your account or adjusting your sliding-scale metrics incredibly straightforward via your active dashboard. Initiating a direct, adversarial credit card chargeback dispute with your bank for a legitimate subscription or renewal invoice, rather than addressing it through our standard channels, violates fair use.
    • Grace Period Manipulation & Cyclical Delinquency: Our 14-day grace period is designed to act as a supportive safety net for occasional corporate procurement delays or unexpected bank routing errors. Repeatedly or systematically allowing your billing method to fail at the start of consecutive billing cycles—effectively exploiting the 14-day grace period to delay payments while keeping active reviews running—is a strict misuse of our payment integrity parameters. edoro reserves the right, at our absolute discretion, to bypass the 14-day grace period entirely, enforce an immediate hard lockout on Day 15, or permanently close the workspace without a refund for accounts that exhibit a pattern of habitual payment failure.

    7. Delinquency, Termination, and the 21-Day Deletion Lifecycle

    • If an automatic billing attempt fails or a subscription renewal lapses, we do not penalize your team by immediately wiping your data. Instead, we initiate a structured, multi-phase safety sequence to protect your active operations while giving your procurement team clear boundaries to settle outstanding invoices.
    • [Day 1] Failed Payment ➤ 14-Day Grace Period (No Restrictions + Payment Reminders)
    • [Day 15] Lockout Phase ➤ Access Paused (Entire Team & Shared Proof Links Blocked)
    • [Day 21] Permanent Purge ➤ Workspace Data, Workflows, & Credits Deleted Permanently

    Phase 1: Days 1–14 (Grace Period, Reminders, and Billing Anchor Alignment)

    • To ensure temporary payment issues do not disrupt your business, your workspace remains fully operational during these first 14 days.
    • Zero Service Restrictions: We do not pause, block, or restrict any core platform features, file uploads, workflow edits, or user permissions during this timeframe. Your reviewers will continue to receive automated notifications, and shared links remain completely active.
    • Retries & Reminders: The billing system will execute 4 automated payment-processing retries over the next two weeks, and our systems will send clear email reminders to your billing administrators to update your payment method.
    • The Compute Resource Exception: While we protect creative timelines by keeping standard canvas features and shared links running during this grace period, this safety net does not apply to Automate Actions and AI Processing Credits. If your workspace completely exhausts its active balance of Actions or AI Credits during delinquency, those specific automation pipelines and AI preflight features will stop working immediately upon credit exhaustion and will not resume until a successful payment or top-up is processed.
    • The Billing Cycle Adjustment Rule (Strict Anchoring): If a failed payment is settled at any point during this 14-day delinquency period, your outstanding invoice is cleared, but your billing cycle renewal date remains anchored to its original due date. Delinquent days are not added as extra service days.
    • For example: If your monthly subscription was set to renew on the 1st of the month, but payment failed and was resolved on the 14th, your account is immediately restored to active status, but you will have exactly 16 days remaining in your current billing cycle before your next invoice is due on the 1st of the following month. This cycle adjustment rule applies to both monthly and annual billing cycles, without exception, to prevent payment from shifting.

    Phase 2: Days 15–21 (Account Lockout Phase)

    • If the delinquency extends beyond Day 14 without a complete invoice resolution (or if you choose to let a terminated account expire beyond the grace period), the platform enters a Hard Lockout Phase on Day 15. Your structural data remains safe on our backend, but all operational systems are completely paused.
    • Operational Freeze: All team members, administrators, and owners are entirely blocked from logging into the platform dashboard. Furthermore, all outgoing automated workspace emails have been stopped, and all shared asset links (including public review proofs) are strictly locked, disabling access for clients, review partners, and stakeholders.

    Phase 3: Day 21 (Immutable Permanent System Purge)

    • If the account remains delinquent or terminated at the end of Day 21, all workspace data is permanently and immutably deleted from the platform servers.
    • Complete Data Loss: This includes custom workflows, historical review annotations, comment threads, task boards, user settings, and raw uploaded creative files. Because this erasure is hard-coded at the server database layer for compliance and security, it cannot be reversed.
    • Credit & CNAME Forfeiture: All unused, unexpired compute credits are permanently deleted. Any custom domain (CNAME) routing is removed from our load balancers, so you will need to repurchase the CNAME setup for $299.00 if your team decides to sign up again in the future.
    • The Formal Written Extension: If your team is experiencing corporate procurement delays, you can submit a formal written request to our support team prior to Day 21. edoro can grant a single 7-day lockout extension (delaying hard deletion by up to 28 total days from the initial failure). Absolutely no exceptions or extensions are permitted beyond this final limit.

    8. Severe Violations Protocol

    • No Grace Period for Malicious Activity: While standard billing failures receive the 14-day grace sequence outlined above, confirmed safety, security, or malicious resource abuse violations (such as trial farming, rogue infrastructure loops, malware hosting, or web scraping exploits) do not receive warnings or operational grace windows. The platform plug will be pulled immediately.
    • Total Forfeiture of Assets & Capital: If your workspace subscription is terminated due to a verified violation of this Fair Use Policy, your rights under our standard billing terms are voided. All project files, workflow layouts, and comment threads are permanently deleted. All remaining unexpired Automate Actions, AI Credits, prepaid onboarding blocks, and prorated annual conversion balances are instantly and completely forfeited with zero cash or credit refunds.