Pika raised its minimum age requirement from 13 to 18 years old for all users, expanded the Service definition to include APIs and third-party model access, introduced organizational account structures with designated administrators, and restructured its monetization and payment model from subscription-based profit sharing to a flexible system combining subscriptions, usage-based charges, and prepaid credits with explicit nonrefundable and expiration terms. The company also removed detailed language describing AI Self autonomous operation and training responsibilities, and added new provisions governing API key management, rate limiting, and organizational liability.
Organizations: If you use Pika as an organization, you are responsible for managing who can access it and for everything those users do on the platform.
Developers: If you use Pika's API, you must keep your API keys secret, tell Pika immediately if they are compromised, and accept that Pika can limit or stop your access if usage is excessive or abusive.
Consumers: You must be at least 18 years old to use Pika; users aged 13-17 are no longer permitted.
Consumers: If you buy prepaid credits, you cannot get your money back, and any credits you do not use within one year will be lost.
Developers: Pika can limit how much you use the API and can slow down or stop your requests if you exceed those limits or use it in a way Pika considers abusive.
Consumers: The terms no longer explicitly detail how you train your AI Self or your responsibility for what it generates; the language is now simplified.
The updated terms raise the minimum age to use Pika from 13 to 18 years old, which will restrict access for users aged 13-17. The revised payment model introduces prepaid credits as an alternative to subscriptions; credits are nonrefundable and expire 365 days after purchase. The terms now explicitly authorize organizational accounts with designated administrators who manage user access and bear responsibility for user compliance, and establish that organizations remain liable for all acts and omissions of authorized users. For API users, the terms introduce new requirements for API key management, confidentiality, and security, and authorize Pika to establish rate limits, throttle usage, or revoke API keys for security or suspected abuse.
→ If you are aged 13-17, you will no longer be able to use Pika after this change takes effect; existing accounts will be subject to the new 18-year minimum age requirement.
→ If you purchase prepaid credits, review the 365-day expiration date and nonrefundability terms before purchase; unused credits will not be refunded after expiration.
→ If you use Pika's API, review the new rate limiting, API key management, and usage restriction provisions; ensure your API keys are kept confidential and notify Pika immediately if compromised.
Raised from 13 to 18 years old for all Service access; users aged 13-17 are no longer permitted.
Organizations remain liable for all acts and omissions of authorized users; administrators must ensure compliance and manage access.
Credits are nonrefundable, expire 365 days after purchase, and expired or unused credits will not be refunded.
This change record describes what was added, removed, or modified in the document. Analysis reflects what the updated agreement states or permits. It does not constitute a legal determination about enforceability. Applicability may vary by jurisdiction. Methodology
Wording edits to this record that do not change what it claims. Changes to a claim are published as corrections.
Pika restructured its terms to support organizational and API-based use cases while raising the minimum age requirement to 18. The change introduces new governance structures (organizational accounts with administrators), payment mechanisms (prepaid credits with expiration), …
Regulatory exposure, obligation change, escalation trigger, board-ready language, and recommended action for legal and compliance teams.
Unlock the full institutional analysis — InsightConductAtlas provides verified policy intelligence sourced directly from platform documents. All analysis is intended to support, not replace, legal and compliance review. Record CA-X-005161.
Get the weekly coverage letter
Companies change their terms without announcing it. We capture governance documents, compare each new version with the last, and publish what changed, with the source text behind it. One email a week on what we found and what we could not reach.
Get alerted when this policy changes again, including what changed and why it matters.