Penguin Translator pricing for teams keeps administration simple. Each workspace picks a single plan—most teams choose Premium for shared history, seat management, and API access—and then add members as needed. Every seat shares one renewal date and quota pool, so finance only reconciles one invoice.

Start on the Free tier to prototype, then upgrade from the pricing plans page when you're ready. Need SSO, custom terms, or security review? Contact us via About & Contact and we'll match the right onboarding path.

All paid plans bill in USD through Stripe. During checkout you can add VAT, GST, or tax IDs so invoices show the right country codes and reverse-charge notes. Download every invoice or receipt from the billing portal, and you'll see prorated adjustments when you change plans mid-cycle.

Note: Add tax details during checkout; retroactive edits require a support ticket and may delay compliance receipts.

Downgrades never claw back what you already paid. When you switch tiers, your current billing period stays active until its scheduled renewal date, so your team keeps Premium features until that moment. The next invoice (or lack of one) reflects the lower pricing tier.

Plan to export shared glossaries or API keys before the downgrade effective date, because those advanced capabilities switch off right after renewal. Full behavior is detailed in the terms of service.

Every plan combines a per-minute burst limit with a per-day quota. Free allows 50 requests per calendar day with a low burst cap; Pro raises that to 500 daily, and Premium climbs to 1,500. Minute windows reset automatically every 60 seconds, while daily counters reset at midnight UTC.

Use the quota widget in the dashboard to watch both numbers in real time, and schedule larger batches slightly apart to avoid tripping the minute ceiling.

A translation request is any action that engages the translation engine, regardless of interface.

• Clicking Translate in the app.
• Replaying a saved history entry.
• Calling the API with new text.

Manual retries you trigger count again, but automatic network retries do not. Copying past results or exporting history stays free.

Tip: Bundle related sentences (up to the character limit) to minimize how many requests you spend each day.

Server-side caching speeds up repeat translations but does not waive pricing rules. When we serve a cached response, the original request already consumed quota, so the subsequent hit reuses the output without charging you twice. If the cache expires or the source text changes, we process it again and deduct a fresh request.

Local browser cache works similarly—it improves perceived speed, yet quota math happens on the server and always reflects real processing.

Payment credentials never touch Penguin Translator servers. All card data flows directly to Stripe, our PCI-DSS Level 1 provider, through a secure iframe, and we only store masked card brand, expiry, and invoice history—encrypted at rest.

Premium workspaces can require multi-factor authentication via Clerk before anyone views billing screens, keeping finance data safe even if a seat is compromised.

Deleting your personal account wipes profile details, translation history, and saved preferences immediately.

Billing metadata follows different retention: Stripe keeps invoices for tax compliance, and we retain minimal plan identifiers for [[ADD_DATA_RETENTION_POLICY]]. If you close a paid workspace, quotas disappear right away and any remaining prepaid time is handled under [[ADD_REFUND_POLICY]]. Review the terms for full closure language.

On the Free tier, translation text stays in your browser only. On Pro and Premium, synchronized history lives in encrypted storage and purges automatically after [[ADD_DATA_RETENTION_POLICY]]. We keep lightweight analytics—timestamps, request counts—to monitor quotas but never store source text longer than necessary.

Billing records stay with Stripe for the legally required term (commonly seven to ten years). See the privacy policy for the evolving retention schedule.

Copy limits scale with plan tier. Free supports up to 1,000 characters per submission, Pro increases the cap to 10,000, and Premium reaches 50,000 including extracted text from PDF or DOCX uploads.

The composer shows a live counter beneath the text area so you can trim or split content before sending. For longer documents, break them into logical sections—each translation still lands in history so you can stitch the full piece together.

API usage currently ships with Premium workspaces (beta). Each API call counts as one translation request and respects the same per-minute and per-day quotas as the UI. Authenticate with your workspace token and follow the published rate limit shown in settings; exceeding it returns HTTP 429.

Implement exponential backoff, caching, and batching to stay efficient. Need higher throughput or dedicated IPs? Reach out through About & Contact for a custom add-on.

Cancelling stops auto-renewal but keeps paid features active until the current billing cycle ends, so you can wrap up projects without interruption. Refunds are handled manually—email support within [[ADD_REFUND_POLICY]] so we can review usage and eligibility. Approved refunds post back to the original payment method.

Warning: Submit cancellations at least 48 hours before renewal so Stripe can settle taxes and invoices cleanly. Full policy language lives in the terms of service.

Minute limit errors mean the burst ceiling fired. Wait 60 seconds—the window resets automatically—then retry. If it happens often, stagger large jobs or distribute them across teammates so each session uses its own buffer.

Check the quota widget for which metric is tightest. If integrations are re-sending the same text, audit logs in history will show duplicates. Still blocked? Upgrade on the pricing plans page or send timestamps to support so we can investigate.