Read this page in English

Meta and API Spend Policy — AMASFLY Studio

DRAFT FOR REVIEW BY THE CEO'S HUMAN COUNSEL. Prepared by Carola (Legal Advisor, AMASFLY) on October 15, 2026. This is not final legal advice. [[VARIABLE]] = pending CEO decision. English translation of the Spanish original; see section 11.

Version 0.2 (draft, adjusted for U.S. Customers) · Effective as of [[EFFECTIVE_DATE]]

This Policy forms part of the AMASFLY Studio Terms of Service. It explains who pays for what, who approves spending, and what happens when something goes wrong. There are five distinct spend items and they are not mixed:

1. Principles

1.1. AMASFLY never advances, finances or handles advertising money. We do not receive your advertising budget, we do not pay Meta for you, and we do not lend you credit to advertise.

1.2. Nothing is spent without the Human Reviewer's express approval. Silence is not approval: if the Human Reviewer does not respond, no spend is activated or increased.

1.3. Hard caps, not just warnings. Where the technology allows, caps are enforced as blocks, not merely as notifications.

1.4. Transparency: the Customer sees on the Platform, in near real time, what has been consumed and approved.

2. Advertising on Meta

2.1. Customer's account and payment. The ad account, payment method and permissions belong to the Customer. Meta issues advertising invoices to the Customer, who is the advertiser and is responsible to Meta.

2.2. Who approves. The Human Reviewer approves in writing on the Platform, before any ad runs: (a) each Campaign (objective, audience, creatives and text); (b) the daily cap and the total or monthly cap of each Campaign; (c) each increase in budget; (d) each reactivation of a paused campaign.

2.3. How caps are applied. The Platform configures budgets in Meta with an end date and a total cap (lifetime budget) or a daily cap, does not open campaigns without a defined budget, and maintains a global monthly cap for the Customer [[defined by the Human Reviewer; AMASFLY recommends one]]. If the Human Reviewer has not defined caps, no campaign is created. (Note for development: see spec-controles-de-contenido.md, section 9.)

2.4. Alerts. We notify the Human Reviewer upon reaching 80% and 100% of the cap, and upon anomalous spend (for example, a day with more than [[150]]% of the daily cap).

2.5. Emergency pause. AMASFLY may pause campaigns, without awaiting approval, if it detects spend outside the caps, possible fraud, a policy violation or an order from an authority. Reactivation always requires the Human Reviewer's approval.

2.6. Meta's technical limit. Meta may spend slightly above or below the daily budget for reasons inherent to its system, and may bill with a delay. What Meta charges under its rules is the Customer's responsibility toward Meta; AMASFLY is not liable for those differences.

2.7. Taxes. Taxes on advertising (for example VAT or withholdings) are determined by Meta and borne by the Customer. Sales or use tax on the monthly fee and overage is calculated and collected by Paddle (Terms, clause 11.7).

2.8. Time zone and currency. The "day" of the daily caps and the end dates are counted in the time zone of the Customer's ad account, and advertising is paid in the currency of that account (for a U.S. Customer, normally dollars) [[Development: confirm against Meta's configuration]]. The monthly fee and overage are charged in [[USD]] by Paddle.

3. Results: not guaranteed

3.1. AMASFLY does not guarantee results of any campaign: reach, clicks, messages, leads, sales, cost per result, return on investment or follower growth.

3.2. Reports show data supplied by Meta. AMASFLY is not liable for errors, delays or changes by Meta in those metrics.

3.3. The proposals of the Studio's AI agents (audience, budget, formats) are automated suggestions for the Human Reviewer, not a promise of performance or professional advice; the Studio does not include campaign management by AMASFLY personnel.

4. Included AI generation, overage and synthetic-voice narration

4.1. Included. The monthly fee includes US$ 20 of generation (images, text and other AI tools, excluding video and narration) each calendar month of the billing cycle. The value is calculated at the cost charged by the provider (for example, OpenAI) for each call, according to the provider's current published prices. The US$ 20 does not roll over to the following month. [[CEO: confirm]]

4.2. Separate project per Customer. Each Customer has its own OpenAI key and project, separate from those of any other Customer, in order to measure and isolate consumption precisely. With that same separation AMASFLY can apply a monthly spending limit to the project.

4.3. Notices. We notify the Human Reviewer at 80% and 100% of the US$ 20.

4.4. Overage. All usage above the US$ 20 is charged in addition to the monthly fee, on the next invoice, through Paddle, with usage details [[at cost / with a markup of [[%]]: CEO decision]]. How it is technically charged: see section 8.

