Legal & Beta Status

Effective date: July 2026 · Controlled beta stage

Beta legal copy. These documents are suitable for the controlled beta evaluation period. They should be reviewed and replaced by solicitor-approved terms before Amplifyr is made publicly available in a commercial capacity.

Controlled beta status

The table below shows the current availability of each Amplifyr feature area. This is updated as the beta progresses.

Area	Beta status	User expectation
Content generation	Available	User reviews and approves every draft before it reaches Queue or Calendar.
Finalised Engine	Available	User can review, approve sections, or flag items for change.
Queue / Calendar	Available	Truthful scheduled / blocked / failed states shown. No post publishes without a connected account.
External publishing (X/Late)	Not connected until user links account	Requires a connected X account via Settings → Connections before any real post is sent.
DM / outreach	Strategy review only — no live sending	DM flow and approval UI are reviewable. No DM will be sent until the sending backend is explicitly enabled.
Image generation	Workflow present — provider not enabled unless configured	Image panel visible but disabled. No image is generated or published unless the provider is configured.
Billing / payments	Architecture present — not live unless provider configured	No checkout or subscription enforcement unless BILLING_ENFORCEMENT_ENABLED is explicitly set. Beta workspaces are uncapped.
Analytics / results	Available when data exists or is imported	Empty states are normal before posts are published and the analytics extension is connected.
Optimisation approval	Future direction — not implemented yet	No backend proposal or approval system in this build. AI insights are informational only.

Beta disclaimer

Amplifyr is currently in a controlled beta. Features, pricing, data practices, and availability may change before public commercial launch.

This is beta-stage legal copy and should be reviewed by a qualified solicitor or attorney before Amplifyr is made publicly available in a commercial capacity.

Beta workspaces are provided for evaluation purposes. We reserve the right to change features, adjust access, or deprecate parts of the platform with reasonable notice.

AI and content disclaimer

Amplifyr uses AI to assist with drafts, strategy recommendations, content suggestions, and campaign planning. You are responsible for reviewing and approving all content before use.

Amplifyr does not guarantee reach, engagement, leads, clients, revenue, platform ranking, or virality.
AI-generated content may contain errors, inaccuracies, or outputs that are unsuitable for your specific context.
You must ensure all content is accurate, lawful, and appropriate for your business and audience before publishing.
Do not publish regulated claims (financial, medical, legal, etc.) without review by a qualified professional.
Amplifyr does not review published content on your behalf and bears no responsibility for content you choose to publish.

Publishing and social account disclaimer

External publishing requires a connected provider account (e.g. X/Twitter via Late). No post is published unless you connect an account and explicitly schedule it through Queue or Calendar.

Publishing is only confirmed when the external provider returns a success response. Failed or blocked states appear truthfully in the interface.
You are responsible for all content published from your connected accounts.
You must comply with the terms of service of each platform you connect (including X/Twitter).
Amplifyr must not be used to spam, impersonate, mislead, evade platform rules, or post content at volumes that violate platform policies.
Failed or blocked publishing states may require manual intervention from you.

DM and outreach safety

DM sending is not enabled in this beta build. The DM strategy and approval flow are fully reviewable, but no message will be sent until a sending backend is explicitly configured and enabled.

Reviewing the DM Engine or approving a DM strategy does not trigger any live sending in the current build.
Any future DM workflow will be approval-led, rate-limited, and limited to handles that have engaged with the org's own published content.
Amplifyr must not be used for spam, scraped-contact blasts, deception, impersonation, harassment, or unsolicited mass messaging.
Any DM should be personalised, contextually relevant to prior engagement, and clearly not an automated mass outreach.
You are responsible for complying with applicable laws governing electronic direct messaging in your jurisdiction.

Billing and payment disclaimer

Amplifyr's billing architecture supports Stripe and Lemon Squeezy. Live checkout and subscription enforcement are not active unless a provider is explicitly configured.

Beta workspaces are uncapped and not subject to paid plan enforcement unless billing enforcement is explicitly enabled.
No live checkout or subscription charge will occur without a configured billing provider and an intentional user action.
Billing configuration is visible in Settings → Billing. If the provider is not configured, that tab will say so clearly.
When live billing is enabled, pricing, plan limits, and refund terms will be communicated before any charge is made.
This notice is not a binding commitment to any specific pricing or plan structure before commercial launch.

Privacy statement

This is a plain-language summary of how Amplifyr handles your data during the controlled beta. A full Privacy Policy will be published before commercial launch.

Account data

Email address and authentication credentials are managed via Supabase Auth. Passwords are hashed; we do not store plaintext credentials.

Workspace and organisation data

Strategy profiles, voice profiles, offers, content pillars, and campaign configuration are stored in a Supabase (Postgres) database associated with your organisation.

Generated drafts and content

AI-generated drafts, ideas, and approved content are stored in your workspace database. You own the content you create or approve.

Connected social account data

When you connect an X account via Late, an OAuth token is stored to authorise publishing on your behalf. We do not store your social platform password.

Analytics and performance data

If you use the analytics browser extension, imported post metrics are stored in your workspace. We do not scrape public social data on your behalf.

Billing provider data

If billing is enabled, payment processing is handled by Stripe or Lemon Squeezy. We do not store card numbers. Subscription state is synced from the provider.

Uploaded documents (RAG)

If you upload documents for RAG/knowledge ingestion, those files are processed and stored as embeddings in your workspace context. We do not use your documents to train shared models.

Support and debug logs

Server-side logs may capture API errors and request metadata for debugging. These are not used for profiling or advertising.

To request deletion of your workspace data during the beta, contact the team directly.

Acceptable use policy

By using Amplifyr you agree not to use the platform for any of the following:

Spam, unsolicited mass messaging, or automated contact of any kind without prior engagement or consent.
Illegal content, including content that violates copyright, defames individuals, incites harm, or breaches applicable laws.
Harassment, threats, abuse, or targeted intimidation of individuals or groups.
Impersonation of any person, company, or entity in a deceptive or misleading way.
Deceptive automation — using Amplifyr to create a false impression that content is human-authored when it is not, without appropriate disclosure.
Platform abuse — violating the terms of service of any platform you connect (including X/Twitter) through actions taken via Amplifyr.
Publishing content you do not have the rights to use, including copyrighted text, images, or trademarks.
Publishing regulated claims (financial advice, medical advice, legal advice, etc.) without appropriate professional review and disclaimers.
Using Amplifyr to evade platform restrictions, bans, or rate limits.

We reserve the right to suspend or terminate beta access for violations of this policy.

Terms of service (beta)

These are brief terms for the Amplifyr controlled beta. Full commercial terms will be published before public launch.

Access. Beta access is granted by invitation only and may be withdrawn at any time. You may not transfer, resell, or grant sub-licences to your beta access.

Licence. Amplifyr grants you a limited, non-exclusive, non-transferable licence to use the platform for evaluation purposes during the beta period.

Your content. You retain ownership of all content you create, upload, or approve using Amplifyr. You grant Amplifyr a limited licence to process that content to deliver the service.

No warranties.The beta is provided "as is". Amplifyr makes no warranties regarding uptime, accuracy, fitness for purpose, or continued availability of any feature.

Limitation of liability. To the maximum extent permitted by law, Amplifyr is not liable for indirect, incidental, or consequential losses arising from your use of the platform, including any publishing errors, content inaccuracies, or loss of social account access.

Changes. We may update these terms at any time. Continued use of the beta after notice of changes constitutes acceptance.

Governing law. These terms are governed by English law. Any disputes will be subject to the exclusive jurisdiction of the courts of England and Wales.