APIWings Terms of Service

Last updated: 9 November 2026

1. Agreement

These Terms of Service (“Terms”) are a contract between LV Tech Labs S.L. (in the process of incorporation), Carrer de Modolell 36, 2, 08021 Barcelona, Spain (“APIWings”, “we”) and the person or entity that creates an APIWings account or uses the Service (“Customer”, “you”). By creating an account, accepting these Terms in the dashboard or using the API, you agree to them. If you act for a company, you confirm you have authority to bind it.

The Privacy Policy (apiwings.com/privacy) and the Data Processing Agreement in Annex A form part of these Terms. If you have a signed Enterprise agreement with us, it prevails over these Terms where they conflict.

Early access. Until we announce general availability, the Service is offered as an early access programme: only some Platforms and features are available, paid plans are not yet open, and the service levels in Section 8 apply as stated there. We will notify you before general availability and of any change it brings to these Terms, as described in Section 18.

2. Definitions

3. Account and API keys

You must provide accurate account information and keep it current. You are responsible for all activity under your API keys, including by your employees, contractors and End Users. Keep keys confidential; do not embed live keys in client-side code or public repositories. If you believe a key is compromised, revoke it in the dashboard, or ask us to revoke it, immediately and tell us at support@apiwings.com. You may create keys scoped to a single Profile to limit exposure.

You must be at least 18 years old and may not use the Service if you are barred from doing so under applicable law or Platform Terms.

4. Acceptable use

The Platforms hold APIWings responsible for everything published through our integration. A single abusive Customer can cause a Platform to revoke our access for every Customer. For that reason the following rules are strict, and we enforce them automatically where we can.

You must not, and must not allow your End Users to, use the Service to:

• send spam, unsolicited or bulk promotional content, or publish substantially identical content across many accounts;
• publish content that violates a Platform's community guidelines or Platform Terms, including deceptive, misleading, infringing, harassing, sexually explicit or illegal content;
• operate fake, purchased or compromised accounts, or publish on an account without the genuine authorisation of its owner;
• circumvent Platform rate limits, visibility restrictions or review processes, or misrepresent to a Platform who is publishing;
• scrape, harvest or store Platform data beyond what the Service returns for your own Posts;
• resell the Service as a bare API without adding your own application, unless agreed in an Enterprise plan;
• interfere with the Service's security or other Customers' data, or reverse-engineer it except as permitted by law.