4.5. Prior acceptance by amount. [[PENDING CEO: does overage need the Human Reviewer's express prior acceptance before exceeding a certain amount?]] Carola's recommendation: yes. Proposal: when the cycle's overage reaches US$ [[10]], generation is paused until the Human Reviewer agrees to continue up to a new cap set by them. Without acceptance, no further generation occurs. This avoids surprise invoices, reduces chargeback risk, and is consistent with the rule that silence does not approve.

4.6. Technical hard cap. Until the acceptance in 4.5 exists, the Platform applies a hard generation cap of US$ [[MAX_OVERAGE_CAP]] per cycle and per Customer (suggestion: equal to the prior-acceptance amount), so that overage cannot grow without approval.

4.7. Retries. Automatic retries for transient image or text failures are limited to [[1]], and their costs count toward consumption. A result rejected by moderation is counted if the provider charged for it.

4.8. When the contract ends, pending overage is billed on the final invoice or in a final transaction, as Paddle permits.

4.9. Synthetic-voice narration: what the Customer chooses. The Customer chooses the voice (with listening samples in its panel), the tone, the script's form of address (tú, vos or usted; the voseo is permitted in the Customer's content if the Customer chooses it) and the speed.

4.10. Price. Narration costs US$ 2 per minute, in addition to the US$ 20 included. The actual seconds are charged, rounded up to the next half minute (for example: 47 seconds is charged as 1 minute; 61 seconds as 1.5 minutes).

4.11. Only the final approved narration. Tests and iterations are free, until the Customer makes its choice. Only the final narration approved by the Human Reviewer is charged. Narration does not consume the US$ 20 included or the video cap.

4.12. Invoicing. The narration charge is invoiced in the month through Paddle, with details available on the Platform.

5. Video (Kling via Higgsfield): the Customer's own account and special rules

Video costs far more than an image. AMASFLY does not sell or bill video: the Customer generates it with its own Higgsfield account and pays Higgsfield directly. Video is not billed through Paddle, as overage, or with a markup.

5.1. Customer's own account. Video is generated with the Higgsfield account the Customer opens and connects to the Studio. Consumption, billing and the contractual relationship with Higgsfield belong to the Customer; AMASFLY is not a party to them.

5.2. Prior approval for each video, with estimated cost. Before generating each video, the Platform shows the Human Reviewer: the description, the duration, the model and the estimated cost in dollars. It is generated only if the Human Reviewer expressly approves. Without a response, it is not generated.

5.3. Monthly safety cap, set by the Customer. The Customer sets a monthly video cap, in dollars, in its panel as a safety limit. There is no suggested or default cap: until the Customer sets one, the Studio does not approve videos. Upon reaching it, video generation is blocked until the next cycle, unless the Human Reviewer approves an express, recorded extension. The cap is a Studio control; it does not limit what Higgsfield charges on the Customer's account.

5.4. Never retried automatically. If a video fails, is rejected by moderation or the result is unusable, the Platform does not regenerate it on its own. The Human Reviewer must approve each new attempt again, seeing the cost. If the provider retries internally on its own, we configure it to disable this; if not possible, it is documented.

5.5. No billing by AMASFLY. The cost of video does not count against the US$ 20 included and is not charged on any AMASFLY invoice. Higgsfield charges it directly to the Customer on its own account.

5.6. Disclaimer. Every video and every regeneration is charged on the Customer's Higgsfield account. AMASFLY is not responsible for spend on the Customer's Higgsfield account or for the iterations that the Customer or its Human Reviewer requests or approves. The Customer expressly accepts this when setting its monthly video cap and when approving each video.

5.7. Recommendation and MCP. The Studio recommends generating and refining videos from the Customer's own Claude or Codex connected to the Studio MCP, because better results are achieved there. Video can be requested and approved through the MCP, but always within the cap the Customer has set; approval through the MCP counts as approval by the Human Reviewer.

5.8. No sensitive material. Material flagged as sensitive (photos of third-party interiors with people, identifiable minors) is not sent to video generators except with the specific approval described in the acceptable use policy and the technical spec.

6. What happens if Meta rejects or suspends

6.1. Rejected ads. Meta reviews each ad. If it rejects one, the Platform notifies the Human Reviewer with the reason Meta shows, proposes a correction (for example, adjusting text or image), and resubmits only with their approval. Meta's review systems are not evaded (for example, by hiding content or creating new accounts to bypass a block).

6.2. Restriction or suspension of the ad account, page or payment method. The account is the Customer's, and the decision is Meta's. AMASFLY (a) pauses the affected campaigns and posts, (b) notifies the Human Reviewer, (c) helps prepare the information for the appeal that the Customer itself files in Meta's tools (for example, the account support center), and (d) does not guarantee the outcome.

6.3. Liability. AMASFLY is not liable for the rejection or restriction or for resulting lost profits, unless the cause is a violation attributable to AMASFLY through willful misconduct or gross negligence (for example, publishing without approval). The monthly fee is not refunded for this cause, except as provided in the Terms.

6.4. If the cause was Customer content that breached Meta's rules or the Acceptable Use Policy, the Customer bears the consequences.

6.5. Spend already executed. What Meta has already charged for ads that ran with approval is not refunded by AMASFLY.

7. Key isolation and security

7.1. Each Customer's API keys are separate, encrypted and not shared between Customers. A Customer never sees the keys of AMASFLY or of another Customer.

7.2. Meta tokens are stored encrypted and revoked upon termination of the contract.

8. How overage is invoiced (note for the CEO and counsel)

According to Paddle Billing's official documentation, a one-time charge can be added to an existing subscription through the subscription charge endpoint, using the effective_from parameter: next_billing_period (added to the next renewal, which is what the CEO decided) or immediately (immediate transaction). Paddle states that, for metered usage, the seller calculates the amount on its own platform and adds it as a charge; Paddle does not measure usage. A transaction preview exists before charging. Source: developer.paddle.com (Bill for one-time charges; Create subscription charge; Metered billing).

• The charge will be included in the invoice/receipt issued by Paddle.
• If payment of the charge fails, the non-payment rules in the Terms apply.
• To verify with Paddle: whether charges with variable amounts that do not previously exist in the catalog can be created; the charge limit; the tax treatment of overage; refund and dispute of usage-based charges; and whether charging variable consumption on a subscription of this type is compatible with its accepted-business policy.

9. Customer control

The Human Reviewer may at any time view consumption, lower or raise their own caps (an increase requires confirmation), pause generation, pause campaigns and disconnect Meta.

10. Contact

[[STUDIO_CONTACT_EMAIL]]

11. Languages and versions

This Policy exists in Spanish and English. If there is any discrepancy between the two versions, the version indicated in clause 25.4 of the Terms prevails [[CEO DECISION]]. AMASFLY S.R.L. is a Bolivian company.

Draft — pending final legal review