Terms for App Checkup
These are the terms for App Checkup from Appgarten. Part 1 applies to the service itself. Part 2 is the data processing agreement, which applies when you give us code. The terms apply only to App Checkup and the trial of App care (section 10). Fixes, App care and other work on code require a separate agreement.
Part 1 of 2. Version: 13 · Effective from: 20 November 2026
1. Parties, and what App Checkup is
The terms apply between Little Red Hen AS, org. no. 818 764 022, Frostveien 18B, 1164 Oslo ("Appgarten", "we") and the party ordering App Checkup ("you"). That is a company or other organization with an organization number. A sole proprietorship counts as an organization. By accepting the terms, you confirm that you can bind the organization.
App Checkup is a review of a tool you have made yourself. The first App Checkup for each company is free. It is done by our service and Claude, without a human having looked it over before you get the report. There are three ways in, and you choose in the order. With a domain: the service checks what is publicly available at the address you provide, and reads the code if you connect a GitHub repo or upload a zip file. Without a domain: the app is not live yet, and the service only reads the code you upload as a zip file or paste in as a single file. In that case the service checks no address. From an AI tool: if you have connected the app to Appgarten in Claude, Lovable or another AI tool, the service uses the code the tool has sent us, and the address you have confirmed with the Appgarten tag. Claude, an AI model from Anthropic, assesses the ten checkpoints and estimates what it will cost to fix the findings. The report is ready right away. You see the full report on My account after you have logged in. By email you get a summary: how many points are red, yellow and green, and the names of the most important points.
App Checkup is not a security test. The service does no penetration testing, does not guess passwords and never tries to get past login or other safeguards. We change nothing in your tool, code, data or accounts. With a domain, the service sends only ordinary GET requests, from one fixed IP address, and the requests refer to appgarten.ai/appsjekk/skanning, which explains what we fetch.
2. What you are responsible for
- Permission and ownership. You confirm that you, or the organization you are ordering for, own or control the tool and the code, and that you have the right to give us permission and share the code. If you provide a domain, the service does not scan and does not accept code until ownership of the domain is confirmed. You confirm it with a code from us, which you add as a TXT record in DNS, a meta tag on the front page or a file on the website. The service checks the code again right before the scan. If the app is on an address shared with others, for example under lovable.app, you cannot use DNS, and the service does not try the known paths. Without a domain, we do not check ownership. In that case we rely on your confirmation, and you are responsible for it being correct. If the code was made for an employer or an organization, you must order with the organization's organization number.
- Correct information. The assessment is based on what you tell us and what you give us. Answers that are wrong or missing can lead to a wrong assessment.
- Code without data. With a domain, code is optional. Without a domain, the code is the only thing the service sees, and then you must give us the code. Give read access to one repo only, upload a zip file or paste in a single file, without databases, exports, logs or other information about your users. This also applies to lists of customers, employees or other people that sit directly in the code. The service skips files that look like data, and hides email addresses, phone numbers, national identity numbers and keys, but you are the one who knows what the code contains.
- Withdrawing permission. You can withdraw permission at any time. The service then stops, and the code is deleted.
3. Price and ordering
The first App Checkup for each company is free. The first App Checkup of an app you have connected from an AI tool is also free. Otherwise each App Checkup costs NOK 49 excl. VAT, and a new App Checkup of an app you have checked before costs NOK 19 excl. VAT. If the app has an app care agreement, a number of App Checkups per month are included in the price for the level: 2 at Level 1, 4 at Level 2 and 8 at Level 3. You order new App Checkups on My account, and the price is shown in the form before you order. The person ordering ticks a box confirming that the company will pay. We charge only once the report has been delivered. An order that does not become a report costs nothing. The amount is added to the company's invoice from us, collected once a month. No App Checkup commits you to buying anything more.
The next steps are sent only to the email address you provide. The analysis starts only when you have given us the code or, with a domain, started the App Checkup. You can get one free App Checkup with a domain and one without a domain per 60 days. With a domain, this is counted per domain and organization number, without a domain per organization number. Paid App Checkups have no such limit. The service can reject an order, for example if the organization number is not active in the Brønnøysund Register Centre (Enhetsregisteret), if the App Checkup is not started, or, with a domain, if ownership cannot be confirmed. We can also decline or stop an order without giving a reason.
4. The report and the prices
The report is a first assessment. It is made by the service and Claude without a human having looked it over before you get it, and it is marked as such. It may contain errors, omissions or findings that have been misunderstood. It is based on what the service saw on the date it was carried out, given the access and information it received. Without a domain, the service sees only the code, not the app as it runs for users. Points that cannot be assessed before the app is live are marked "Not set up yet". It is no guarantee that the tool is secure, lawful or free of errors, and it does not cover changes after that date.
We can correct the report afterwards. We are notified of every report and can correct findings, colors, the recommendation and prices. You are then notified, and the new version gets a new date. You can ask for a human to look at the assessment.
The report shows no prices. When you press "Ask us for help", that is a request and not an order. We look at it and send a quote with a fixed price per point. Fixes, App care and all other work on code or systems are done only under a separate, written agreement, which we enter into only after we have gone through the points, the price and the scope. Until such an agreement has been entered into, we do no work in your systems.
5. Liability
You use App Checkup at your own risk. The tool, the code, the data and the accounts are yours, and you are fully responsible for them. This also applies to the issues the report points to, and to what you do or fail to do with the report, including decisions you make based on the first assessment or a price in the report.
Our liability. App Checkup is an assessment and no guarantee (section 4). We are not liable for your tool, code, accounts, suppliers or operations. If we fix something under a separate agreement, we are liable only for our own work, that is, the code and the changes we make ourselves, and in accordance with that agreement.
Limitation. To the extent permitted by mandatory law, we are not liable for indirect loss, such as lost profit, lost data, downtime or third-party claims, and our total liability is limited to NOK 10,000, for the terms and the data processing agreement combined. The limitations do not apply where the law does not allow them, for example in cases of gross negligence or intent.¹
6. Confidentiality
Both parties keep confidential what they learn about the other through App Checkup. For us, this applies in particular to code, keys, findings and the report. We never store full keys or passwords, and the report is on My account behind login. Give access only to those who should see it. The duty of confidentiality does not apply to information that is already public, or that we must disclose by law or by order of the authorities. It also applies after App Checkup has ended.
7. Privacy
How we process information about you and the contact person is set out in the privacy policy: appgarten.ai/en/personvern. When you connect GitHub, upload code or paste in code, we process information on behalf of you or your organization. The data processing agreement (Part 2) then applies. It must be accepted before the service lets you connect, upload or paste.
8. Subcontractors
The service is hosted with Google Cloud in Finland, and the assessment is done with Claude from Anthropic. The subcontractors are bound by data processing agreements and confidentiality. Which ones we use is set out in the data processing agreement.
9. Urgent findings
If the scan finds something at your address that requires action right away, it is shown at the top of the report. Today this covers a file with secrets, such as passwords and keys, the app's version history, or a key that gives full access to the database, that is openly exposed. On My account, only the type of finding is shown. Where the finding is located is stated only in the PDF of the report. The contact person gets an email the same day, when the report is ready, with a link to the report on My account and without details about the finding. We are also notified. The service does not store the content, only the type of finding and where it is located. You decide what should be done, and you may need to report a breach to the Norwegian Data Protection Authority (Datatilsynet).
10. Trial of App care
An organization can try App care at Level 1 free for 14 days, once per app. We check only the address you have shown is yours, and only what anyone can see on the internet. Alerts go to the email address that was registered when you started the trial. After 14 days we stop checking. The trial costs nothing. App care continues only when you accept the App care agreement. Our liability during the trial is limited as in section 5.
11. Deletion, governing law and disputes
Code is deleted according to the rules in the data processing agreement. Other information is deleted according to the privacy policy. The terms are governed by Norwegian law. Disputes shall first be sought resolved amicably. If that does not succeed, Oslo District Court (Oslo tingrett) is the legal venue.
¹ Why the limitation is worded this way. Under Norwegian law, liability cannot be limited in cases of gross negligence or intent, and a term can be set aside if it is unreasonable (the Norwegian Contracts Act (avtaleloven) § 36). Without the exception, the entire provision could be set aside. Liability under the GDPR towards the data subjects cannot be contracted away.
Part 2: Data processing agreement for App Checkup
Version: 13 · Effective from: 20 November 2026
The parties: The customer ordering App Checkup (controller, hereinafter "the customer") and Little Red Hen AS, org. no. 818 764 022, which operates Appgarten (processor, hereinafter "Appgarten").
The customer accepts the agreement in the order, before the service lets the customer connect GitHub, upload code or paste in code. In substance, the agreement is based on the European Commission's standard contractual clauses for data processing agreements from 2021 and meets the requirements of Article 28 GDPR.
1. What the agreement covers
1.1 The agreement covers only App Checkup: that Appgarten's service fetches code from one GitHub repo with read access, receives a zip file or receives a single file the customer pastes in, and analyzes the code without a human reading it, in order to produce the App Checkup report. This applies both with and without a domain. Fixes, Fiks, App care and other work require a separate data processing agreement before they start.
1.2 The agreement covers personal data that the customer is responsible for, and that may be in the code. The details are set out in the appendix. Information Appgarten itself is responsible for (contact person, order, permission, intake, report and follow-up) is covered in the privacy policy, not here.
1.3 In case of conflict, this agreement takes precedence over other terms with regard to personal data.
2. The customer's responsibilities
2.1 The customer is the controller for the information in the tool and the code and determines the purposes and means. The customer is responsible for the information being processed lawfully, for having a legal basis for processing, for informing its data subjects and for it being lawful to give Appgarten the code.
2.2 The customer gives as little as possible: read access to one repo, a zip file or a single pasted file, without databases, exports, logs and other information about users, nor lists of people that sit in the code itself.
2.3 The customer is and remains responsible for the tool, the data, the accounts and their security, including weaknesses that existed before App Checkup and weaknesses that the report points to.
3. Instructions
3.1 The agreement and the appendix are the customer's documented instructions. Appgarten shall only:
- fetch and analyze the code the customer has provided, without a human reading it, in order to produce the App Checkup report
- not change anything in the customer's code, data, configuration or accounts
- not copy, store or use information about the customer's customers, users or employees, and not send folders or files with data to Claude
- not use the information for any other purpose, including training AI models
3.2 The report may describe what types of information the code or the tool holds and where it is located, but does not reproduce the content.
3.3 Appgarten notifies the customer immediately if we believe an instruction is in breach of data protection rules. If the law requires Appgarten to process information beyond the instructions, we notify the customer first, unless the law prohibits it.
4. Duty of confidentiality
Everyone who has access to the information on behalf of Appgarten (currently one person) has a written duty of confidentiality that also applies after the agreement has ended. The same applies to code, keys and trade secrets, even if they are not personal data. In normal operation, no one at Appgarten reads the code. The service analyzes it without a human reading it, and deletes it.
5. Security
Appgarten has measures appropriate to the risk (Article 32 GDPR). The measures are set out in the appendix. Appgarten may change the measures, but not in a way that weakens security.
6. Sub-processors
6.1 The customer gives general authorization for Appgarten to use the sub-processors in the appendix.
6.2 Appgarten notifies the customer in writing at least 14 days before a new sub-processor is engaged or one is replaced. The customer can object within that deadline. If we cannot agree, the customer can end App Checkup. Processing then stops, and section 10 applies.
6.3 Appgarten enters into a written agreement with each sub-processor with obligations at least as strict as in this agreement, and is liable to the customer for the sub-processor fulfilling them. A freelancer or other person who helps Appgarten counts as a sub-processor and must have a duty of confidentiality and a data processing agreement.
7. Transfers outside the EU/EEA
The code is stored and analyzed in the EU/EEA (Finland). What is sent to Claude is processed by Anthropic in the USA. Information is transferred outside the EU/EEA only when there is a valid basis under Chapter V GDPR. The appendix shows countries and bases.
8. Breaches
8.1 Appgarten notifies the customer without undue delay and no later than within 24 hours after becoming aware of a personal data breach affecting the customer's information. The notification states, as far as is known, what has happened, which information and approximately how many people are affected, possible consequences and what has been done. What is not yet known is provided later.
8.2 The customer decides whether the breach is to be reported to the Norwegian Data Protection Authority (Datatilsynet) (within 72 hours) and to the data subjects. Appgarten helps with the information the customer needs.
8.3 The service does not look for personal data that the customer's tool exposes openly, and never downloads or stores such information. If Appgarten nevertheless sees that the tool exposes personal data openly, for example without login, we note only that and where and notify the customer without undue delay. This is the customer's breach, and the customer may have a duty to report it.
9. Assistance and audits
9.1 Appgarten assists the customer, as far as is reasonable given our role, with responding to requests from data subjects (access, erasure and other rights), with security, with data protection impact assessments (DPIA) and with prior consultation with the Norwegian Data Protection Authority. If Appgarten receives such a request directly, it is forwarded to the customer without Appgarten responding to it itself.
9.2 On request, Appgarten gives the customer the documentation needed to show that the agreement is being complied with, for example the time the code was deleted. The customer, or an independent auditor bound by confidentiality, can audit compliance with reasonable notice, normally no more than once a year or after a breach. The customer covers its own audit costs. Appgarten's time beyond 2 hours per audit is invoiced as agreed.
10. Duration, access and deletion
10.1 The agreement applies from when the customer connects GitHub, uploads code or pastes in code, until the code has been deleted under 10.2.
10.2 When the analysis is finished, or when App Checkup stops, is canceled or permission is withdrawn:
- code, zip files and pasted files at Appgarten are deleted as soon as the analysis is finished and no later than after 7 days
- Anthropic deletes what was sent to Claude within 30 days, under Anthropic's terms
- if the customer has connected GitHub, the service removes Appgarten's app from the customer's GitHub account right after the code has been fetched, also when the fetch fails. A connection that is not used is also removed. If the removal does not succeed, the customer sees a message on the page for the App Checkup and in the report, with a link to the settings in GitHub, and the service tries again every night until the app is removed. The customer can also remove the app themselves in GitHub at any time.
- Appgarten confirms the deletion in writing when the customer asks for it
10.3 The report is kept according to the privacy policy. It does not contain code or information about the customer's users.
10.4 Under the instructions, information about the customer's users shall not be held by Appgarten. If such information nevertheless comes in, it is deleted together with the code.
11. Liability
11.1 Each party is liable for its own breaches of this agreement and of data protection rules. Appgarten is liable only for damage caused by Appgarten having breached obligations that apply to processors, or having acted outside or contrary to the customer's lawful instructions (Article 82(2) GDPR).
11.2 The customer is fully responsible for the tool, the code, the data, the accounts and security, including weaknesses that already existed or that the report points to. Appgarten is not liable for these, for the customer's own choices or for the customer's suppliers and operations.
11.3 To the extent permitted by mandatory law, Appgarten is not liable for indirect loss, and Appgarten's total liability under this agreement and the terms (Part 1) is limited to NOK 10,000. The limitations do not apply where the law does not allow them, for example in cases of gross negligence or intent.
11.4 The limitations apply between the parties. The data subjects' right to compensation under Article 82 GDPR cannot be contracted away.
12. Changes, governing law and disputes
Appgarten can change the agreement by giving the customer written notice. Changes do not apply to an App Checkup that is in progress, unless the customer accepts them. The agreement is governed by Norwegian law. Disputes are resolved in Oslo District Court (Oslo tingrett) if the parties cannot agree.
Appendix: Description of the processing
| Purpose | Review the customer's self-made tool and produce the App Checkup report. No other purposes. |
| Nature of the processing | Analysis without a human reading the code. The service fetches the code from the default branch of one GitHub repo as an archive without git history, receives a zip file (from which .git/ is removed), or receives a single file the customer pastes in, which is processed as a zip file with one file. Without a domain, no address is scanned. The code is stored temporarily in Google Cloud Storage and analyzed in Google Cloud Run, both in europe-north1 (Finland). The service skips folders and files with data, masks keys and sends filtered parts of the code to the Claude API (Anthropic), which assesses the checkpoints and estimates. No changes, no fetching of production data and no copying of information about users. In normal operation, no person reads the code. |
| Access | GitHub app installed by the customer in the customer's own account, with read access to the contents of one repo. The app removes itself right after the fetch. Or upload of one zip file, or pasting of one file. Without a domain, only a zip file or pasting. |
| Categories of data subjects | The customer's customers and users, the customer's employees, and developers mentioned in the code. |
| Categories of data | What may incidentally be in code, test data, configuration and comments: for example names, email addresses, phone numbers, usernames and IP addresses. Git history is not fetched. |
| Special categories | Not processed intentionally. May be in the tool (for example health data or national identity numbers). The customer states this in the intake (question 5). The service masks such patterns before anything is sent to Claude, and the matches become findings in the report. |
| Duration and retention period | Code, zip files and pasted files at Appgarten: deleted when the analysis is finished, and no later than after 7 days. At Anthropic: deleted within 30 days. GitHub access: removed right after the fetch, also when the fetch fails. If that does not succeed, the service tries again every night. Information about the customer's users: not stored. |
Security measures
- Code is stored only in a private bucket in Google Cloud Storage in europe-north1, encrypted, with public access blocked. Soft delete and versioning are turned off, so that deleted code is actually gone.
- The code is deleted when the analysis is finished or fails, and a rule deletes everything older than 1 day. The deletion is logged without content.
- Upload via a signed link with a short lifetime and a size limit.
- Folders and files with data are not read and not sent to Claude (for example databases, exports, CSV, logs, seed and test data and
.env). Keys are masked before anything is sent. - Findings are stored with file path and description, not with code excerpts. Keys are shown only as type, location and a short fingerprint, never with characters from the key itself.
- Claude is used only through the service, via the API on Anthropic's commercial terms, under which data is not used to train models.
- Service accounts have the least possible access. Keys are kept in Secret Manager. Logs do not contain code or responses from Claude.
- Two-factor sign-in on Google Cloud, Anthropic Console and GitHub.
- The report is on My account behind login, and only those the customer has given access can see it.
- Internal breach log.
Sub-processors
| Sub-processor | What they do | Where | Basis for transfer |
|---|---|---|---|
| Google Cloud EMEA Limited (Google Cloud: Cloud Run, Cloud Storage, Secret Manager, Cloud Logging) | Operation of the service, temporary storage and analysis of the code | Finland (europe-north1) | Storage in the EU/EEA. Google's Cloud Data Processing Addendum, with the EU standard contractual clauses for any access from countries outside the EEA |
| Anthropic Ireland, Limited (Claude API) | The first assessment of the checkpoints and hour estimates, based on filtered code | Ireland. Processing in the USA. | EU standard contractual clauses (Modules 2 and 3) in Anthropic's data processing agreement |
Contact for privacy and breaches: Appgarten (Little Red Hen AS, org. no. 818 764 022), hello@appgarten.ai
If the Norwegian and English versions differ, the Norwegian version applies.