Terms of Service

These terms are an agreement between you and ZenTalk LLC, Houston, Texas, United States ("we", "us"), which operates AppForShare at appforshare.io. By uploading a build, creating an account or buying a plan you accept these terms and our Privacy Policy. If you use AppForShare for a company, you accept them on its behalf and confirm you are allowed to.

You must be at least 13 years old (16 in the EEA and UK), and old enough to enter a contract where you live to buy a plan.

AppForShare stores iOS and Android builds you upload and gives you install links, QR codes, analytics and tools for teams and testers. It is meant for testing and internal distribution, not for replacing the App Store or Google Play. Whether an iOS build installs on a device depends on how you signed it; we cannot change Apple's or Google's rules.

Give us accurate details and keep your password and API tokens private. You are responsible for what happens under your account, including uploads made with your tokens and actions of team members you invite. Tell us at [email protected] if you think your account has been misused.

You keep all rights to the builds, icons, notes and other content you upload. You give us a limited licence to store, process, copy and deliver that content only as needed to run AppForShare for you, for example to read the app details, make the install page and send the file to the people you share the link with. This licence ends when the content is deleted, apart from copies in short lived backups.

You confirm you have the right to upload and distribute everything you share, including any third party code, names and logos. Anyone with a public install link can download the build; use a password or private tester access when a build should not be public.

On the Team plan you can hide AppForShare and show your own name, logo and links on install pages and in the emails your testers get. When you do, you are responsible for telling the people who open those pages or get those emails who you are and how their data is handled, for example by adding a link to your own privacy policy. You may not use this to pose as another company. We still handle their data as our Privacy Policy describes, and a report about an app may still open on AppForShare.

You may not use AppForShare to:

• share malware, spyware, or apps that collect data from people without their clear consent;
• share cracked, pirated or modified copies of apps you do not own, or anything else that infringes someone's rights;
• phish, impersonate another app, person or company, or mislead people about what an app does;
• distribute illegal content, or apps that facilitate gambling, adult content or other activity where it is unlawful;
• use AppForShare as a general file host or CDN, or work around plan limits, link expiry or bot checks;
• attack, overload, scrape or probe the service, or access other users' data.

Anyone can report an app with "Report this app" on its install page. Rights holders can also write to [email protected] with the link, the work concerned and their contact details. We may remove builds, disable links, or suspend or close accounts that break these rules, usually with notice by email unless that would be unsafe or unlawful.

When someone reports a build, they must say why. We check each report with an automated review of the report and the build's details, and a person on our team makes the final decision. A build without an account or on a Free account stops taking installs while we check a report, and its owner is told by email. A build on a Pro or Team plan keeps working; its owner gets an email for each report, and the build stops taking installs while we check once five different people have reported it. Uploads without an account that ask for a set of permissions often used to watch a phone without its owner knowing are held the same way until a person checks them. A file we removed for abuse is refused if it is uploaded again.

Each plan has limits on file size, storage, monthly downloads and how long links stay up, shown on the pricing page. Links made without an account or on the Free plan expire; expired and deleted builds are removed after a short grace period. When an account reaches its download limit, downloads may pause until the next month unless the plan is upgraded or more bandwidth is added. We may change free limits at any time.

The store readiness check compares your build with App Store and Google Play rules as we understand them at the time. It is guidance, not a promise that Apple or Google will accept your app, and store rules change. AI fix plans, release note drafts and review reply drafts are written by a machine from your build details and can be wrong or incomplete, so review them before you use them. Each plan includes a number of AI actions a month, shown on the pricing page.

You can connect an App Store Connect API key or Google Play access to AppForShare. When you do, AppForShare acts as your service provider and uses that access only on your behalf, only for the apps you choose, and only for the actions you or people you authorize start in AppForShare. We keep the key confidential, encrypted, and never share it, and we hold ourselves to terms at least as protective of Apple and Google as your own agreements with them. You stay responsible for your developer accounts and for what is done with them, including by people you invite.

While an app is shared, AppForShare checks its release status on a schedule. For Apple apps it also adds a webhook named "AppForShare release status" to that app in App Store Connect, so Apple can tell us about review and build changes, and removes it when you stop sharing the app or disconnect. These checks only read; they do not change your listings or releases.

