Usage Limits Policy
On this page
1) Introduction and scope
This policy states the quotas for each plan/add-on/cloud infrastructure/API and what happens if usage exceeds them.
Read together with the Pricing Disclosure, Billing & Payment Policy, Subscription Policy, Acceptable Use Policy, and Terms of Service; if conflicts arise, the stricter/more specific document controls (Order Form/SOW > this policy > Terms).
For Tanqory's own sale of platform subscriptions and services to the merchant, the Merchant of Record is Tanqory Inc. This does not apply to the merchant's own sales to its customers, for which the merchant is the seller and Merchant of Record under the Merchant Agreement; binding numbers are in the live dashboard/Pricing page (https://partners.tanqory.com/pricing) or Order Form; appendix tables are snapshots for quick reference.
Primary governing law is Singapore (unless a contract specifies otherwise) and subject to sanctions/AML constraints.
Customers must keep contact/tax/billing data accurate for quota calculation, tax, and to avoid disruption.
Quotas may vary by region or cloud provider (DigitalOcean/AWS/GCP/Azure) and will be shown in the dashboard/Order Form.
If changes are announced and you continue using the services, you accept the new quotas/rates.
We support both soft limits (notifications/throttling) and hard limits (blocking) with cost controls such as spending caps/auto-scale.
Enterprise/Custom terms follow Section 9 and Order Form/SOW.
Historical usage and alerts are available in the dashboard/channels in Section 6 so you can manage before exceeding quotas.
2) Plan quotas (snapshot)
Each plan has quotas for Orders/Stores/Team/Products/CDN/API as per the snapshot below; binding numbers are in the dashboard/Order Form if they differ.
Quotas reset each billing cycle (UTC) unless the contract states otherwise and update automatically when upgrading/downgrading plans or toggling add-ons.
DigitalOcean is included in standard plan pricing; choosing AWS/GCP/Azure adds uplift per Appendix A and may impose egress caps/overage per provider.
At least 12 months of historical usage can be viewed/downloaded (CSV/JSON) in the dashboard; Enterprise can request more detailed reports.
Quota warnings at 80/90/100% via email/dashboard (see Section 6); overage starts at 100% at rates in the appendix.
Customers may set soft caps or disable auto-scale to prevent overage (see Section 7).
Compliance constraints (e.g., PCI isolation/HIPAA/FedRAMP) may impose specific quotas/resources; must be stated in the Order Form.
If abnormal usage (spike/abuse) occurs, Tanqory may temporarily limit to protect stability/cost and will give reasons.
Third-party services/apps are subject to their own quotas/rates, which may add costs.
See quota snapshot in Appendix A; Tanqory will give ≥30 days’ notice when changes add burden.
3) API rate limits
Rate limits are per endpoint with multipliers by plan; binding values are in the dashboard/API docs (https://tanqory.dev) with headers showing remaining quota.
Basic example: Read 100/min, Write 30/min, Bulk 10/min, Search 50/min, Upload 10/min with bursts as noted in Appendix; Team/Business/Enterprise get 3x/10x/Custom multipliers.
Responses include X-RateLimit-Limit, X-RateLimit-Remaining, X-RateLimit-Reset, Retry-After so clients can re-queue.
When limits are hit, system returns 429 with Retry-After; use exponential backoff, pagination, webhooks instead of polling, and conditional requests (ETag/If-Modified-Since).
Pen-testing/scanning without prior approval is prohibited; attacking/spamming APIs is an AUP breach and may trigger immediate suspension.
Protect API keys; do not expose client-side without safeguards; rotate keys when at risk.
Enterprise may request custom rate limits/SLA via Order Form with load-verification terms.
If abnormal usage or retry storming occurs, Tanqory may temporarily reduce limits or enforce a hard cap for stability.
Rate-limit reductions that diminish user rights will be announced in advance unless a security emergency.
See snapshot figures in Appendix A and live limits in dashboard/API docs.
4) Storage and files
Storage quotas cover file/db/media/backup per plan (see Appendix A); storage overage is billed on GB/month exceeding quota.
File size limits by type (e.g., Images 10–100 MB by plan; Video 100 MB–10 GB) and supported types (JPEG/PNG/WebP/AVIF/SVG/HEIC, MP4/MOV/WebM, PDF/DOC/XLS/CSV, ZIP/7Z, etc.).
Backups per plan (7–30 days); for longer retention, use add-ons or an Enterprise agreement.
Deletion/downgrade may remove data over quota automatically after notice—back up/download before.
Basic malware scanning is automatic; harmful files may be quarantined/removed and may impact the account.
Hosting illegal/IP-infringing/harmful content is forbidden; breaches AUP and may be suspended immediately.
CDN/Optimization (WebP/AVIF, Brotli/Gzip, caching) is on by default to reduce bandwidth.
Enterprise can request larger file sizes/retention/custom encryption via Order Form.
Real-time storage usage is in the dashboard; alerts at 80/90/100% per Section 6.
For migration/archival, Tanqory can offer Professional Services with scope-based fees.
5) Bandwidth and data transfer
Includes CDN egress per month by plan; binding figures in dashboard/Appendix A and may differ by region/provider (AWS/GCP/Azure have different caps/egress fees).
Counted: static assets, media downloads/streams, API responses; Not counted: some admin dashboard traffic and internal system traffic.
At 100% of quota, overage is charged at rates in Appendix A or Order Form; customers can set soft caps/disable auto-scale to stop extra charges.
Automatic optimizations (image compression, Brotli/Gzip, CDN caching, lazy loading) help reduce usage.
If abnormal spikes occur, Tanqory may throttle/limit temporarily to protect cost/stability and will give reasons.
Enterprise may request reserved capacity or dedicated CDN/WAF per contract.
Use webhooks/streaming with awareness of limits/caching to avoid overage.
Lower overage rates take effect immediately; increases/cap reductions with added burden will have ≥30 days’ notice.
Calculations use UTC billing cycles and appear itemized on invoices.
Historical bandwidth data is downloadable from the dashboard.
6) Alerts and monitoring
Alerts at 50% (info), 80% (warning), 90% (critical), 100% (exceeded) via dashboard/email, and SMS for Team+ (if enabled).
Alert emails show current usage, reset date, and options: upgrade, wait for reset, set spending limit, or disable auto-scale.
Set budget alerts and spending caps in Settings → Billing; when cap is reached, auto-scale stops per your setting.
Real-time usage: Dashboard → Usage Overview; Settings → Billing → Usage Details; or API GET /api/v1/account/usage.
If alerts/usage data are missing, contact support@tanqory.com to resend or troubleshoot.
Security-related alerts (abnormal spikes) may arrive earlier or outside normal quota thresholds.
Customers acknowledge that disabling some alert channels may delay awareness and cause overage.
We log alert history for dispute/audit reference.
Any change in alert frequency/channels will be announced in advance unless for security reasons.
Enterprise can set custom alert runbooks (e.g., webhook/Slack) per contract.
7) Overage and controls
Overage starts at 100% of quota; rates in Appendix A/dashboard/Order Form and itemized on invoices.
Controls: auto-scale (on/off), spending cap, budget alert, soft cap (notify), and hard stop (block at threshold) to prevent unintended charges.
Billed per unit of actual use, charged with the next bill or immediately if unusually high or above published thresholds.
Discounts/credits/promotions apply before tax and exclude tax/government fees unless stated.
In case of chargeback/delinquency, Tanqory may set reserves/holds per Billing Policy to cover risk.
Invoice/overage disputes: notify within 30 days (SLA: intake ≤2 Business Days, updates every 10 days, target resolution 30 days or notify if longer).
To stop overage immediately, disable auto-scale and set a hard stop/soft cap; customers must back up/reduce usage if blocking takes effect.
Enterprise can negotiate overage rates/thresholds and billing models (e.g., quarterly true-up) in contract.
Other currencies use mid-market FX at billing time; bank/FX fees per Billing Policy.
Late fees/interest are capped by law (see Billing Policy Appendix A).
8) Soft/hard limits and suspension
Soft limit: notify and possibly slow (e.g., API 429) but allow continued use with overage if auto-scale is on.
Hard limit: block creating/uploading/adding orders/members/stores/products at the cap, or temporarily suspend if stability/security is at risk.
Typical sequence: notify → slow/429 → block some actions → partial suspension → full suspension/termination (steps may be skipped for high risk such as abuse/sanctions/security).
Tanqory may request additional info or KYC/AML when abnormal use or financial/compliance risk appears.
If blocked by hard stop, customers can remove the hard stop or upgrade/increase quota to resume.
Data/content above quota may be deleted/quarantined/disabled after notice for safety and cost control.
Unauthorized pen-testing/scanning is a breach and may be suspended immediately.
Illegal/sanctioned/AML/IP-infringing activity will be blocked immediately and may be reported.
Continued use after notice is deemed acceptance of temporary mitigation (rate limiting/throttling) to address risk.
Appeal channels and response SLA are in Section 13 and Billing Policy Appendix B.
9) Enterprise and custom limits
Enterprise customers can set quotas/caps/overage/rate limits/file sizes/retention and billing models tailored to workloads in the Order Form/SOW.
Add-ons: reserved capacity, dedicated infrastructure, premium support SLA, custom alert runbooks, data residency/segmentation, dedicated WAF/CDN.
Process: contact sales@tanqory.com or enterprise@tanqory.com with needs → assessment/offer within 2 Business Days (target) → Order Form/SOW → signature and activation.
Can set spend caps/quarterly true-ups/annual commits per financial terms stated.
Special-regulated workloads (PCI, HIPAA, FedRAMP, IRAP) must use certified services/regions/providers stated in the contract.
Custom SLA (uptime/response/resolution) and throttle policies for anomalies may be defined.
Custom migration/archival is fee-based per scope and specified in the quote/Order Form.
Temporary quota boosts for short campaigns can be requested and billed by actual use or add-on packages.
Detailed per-endpoint/resource usage reports are available for Enterprise on request.
Privacy/sensitive data requirements must follow the DPA/Privacy Policy and local law.
10) Regional requirements and applicable law
EU/UK: comply with GDPR/UK GDPR/IDTA/SCCs for data transfers; transparent renewal/cost per CRD/CCR.
US: comply with Auto-Renewal/Negative Option laws (e.g., CA B&P §17600‑17606, NY ARL) for renewals, and state caps on fees/interest (see Billing Policy).
Singapore: comply with PDPA/local consumer law, including e-tax invoice/e-receipt where mandated.
Australia/Canada/Japan/UAE: comply with relevant tax/advertising/consumer and sanctions/export rules.
Service may not be used in sanctioned regions (UN/EU/OFAC/UK/HK/SG, etc.) or to evade sanctions/export controls.
If local law mandates disclosures/special caps, Tanqory will add required notices in dashboard/invoice/Checkout.
Customers are controllers of their customer data and must have a legal basis and honor data subject rights.
AI/automation hitting APIs at scale must respect the AUP and avoid unlawful automated decision-making.
Quota/overage/suspension disputes use the governing law stated above unless a specific contract differs.
This document’s English version controls if there is a conflict with translations.
11) Security, acceptable use, and data
Follow the Acceptable Use Policy: no spam/phishing/malware/illegal content/IP infringement/sanctioned activity.
Secure accounts and use MFA/2FA; keep API keys confidential and rotate when at risk.
Abnormal activity affecting stability (e.g., retry storming/scraping/abuse) may be throttled/blocked immediately.
Access/processing of personal data must follow the Privacy Policy/DPA and use lawful transfer mechanisms.
Security incidents must be reported promptly via designated channels; Tanqory will follow Incident Response and notify authorities per law.
Backups/deletion after termination are the customer’s responsibility; Tanqory may delete data after the retention period.
Pen-testing requires prior written authorization.
Bots/scripts must respect rate limits and not evade protections.
Repeated/serious violations may lead to service termination and/or enforcement under contract/law.
Shared responsibility: Tanqory secures platform/infrastructure; customers secure their content/config/access.
12) Policy changes
Limit increases/price reductions/credits: effective immediately or on the announced date; changes adding burden (lower limits/higher overage) will have at least 30 days’ notice via email/dashboard (durable medium per EU/UK practice).
Annual plans lock pricing per contract; pass-through tax/provider cost changes (e.g., egress) will be communicated with appropriate options.
If price/quota data conflict, rely on the latest document (Order Form/dashboard/invoice).
Changes mandated by law/security may take effect faster and may start immediately to mitigate risk; notice will follow as soon as practicable.
Notices and versions are retained for dispute reference.
Customers may terminate before the effective date if they do not accept changes, per rights in Terms/contract.
Promotions/discounts/coupons follow the Promotions & Coupons Policy and may expire as stated.
Requests for temporary/permanent quota changes should use dashboard channels or sales.
If interpretation conflicts arise, the English version controls unless mandatory law dictates otherwise.
Updates to this version will appear in the change history below.
13) Updates and notices
Material updates (e.g., quota/price changes or enforcement mechanics) will be posted at https://legal.tanqory.com with effective date/version and, where appropriate, announced via email or dashboard before taking effect. Live dashboard/Order Form numbers always prevail over snapshots. If you do not agree with a change, downgrade/cancel before the effective date; statutory rights remain.
Version history
| Version | Date | Notes |
|---|---|---|
| 2.0 | 10 Dec 2025 | Initial publication with quotas, overage rules, and notice mechanics. |
13) Contacts and appeals
General/usage/technical: support@tanqory.com
Billing/quotas/overage/disputes: billing@tanqory.com (include account/invoice/Order Form)
Sales/Enterprise/Custom limits: sales@tanqory.com, enterprise@tanqory.com
Legal/privacy/sanctions: legal@tanqory.com
Urgent/emergency channels for Enterprise are listed in the Order Form/Runbook.
Billing dispute SLA: intake ≤2 Business Days, updates every 10 Business Days, target resolution 30 days (or notice if longer).
Report pricing/quota display issues with evidence (screenshots/invoices) to speed review.
Appeal suspensions/blocks via support@tanqory.com or billing@tanqory.com with reasons and remediation.
If usage/bill/alerts are missing, contact us to resend or fix notification settings.
Help Center: https://help.tanqory.com
Appendix A: Quota/overage snapshot (quick reference)
- Binding numbers: live Pricing/dashboard or latest Order Form if different from this snapshot.
- Snapshot as of 10 Dec 2025 (updated when price/quotas change).
| Plan | Orders/mo | Stores | Team | Products | CDN Bandwidth | Included API Calls | Infra Uplift | Overage (see dashboard) |
|---|---|---|---|---|---|---|---|---|
| Solo | 500 | 1 | 1 | 50 | 50 GB | 1M/mo | DigitalOcean included | Storage $0.10/GB/mo; Bandwidth $0.01/GB; API $0.001/1k calls |
| Team | 5,000 | 3 | 5 | 500 | 200 GB | 5M/mo | DO included / AWS+10 / GCP+10 / Azure+15 USD | Bandwidth $0.01/GB; API $0.001/1k calls; Storage $0.10/GB/mo |