Privacy policy

Who we are

SwiftLambda is a service for compiling and running short-lived Swift programs from a Git repository. This policy covers the SwiftLambda website at swiftlambda.com, the web console, and the SwiftLambda HTTP API. It explains what personal information we handle and the choices you have about it.

"Personal information" here means information that relates to an identified or identifiable person — your email address, for example, or an identifier a tracking tool assigns to your browser.

What we collect

Three categories, and nothing else:

• Account information you give us. Your name, email address, and a password. Passwords are stored only as a salted hash — we cannot read yours, and password resets go out from noreply@swiftlambda.com as one-time links.
• What you build and run. If you connect a GitHub account, we store the access token that connection issues and the repository you select, so we can fetch your code and compile it. We store the lambda projects you create, their build output and status, the runs you start, the logs those runs produce, and any API keys you generate. Run logs are whatever your own program writes to standard output — if your code logs personal data, that data lands in your logs.
• Technical information collected automatically. When you load a page, our analytics and advertising tools receive your IP address, browser and device type, referring page, the pages you visit, and how you interact with them. This is the category the next section itemizes in full.

We do not ask for your phone number, your postal address, or your location, and we do not buy personal information about you from data brokers. Card details are entered on Stripe's hosted checkout and are never sent to or stored by SwiftLambda — we receive only the subscription status that results.

Analytics and advertising

SwiftLambda loads four third-party tools in the browser. Each one is operated by a company other than us and receives your IP address and browsing activity on this site when it runs:

• Matomo (hosted Matomo Cloud, operated by InnoCraft Ltd, New Zealand) — product analytics. Records page views, sign-ups, and in-product events so we can see which parts of SwiftLambda get used. This is our primary analytics tool.
• Google Analytics 4 (Google LLC), measurement ID G-0DX7VG3GZQ, loaded via googletagmanager.com/gtag/js — audience and traffic analytics covering the same page views and events.
• Google Ads conversion tag (Google LLC), conversion ID AW-655945723, loaded by the same Google tag — advertising measurement. Tells us which Google ads led to a sign-up or a purchase, and lets Google build advertising audiences.
• Meta Pixel (Meta Platforms, Inc.), dataset ID 1506026001279031 — page views and conversion measurement for Facebook and Instagram advertising. This dataset is shared with another site we operate, audioproducer.ai; the two are distinguished by the address of the page the event came from.

We use these to understand traffic and to measure advertising. We do not sell personal information, and we do not upload your email address or other account details to any of these tools. Google and Meta act as independent controllers of the data their tags collect and use it under their own policies, which are linked in Your choices and rights below.

Cookies and local storage

Cookies and similar browser storage are used for two different purposes here, and they are worth separating:

• Strictly necessary. Your login session, and a local preference for the light or dark theme. Without these you cannot stay signed in. These are set by us, not by a third party.
• Analytics and advertising. Set by the four tools above to recognize a returning browser and attribute a conversion. These are not necessary to use SwiftLambda.

These are the actual cookies involved. If this table and the site ever disagree, the table is the bug — tell us and we will fix it.

To be straightforward about the current state: SwiftLambda does not show a cookie-consent banner, so analytics tools load on page load. The two advertising tools are different — they are gated on the opt-out control in Do not sell or share below, and they never load for a browser that has opted out or that sends Global Privacy Control. We honor GPC; we do not act on the older and largely abandoned "Do Not Track" header.

How we use it

• To run the service. Authenticating you, fetching and compiling the repository you connected, executing your runs, showing you logs, and enforcing the limits of your plan.
• To support you. Answering questions you send us and investigating failures — which sometimes means reading the build or run logs on your account.
• To bill you. Only if you subscribe to a paid plan.
• To improve and market the product. Understanding which features are used, and measuring whether an ad campaign worked. This is the purpose the analytics and advertising tools serve, and it is the one you can opt out of without losing any functionality.
• To meet legal obligations and to investigate abuse of the compute we provide.

We do not use your source code, your build output, or your run logs to train machine-learning models, and we do not share them with anyone except the infrastructure providers named below who process them on our behalf.

Who we share it with

We do not sell personal information. We share it only with the following categories of recipient:

