Terms of Service

By accessing or using ipafy, you agree to be bound by these Terms of Service and by the Privacy Policy. If you do not agree, do not use the service.

ipafy is a build automation service. Given a project archive and the configuration you supply, ipafy produces an iOS application archive (IPA file) and, when you enable it, delivers that build to one or more destinations on your behalf. Optional capabilities include activating your game engine's editor license and uploading the resulting build to Apple App Store Connect or to any additional delivery destination enabled for your account.

ipafy is a developer tool. It does not distribute your builds anywhere other than the destinations you configure, and it does not make changes to your third-party accounts beyond the upload you explicitly request.

You are responsible for keeping your account credentials confidential and for all activity that occurs under your account. If you believe your account has been used without your authorization, contact support so that we can help you secure it.

You must be at least the age of majority in your jurisdiction to use the service. If you are using ipafy on behalf of an organization, you represent that you have authority to bind that organization to these terms.

You retain all rights in the project source code, assets, and configuration you upload to ipafy. You grant the operator a limited, non-exclusive, royalty-free license to host, copy, process, and execute that content for the sole purpose of running the build you requested and delivering the results where you asked.

You are responsible for:

• ensuring that you have the right to upload, build, sign, and distribute anything you submit to the service;
• the validity and authority of the credentials you provide (App Store Connect API keys, game engine editor credentials, and similar);
• the accuracy of the configuration you submit, including Bundle IDs, version numbers, and any metadata that will appear on third-party platforms.

For each build, you choose which destinations to enable and which credentials to supply. By enabling a destination, you authorize ipafy to act as your agent and to interact with that destination on your behalf, using the credentials you provided, solely to perform the action you requested. The operator does not act outside of that authorization.

• Apple App Store Connect. When you enable App Store Connect delivery, you authorize ipafy to use the App Store Connect API key, Key ID, and Issuer ID you supply to upload the resulting build to the App Store Connect record matching the Bundle ID you specified. The service does not change your app metadata, pricing, availability, App Store review status, or any other App Store Connect resource. It reads only the information it needs to confirm that the upload succeeded.
• Game engine editor license activation. When you enable engine editor activation, you authorize ipafy to sign in to your game engine's licensing service on your behalf with the engine account credentials you supply, solely to activate the editor for the duration of your build. The credentials are not used for any other purpose and are not retained after the build completes.

You may revoke this authorization at any time by removing the relevant credentials from your build configuration or by rotating those credentials at the third-party platform. Once a credential has been removed or rotated, the operator can no longer use it.

You remain solely responsible for complying with the terms of every third-party platform you direct ipafy to interact with, including the Apple Developer Program License Agreement, the App Store Review Guidelines, and your game engine's software licence terms.

To meet the technical requirements of certain distribution destinations, and to produce a build that is distinct at the binary level on each release, the service applies a series of automated transformations to your project before producing the IPA. At a high level, those transformations may:

• regenerate internal identifiers used by the engine and the Apple toolchain, so that two builds of the same project are not byte-identical;
• substitute or reorder internal names and structural elements that do not affect the documented behavior of your application;
• adjust embedded metadata and resource layout to satisfy the per-build uniqueness checks of platforms that require them.

By starting a build, you authorize the operator to apply these automated transformations to your project for the sole purpose of producing the build you requested. The transformations are limited to the modifications described above and are not used to alter the documented behavior of your application.

These transformations are automated and best-effort. They are designed to leave the observable behavior of your application unchanged, but the operator does not, and cannot, guarantee that every transformed build will run correctly, that every transformed build will be accepted by every distribution destination, or that a transformed build will behave identically to a build produced without the transformations. You are solely responsible for testing each build before publishing or distributing it, and your use of any build produced by the service is at your own risk.

The project source, credentials, and build artifacts you provide to or generate through the service are stored in encrypted form at rest, transmitted over TLS-encrypted connections, and scoped to your account. They are used solely to operate the service for you and to perform the actions you authorized. The Privacy Policy describes the categories of data handled by the service, the safeguards applied to that data, and your rights with respect to it.

You agree not to use ipafy to:

• build, sign, or distribute software that you do not have the right to distribute;
• attempt to gain unauthorized access to the service, its infrastructure, or other users' data;
• interfere with the operation of the service, including by submitting builds designed to exhaust resources or to extract secrets from the build environment;
• upload malware, illegal content, or content that violates the intellectual property or privacy rights of others;
• circumvent the rules of any third-party destination, including the Apple App Store Review Guidelines, or use the service to misrepresent the origin or authorship of an application.

The operator may suspend or terminate access if a build or a pattern of builds breaches these rules.

The ipafy service, including its software, design, and documentation, is owned by the operator and is protected by intellectual property laws. These terms do not grant you any rights in the service beyond those required to use it as intended.

Feedback you send to the operator about the service is not confidential, and the operator may use it to improve the service without obligation to you.

ipafy relies on infrastructure providers to host the service, run builds, store data, and deliver transactional email. It also interacts on your behalf with the third-party platforms you explicitly enable, including Apple App Store Connect and your game engine vendor, and offers Telegram and Google as sign-in options. Your use of those platforms is governed by their own terms, and the operator of ipafy is not responsible for their availability, behavior, or actions. You are responsible for complying with the terms of any third-party platform that you direct ipafy to interact with on your behalf.

To operate the service, we may route certain outbound traffic to Apple services, including App Store Connect, through third-party network infrastructure. We select this infrastructure and manage how the service uses it to provide the network-isolation features described in our Privacy Policy.

The service is provided on an "as is" and "as available" basis, without warranties of any kind, whether express, implied, or statutory, including warranties of merchantability, fitness for a particular purpose, and non-infringement. The operator does not warrant that the service will be uninterrupted, that builds will always succeed, that artifacts will be free of defects, that the uniqueness transformations described above will leave every application functioning correctly, or that third-party platforms will accept the builds the service produces.

You are solely responsible for testing and verifying every build before publishing or distributing it. Use of any build produced by the service is at your own risk.

To the maximum extent permitted by law, the operator of ipafy will not be liable for indirect, incidental, special, consequential, or punitive damages, or for any loss of profits, revenue, data, goodwill, or other intangible losses, arising out of or related to your use of the service or of any build produced by it. This limitation applies regardless of the legal theory under which the claim is brought.

To the maximum extent permitted by law, the total aggregate liability of the operator in connection with the service is limited to the greater of (a) the amount you paid to the operator for the service in the twelve months preceding the event giving rise to the claim, and (b) one hundred United States dollars.

You may stop using the service at any time. The operator may suspend or terminate your access to the service if you breach these terms, if continuing to provide the service to you would create a material risk to others or to the operator, or if required by law. Where reasonable, we will notify you before termination.

Sections of these terms that by their nature should survive termination (including those covering intellectual property, disclaimers, limitation of liability, and governing law) will continue to apply after your access ends.

We may revise these terms from time to time. Material changes will be reflected by an updated date at the top of this page. Your continued use of the service after a change indicates acceptance of the revised terms. If you do not accept the revised terms, you must stop using the service.

These terms are governed by the laws of the operator's primary country of business, without regard to its conflict of laws principles. Disputes will be brought before the competent courts of that jurisdiction, except where mandatory consumer protection laws of your country of residence grant you the right to bring proceedings in a different forum.

Questions about these terms can be sent to support.