Here's what you need to know about using xllify during the beta period. By using the service and compiled artifacts, you accept the below terms.

• 1. We're in (early) beta. This means we're still testing, improving, and occasionally breaking things. The service is provided "as is" without warranties of any kind, express or implied.
• 2. No guarantees. We will do our best to keep xllify running smoothly, but we can't guarantee uptime, availability, or that everything will work perfectly all of the time.
• 3. Third-party dependencies. xllify relies on third-party services including GitHub and Google Cloud Platform. We make use of Firestore, Firebase Authentication, and Google Cloud Storage. Services and data are hosted in the europe-west1 GCS region. Builds are performed within your own GitHub user or organization using GitHub Actions, and are entirely under your control. If third-party services experience outages or degraded service, xllify may be affected too. We will keep you updated on our status page. Note that downloaded artifacts have no reliance on any service other than the machine they're running on.
• 4. No liability. We're not responsible for any damages, data loss, errorneous calculations, business interruption, or other losses arising from your use (or inability to use) xllify. Please test your work thoroughly before deploying to production. xllify is a developer-oriented tool - it is assumed that you are proficient and understand how to use GitHub Actions, Excel and can figure out how to use the service independently. We're new though, so there might be bugs. We're on-hand to support you through xllify issues and issue fixes.
• 5. Your code is your code. You're responsible for the Luau code you submit and the add-ins you create. If the workbooks you use the functions in are insane, xllify won't fix that. We cannot support your use of Microsoft Excel. This is not an official service provided by Microsoft, nor is it endorsed by them. They've probably not even heard of us.
• 6. Best effort support. We provide support on a best effort basis. We'll do our best to help, but response times aren't guaranteed during the beta period. Our support covers xllify itself, not general computer operation or how to use third-party tools.
• 7. Beta builds expire. During the beta period, builds expire after three months. This is common practice to ensure you're always using the latest version with quality improvements and new features. Simply rebuild to get a fresh version good for another three months.
• 8. Beta timeline is flexible. We can't guarantee when the beta period will end or when paid offerings will become available with all slated features. We'll keep you updated via our blog and notify beta users directly.
• 9. Things may change. Features, pricing, and terms may change as we develop xllify. We'll give you notice of significant changes, but this is beta after all!
• 10. We respect your IP. Your code belongs to you. We compile it into a format that works with Excel, but we never claim ownership of it. We may store your compiled code and built files to keep the service running, but we won't share them with anyone. You can request we delete all of your data at any time.
• 11. Behave yersel. Don't abuse the service, attempt to overload or hack it, or use it for anything illegal or malicious. Please and thank you. We reserve the right to terminate accounts that do this.
• 12. AI code assistance. AI-generated code should be given close scrutiny before use, and we make no guarantees as to its correctness, security, or suitability for any particular purpose.
• 13. GitHub Actions costs. Builds run on GitHub Actions using a windows-latest runner, which incurs costs according to GitHub's pricing. These costs are your responsibility and will be billed to your GitHub account according to your plan. GitHub offers free minutes on both public and private repositories, though windows-latest runners consume minutes at a 2x rate compared to Linux runners - but that said, most builds run in around 30 seconds, so you will only use a minute per build! Please review GitHub's pricing before using xllify.
• 14. Packaged binaries and open source. The xllify GitHub Action uses packaged binaries that are licensed for use within GitHub Actions. No source code is provided. The build process makes use of open source software - see the credits and licenses for details.
• 15. UK law applies. These terms are governed by the laws of England and Wales. Lexvica Limited (trading as Acornsoft UK) is registered in England and Wales (company number 16315473). We have no affiliation with any third party organisations mentioned throughout this site. Mention != endorsement on either side.

Last updated: 11 October 2025