• Service providers who process data for us. Our cloud hosting and compute providers (which store your account, code, builds, and logs), Stripe for payment processing, and Matomo Cloud for analytics hosting.
• GitHub, when you connect a repository — we call GitHub's API with the token you authorized, on your behalf.
• Google and Meta, through the advertising and analytics tags described above.
• Law enforcement or other parties where we are legally required to, or where it is necessary to protect our rights, our users, or the safety of the service.
• A successor, if the service is ever sold, merged, or otherwise transferred. You would be notified before your information became subject to a different policy.

Retention

We keep your account information for as long as your account exists. Delete your account and we delete the account record, the connected GitHub token, your lambda projects, and their builds and logs; backups containing them age out afterwards on our ordinary backup cycle. Records we are required to keep for tax or accounting reasons — invoices, chiefly — are retained for as long as the law requires, regardless of account deletion.

Analytics and advertising data is retained by the tool that collected it under that provider's own retention settings, not ours.

Security

Traffic to SwiftLambda is served over HTTPS, passwords are stored as salted hashes, connected GitHub tokens are held server-side and never exposed to the browser, and API keys are shown to you once at creation. No system is perfectly secure, and we do not claim otherwise — if we ever discover a breach affecting your personal information, we will tell you.

Your choices and rights

Turning off analytics and advertising. These are the effective routes, in rough order of how comprehensive they are:

• A content or tracker blocker in your browser will block all four tools described above. SwiftLambda is built to work normally when they fail to load — nothing about the product breaks.
• Matomo: Matomo's opt-out documentation.
• Google Analytics: the Google Analytics opt-out browser add-on.
• Google Ads personalization: Google Ad Settings.
• Meta: your Facebook ad preferences.
• Browser-level cookie controls, which let you block or delete cookies for this site entirely.

Your account. You can view and change your account details in settings, disconnect GitHub at any time, revoke an API key, and delete your account.

Access, correction, deletion, and portability. Whatever your jurisdiction, write to privacy@swiftlambda.com and we will honor a request to access, correct, export, or delete your personal information. If you are in the EEA, the UK, or Switzerland, you also have the right to object to or restrict certain processing and to complain to your local data protection authority. Our legal bases are: performing our contract with you (running the service and billing you), our legitimate interests (securing the service, understanding usage), and consent where the law requires it for advertising tools.

International transfers

SwiftLambda is operated from the United States and our providers process data there and in other countries. If you are outside the United States, using the service means your information is transferred to and processed in a country whose data protection laws may differ from your own. Where that transfer involves personal information protected by EEA, UK, or Swiss law, it is made under the European Commission's standard contractual clauses or another lawful transfer mechanism.

Children

SwiftLambda is a developer tool and is not directed at children. We do not knowingly collect personal information from anyone under 13. If you believe a child has given us personal information, write to privacy@swiftlambda.com and we will delete it.

California residents

California residents may request the categories of personal information we collect, the purposes we use it for, and the categories of third parties we disclose it to — all of which are itemized above — and may request access to or deletion of that information. We will not discriminate against you for exercising any of these rights.

We do not sell personal information for money. We do, however, want to be direct rather than hide behind that distinction: running the Google Ads tag and the Meta Pixel does constitute "sharing" personal information for cross-context behavioral advertising as the CCPA defines it. So we treat it as sharing, and we give you a real way to stop it — see below. We do not knowingly sell or share the personal information of anyone under 16.

Do not sell or share my personal information

Use this control to stop the advertising tools. It takes effect on your next page load and needs no account, no email, and no explanation. It is stored per browser, so repeat it on your other devices.

Loading your current setting…

We also honor Global Privacy Control automatically. If your browser or extension sends that signal, you are already opted out on every page and this control will simply confirm it. If you would rather have a human handle it, write to privacy@swiftlambda.com and we will apply the opt-out to any account you name.

Changes to this policy

We update this policy when what we actually do changes — including when we add or remove an analytics or advertising tool. The "last updated" date at the top of the page always reflects the current version, and we will give notice of material changes before they take effect.

Contact

Questions about this policy, or a request about your data: privacy@swiftlambda.com.

For anything else about the product, see the API documentation.