AppForShare also collects the customer reviews of shared apps. A reply is posted to the store only when a person in your workspace presses Post reply, never by AI on its own, and it appears publicly under the review. You are responsible for what your replies say and for following Apple's and Google's rules for review responses.

If you link a tester group to a TestFlight group, AppForShare adds the group's members to that TestFlight group with their email address and name, and takes out the ones it added when they leave your group, until you stop syncing. Testers someone added in App Store Connect are not removed. A build is given to the group, or submitted for TestFlight beta review, only when a person in your workspace presses the button, or when an Admin asked for it on that build's Send to TestFlight (then it is done once Apple has processed the build). You are responsible for having your testers' permission to share their email address with Apple.

A device is registered on your Apple developer account, and an ad hoc or development profile is made again, only when a person in your workspace presses the button. Apple limits how many devices each account can register per membership year and does not give a slot back when a device is disabled; that use cannot be undone by AppForShare. Remaking a profile replaces the old one in your account.

AppForShare does not re-sign the .apk files you upload, and never re-signs a build for the App Store. On Pro and Team, an iOS build you uploaded is re-signed with a provisioning profile only when a person in your workspace asks for it, or, on Team, when an Admin turned on Hands free for that project and it has no GitHub build. The re-signed build is saved as a new build; the build you uploaded is not changed. Re-signing uses the signing certificate and password an Owner or Admin of your workspace adds. You confirm you may use that certificate and the profiles you choose. AppForShare uses the certificate only to re-sign your own workspace's builds, never shares it, and deletes it at once when it is removed.

An .aab you upload is turned into one APK for testers with Google's bundletool and signed by AppForShare: with a test key AppForShare makes for your workspace, or, on Pro and Team, with the upload keystore an Admin of your workspace adds. You confirm you may use that keystore. An APK signed with the test key cannot update the app installed from Google Play. AppForShare uses your keystore only to sign APKs made from your own .aab uploads, never shares it, and deletes it at once when it is removed.

App Store listing text and screenshots are changed, a language is added or a new version is started only when a person in your workspace saves or presses the button. Changes to a version being prepared reach the App Store after Apple's review; a new promotional text on the live version shows at once. AI translations are suggestions: you are responsible for what your listing says, in every language, and for following Apple's rules for it.

An App Store version is sent for review, taken out of review, released or has its phased release changed only when an Admin of your workspace presses the button, with your own App Store Connect key and in the name of your Apple developer account; we keep who did it. AppForShare never sends a version on its own and does not submit apps on your behalf. You answer Apple's questions (export compliance, App Review contact and sign in details) and you are responsible for the answers, for the app and for following the App Store Review Guidelines and your agreements with Apple. Apple decides on every review.

Google Play listing text and graphics are changed, or a language is added or removed, only when an Admin of your workspace saves or presses the button. Google Play has no draft version, so each change is committed to your Google Play account at once, goes to Google's review and then shows on Google Play. AppForShare does not cancel changes that are already in review. You are responsible for what your listing says and shows, in every language, and for following Google Play's policies for it.

On the Google Play releases page, release notes, promotions between tracks, rollout percentages, halting, resuming and completing a rollout, and the testers of a track change only when an Admin of your workspace confirms the change. Each one is committed to your Google Play account at once with your connection. AppForShare never rolls out, halts or completes a release on its own and does not watch your app's quality data. You decide how and when your app reaches users, and the results of a release are yours.

GitHub builds run only in repositories where your workspace installed the AppForShare Builds app, on that repository's own GitHub Actions minutes, under your GitHub account's terms and billing. When an Admin of your workspace sets up a repository, the App Store Connect key they pick and an upload token are stored as encrypted Actions secrets in that repository; anyone who can change its workflows can use them, so set it up only in repositories you trust. AppForShare proposes the workflow in a pull request and never pushes to your branches or merges; it starts a build only when a person presses the button, and removes the secrets and revokes the token when the setup is removed. With signing by your own certificate, AppForShare reads the provisioning profile of the app from Apple before each build with your key, makes one when none exists, and stores it as an Actions secret. For Android, only an upload token is stored in the repository; your upload keystore stays in secrets you add yourself, and AppForShare does not receive it. When an Android build goes to Google Play, the run uploads the app bundle straight to Google Play into an edit AppForShare opens with your workspace's Google Play connection, and AppForShare releases it on the track you picked; a production release is always left as a draft for you to roll out. Setups made before 1 November 2026 send the bundle through AppForShare, which does not keep it after it is handed to Google Play. You are responsible for your code, the workflow and what it builds.