You are responsible for obtaining each End User's authorisation through the Platform's consent flow and for giving End Users a privacy policy that covers the use of APIWings. You must comply with all Platform Terms applicable to your use, including Meta's Platform Terms, TikTok's Developer Terms, the Google API Services User Data Policy, the YouTube API Services Terms (including the YouTube Terms of Service at https://www.youtube.com/t/terms), the LinkedIn API Terms of Use and the X Developer Agreement.

We may set per-account posting limits below those of the Platforms, and we may suspend a Profile whose Posts are rejected by a Platform at an abnormal rate, pending review. We will notify you by email, and you can contest the suspension at support@apiwings.com.

5. Connected accounts and Platform limitations

The Service depends entirely on the Platforms' APIs, which they change, restrict or withdraw without notice. In particular:

• Each Platform decides which content types, lengths, formats and quotas it accepts. The Service validates your request against the Platform's published rules and returns an explicit error when it cannot be published; it does not transcode, crop or edit media.
• Some Platforms restrict visibility until an integration passes their review. Where that applies, the Service publishes with the visibility the Platform allows (for example, private or self-only) and returns the actual visibility in the response. We publish the current status of each Platform on apiwings.com.
• Platform tokens expire or are revoked by the Platform or the End User. When that happens, Posts fail with an explicit error and we send an account.disconnected webhook; the End User must reconnect.
• We are not responsible for Platform outages, policy changes, account restrictions imposed by a Platform, or content removed by a Platform.

We will give reasonable notice when a Platform change forces us to remove or alter a feature, but we cannot guarantee continued availability of any Platform.

6. Plans, fees and billing

Paid plans are not yet available during early access. When they open, plans and prices will be published on apiwings.com and will form part of these Terms. Paid plans are billed monthly in advance through Stripe; usage above the plan's included Posts is billed at the end of each month at the overage rate of your plan. Prices exclude VAT and other taxes, which we add where required.

• Connected accounts are unlimited on paid plans; the Free plan is limited as stated on the pricing page.
• X pass-through: X charges APIWings for each API operation. If you enable X, we pass those charges to you at cost, without margin, itemised on your invoice. The current X price table is published in the dashboard and may change when X changes its prices; we will notify you by email and webhook.
• Failed Posts are not billed. A Post rejected by a Platform for content or policy reasons is billed once.
• You may upgrade at any time (prorated) and downgrade or cancel from the dashboard, effective at the end of the current billing period. Fees already paid are not refundable except where the law requires or Section 8 provides.
• If a payment fails, we will retry and notify you; after 14 days of non-payment we may suspend the Service until paid.

7. Free plan

The Free plan is for evaluation, personal projects and agents with low volume. It has no card requirement, includes the limits stated on the pricing page, and may be withdrawn or changed by us at any time. Free accounts inactive for 90 days may be deleted after notice.

8. Service levels

During early access we target 99.5% monthly availability of the API, measured on our own endpoints. Before general availability we will publish a public status page and the service levels that will apply from then on. Availability excludes Platform outages (a Post queued because a Platform is down is retried and does not count as downtime), scheduled maintenance announced at least 24 hours ahead, and causes outside our reasonable control.

Service credits for availability shortfalls will apply to the Scale and Enterprise plans from general availability, on the terms published with those plans; credits will be the sole remedy for availability shortfalls. Support response targets will be published with the plans.

9. API versions and changes

The API is versioned in the URL path (/v1). Within a version we only add optional fields and new values in enumerations documented as open; we do not remove fields or change their types. Breaking changes ship only in a new version, and the previous version keeps working for at least 12 months after the new one is announced. Deprecated operations are marked in the OpenAPI specification and announced in the changelog at least 90 days before removal. We may change, suspend or discontinue features with reasonable notice, and immediately where a Platform or the law requires it.

10. Suspension and termination

We may suspend your access, a Profile or an API key immediately if we reasonably believe you or an End User are breaching Section 4, if a Platform requires it, if your use threatens the security or stability of the Service, or if payment is overdue as described in Section 6. We will tell you why and, where the cause can be cured, restore access once it is.

Either party may terminate these Terms at any time: you by cancelling your account, we with 30 days' notice, or immediately for a material breach not cured within 10 days of notice. On termination we disconnect all accounts, delete all stored tokens and delete your data as described in the Privacy Policy. Sections that by their nature survive (fees owed, liability, confidentiality, governing law) survive termination.

11. Intellectual property

We own the Service, including its software, documentation, SDKs and trademarks. You receive a non-exclusive, non-transferable licence to use the Service and SDKs for your own applications while these Terms are in force. You own your application and the content you and your End Users submit; you grant us the licence needed to process, store and transmit it to the Platforms you select. You may describe your integration as “powered by APIWings” but may not use our name or logo otherwise without written permission. Feedback you give us may be used freely.

12. Confidentiality

Each party will keep the other's non-public information confidential, use it only for the purposes of these Terms, and protect it with reasonable care. This does not apply to information that is public, already known, independently developed or required to be disclosed by law (with notice where allowed).

13. Warranties and disclaimers

We will provide the Service with reasonable skill and care and as described in the documentation. Except as expressly stated, the Service is provided “as is” and we disclaim all other warranties, including merchantability, fitness for a particular purpose and non-infringement, to the extent permitted by law. We do not warrant that any Platform will accept a given Post, remain available, or keep its API unchanged.

14. Limitation of liability

To the extent permitted by law, neither party is liable for indirect, incidental, special or consequential damages, loss of profits, revenue, data or goodwill, or for actions taken by a Platform against your accounts. Our total liability under these Terms in any 12-month period is limited to the fees you paid us in that period, or €100 if you are on the Free plan. These limits do not apply to liability for death or personal injury, fraud, wilful misconduct, breach of confidentiality, or your payment obligations.

15. Indemnity

You will defend and indemnify us against third-party claims, fines and losses arising from your or your End Users' content, your application, or your breach of Section 4 or of Platform Terms, including any action a Platform takes against APIWings as a result. We will defend and indemnify you against third-party claims that the Service, used as permitted, infringes their intellectual property rights.

16. Data protection

Our handling of personal data is described in the Privacy Policy. Where we process End User personal data on your behalf, the Data Processing Agreement in Annex A applies and you are the controller. You are responsible for having a lawful basis to publish on your End Users' behalf and for informing them.

17. Governing law and disputes

These Terms are governed by the laws of Spain. Any dispute will be submitted to the courts of Barcelona, Spain, except that consumers may bring claims in their own jurisdiction where the law so provides. Before starting proceedings, the parties will try in good faith to resolve the dispute by discussion for 30 days.

18. Changes to these Terms

We may update these Terms. We will post the new version at apiwings.com/terms with its effective date and notify you by email at least 15 days before material changes take effect. Continued use after that date means acceptance; if you do not agree, cancel your account before the changes take effect.

19. General

These Terms, the Privacy Policy, the pricing page and Annex A are the entire agreement between us. If any provision is unenforceable, the rest remains in effect. You may not assign these Terms without our consent; we may assign them to a successor of our business. Legal notices to us go to hello@apiwings.com; technical support requests go to support@apiwings.com; notices to you go to the email on your account.

20. Contact

Annex A — Data Processing Agreement

This Annex applies to personal data of End Users that APIWings (“Processor”) processes on behalf of the Customer (“Controller”) under the Terms, in accordance with Article 28 GDPR.

A1. Subject matter and duration. Processing is limited to connecting End Users' Platform accounts, publishing content to them and reporting results, for as long as the Customer uses the Service.

A2. Nature and purpose. Storage of encrypted access tokens and account identifiers; transmission of content to the Platforms selected by the Controller; storage of publication results; delivery of webhooks.

A3. Categories of data subjects and data. End Users of the Controller's application. Data: Platform account identifiers and handles, access and refresh tokens (or app passwords for Bluesky), post content and media, publication results and error messages, quota information.

A4. Controller's instructions. The Processor processes personal data only on the Controller's documented instructions, which are the Terms, the API requests the Controller sends, and the dashboard settings. The Processor will inform the Controller if an instruction infringes data protection law.

A5. Confidentiality. Persons authorised to process the data are bound by confidentiality obligations. Access to production systems is limited to the Processor's founders and engineers on a need-to-know basis.

A6. Security. The Processor implements the measures described in Section 7 of the Privacy Policy, including encryption of tokens at rest with per-profile keys managed by AWS KMS, encryption in transit, private networking, hashed API keys, signed webhooks, tenant isolation tests and secrets management.

A7. Sub-processors. The Controller authorises the sub-processors listed in Section 8 of the Privacy Policy. The Processor will notify the Controller by email at least 15 days before adding or replacing a sub-processor; the Controller may object on reasonable data protection grounds within that period, in which case the parties will discuss in good faith and the Controller may terminate the Service if no solution is found. The Processor remains liable for its sub-processors.

A8. Data subject requests. The Processor will forward to the Controller any request received from an End User and will assist the Controller in responding, including by disconnecting accounts and deleting data on request.

A9. Assistance. The Processor will assist the Controller with security, breach notification, data protection impact assessments and consultations with supervisory authorities, to the extent the Controller cannot do so from the information already available.

A10. Personal data breaches. The Processor will notify the Controller without undue delay, and in any case within 48 hours of becoming aware, of a personal data breach affecting the Controller's data, with the information required by Article 33(3) GDPR as it becomes available.

A11. Deletion and return. On disconnection of an account, deletion of a Profile or termination of the Terms, the Processor deletes the personal data concerned within the periods stated in Section 11 of the Privacy Policy, unless retention is required by law. Publication records without content may be kept for 13 months for billing.

A12. Audits. The Processor will make available the information necessary to demonstrate compliance and allow audits by the Controller or an independent auditor once per year on 30 days' notice, during business hours, subject to confidentiality. Where the Processor holds a current third-party certification or audit report (for example SOC 2), it may provide that report in satisfaction of this obligation.

A13. International transfers. Transfers outside the EEA take place only to sub-processors covered by an adequacy decision, the EU–US Data Privacy Framework or Standard Contractual Clauses, as described in Section 9 of the Privacy Policy.

A14. Precedence. In case of conflict between this Annex and the Terms, this Annex prevails for the processing of personal data.