Tables Extractor — Credit Terms of Use
These terms govern the credit-based usage model of Tables Extractor for Jira and Confluence.
Credit-Based Usage
Tables Extractor operates on a credit-based system. Each page processed (whether from a PDF or image file) consumes one (1) credit. Credits are required to extract tables and are deducted at the time of processing.
Credit Allocation
Credits are allocated monthly based on your active Atlassian Marketplace subscription tier. The number of credits included depends on your plan, which is determined by the number of licensed users on your Atlassian site: Free Trial (no subscription) — 10 credits; 1–10 users — 100/month; 11–25 users — 250/month; 26–50 users — 500/month; 51–100 users — 1,000/month; 101–250 users — 2,500/month; 251–500 users — 5,000/month; 501–1,000 users — 7,500/month; 1,001+ users — 10,000/month.
Shared Credit Pool
Credits are pooled at the site (organization) level. All licensed users on the Atlassian site share a single credit balance. Individual user-level credit allocation is not supported. Site administrators are responsible for managing usage across their organization.
Credit Refresh
Credits are refreshed to your tier's full monthly allocation at the start of each billing period (every 30 days from the subscription start date). Unused credits do not roll over — the balance resets to the tier's monthly allocation upon refresh.
Subscription Requirement
An active Atlassian Marketplace subscription is required for credit refreshes. If your subscription lapses or is cancelled: remaining credits may still be used until depleted; no new credits will be allocated until the subscription is reactivated; your data and extracted tables are not affected.
Tier Adjustments
Your credit tier may change if the number of licensed users on your site changes. Upgrades (more users): your tier and monthly credit allocation increase immediately. Downgrades (fewer users): your current tier is maintained until the next credit refresh, at which point the allocation adjusts to reflect the lower user count.
No Refunds on Consumed Credits
Credits consumed for table extraction are non-refundable. Each extraction request is processed in real time using third-party OCR infrastructure, and costs are incurred at the time of processing regardless of the output quality.
Fair Use
The credit system is designed for normal business use. Automated, scripted, or programmatic bulk extraction that exceeds reasonable usage patterns may result in temporary suspension of service. If you anticipate high-volume needs, please contact us to discuss a custom arrangement.
Modifications
We reserve the right to adjust credit allocations, tier thresholds, and pricing with reasonable notice. Any changes will be communicated through the Atlassian Marketplace listing and will take effect at the start of the next billing period.
Contact
Questions about these terms? Email contact@lingway.io.