Create keys with the least access you need, never with the Admin role. If you connect your account to someone else's workspace through an invite link, they can use it for the apps you shared until you disconnect. Disconnecting deletes the key from AppForShare at once; revoking the key itself is done in App Store Connect or Play Console. Apple and Google can change or limit their APIs at any time, and we are not responsible for what their services do or refuse.

If you add a client to a project, we email them a sign in link and show them, in the client portal, the tasks and comments you mark as visible to the client, your deliveries and their feedback. You choose who your client is and what you share with them, and you are responsible for having the right to share it and for your agreement with your client. The client can install the project's builds and download the files you deliver. Removing the client ends their access at once; what they already downloaded stays with them.

You can ask your client to sign agreements and version sign-offs in the portal. You write the agreements; AppForShare writes the sign-off text from the version. We record the signature with the exact text, the signer's details, the email address their sign in link proved, their IP address, browser and the time, and produce a signed PDF for both of you. AppForShare is not a party to your agreement and does not give legal advice; whether an electronic signature is valid for your agreement depends on the law that applies to it, and you are responsible for that choice. Signed documents cannot be changed; a revoked signature stays on record. Signed PDFs and evidence reports carry a document seal with a certificate AppForShare issues itself; the seal and the public check page show whether a file was changed after we issued it, nothing more. While a document waits for a signature, we email your client up to two reminders on your behalf.

Paid plans are billed in advance, monthly or yearly, through Stripe, and renew automatically until cancelled. Prices are shown before you pay and may exclude taxes, which are added where required. Upgrades and seat changes are prorated.

Your first Pro subscription may start with a free trial, shown at checkout. You add a card when the trial starts and nothing is charged during it; when it ends the plan is charged and renews as above, unless you cancelled before. We email you before the trial ends. One trial per account and per card: if the card already had a trial on another account, the plan starts without one.

In some countries we offer lower regional prices. They apply to cards issued in those countries. If your card was issued elsewhere, your plan moves to the standard price from the next payment (or from the end of the trial), we email you when that happens, and you can cancel before it applies.

You can cancel at any time, with no fee, from Dashboard, Billing. Cancelling stops the next renewal; your plan and its paid features stay active until the end of the period you have paid for, then your account moves to Free and Free limits apply to your links. Payments are not refundable, including partly used periods, except for billing mistakes on our side or where the law requires it. The details are in our Refund and Cancellation Policy, which is part of these terms. If we change the price of your plan we will email you at least 30 days before it applies to you. If a payment fails, paid features may stop until it is fixed.

On the Free plan you can also make a one time payment that keeps one build's install link live for a set time (currently $2 for 60 days from the payment). It is not a subscription and does not renew, applies only to that build, and ends early if you delete the build or we remove it under these terms.

We work to keep AppForShare running and your files safe, but we do not promise it will always be available or free of errors, and you should keep your own copies of your builds. We may change or end features; if we end a paid feature you rely on, we will give reasonable notice and a prorated refund for time you have paid for and cannot use.

You can stop using AppForShare at any time and ask us to delete your account at [email protected]. We may suspend or close an account that breaks these terms, puts other users at risk, or has unpaid charges. Sections on content rights you gave us before closure, payments owed, disclaimers, liability and disputes continue after the agreement ends.

AppForShare is provided "as is" and "as available". To the extent the law allows, we disclaim all implied warranties, including merchantability, fitness for a particular purpose and non infringement.

To the extent the law allows, we are not liable for indirect, incidental, special or consequential losses, or for lost profits, revenue or data. Our total liability for any claim about AppForShare is limited to the greater of the amount you paid us in the 12 months before the claim arose and 100 US dollars. Nothing in these terms limits liability that cannot be limited by law.

You will cover us against claims from third parties arising from content you upload or from your breach of these terms.

These terms are governed by the laws of the State of Texas, United States, without regard to conflict of law rules. Disputes go to the state or federal courts in Harris County, Texas, unless the law where you live gives you the right to bring them locally. Please write to [email protected] first; most problems are solved faster that way.

We may update these terms. We will change the date above and, for significant changes, email account holders at least 14 days before they apply. Continuing to use AppForShare after that means you accept the new terms.