Privacy policy for Appgarten
Last updated: 19 November 2026
Appgarten is a service from Little Red Hen AS. Here we explain what information about you we process when you visit the website, order an App Checkup, log in to My account, have an App care agreement with us or talk to us afterwards, why we do it, and what rights you have.
App Checkup can be ordered by businesses with an organization number. If you order for a business, what we write about "you" also applies to the business. A sole proprietorship orders with its organization number. We process the information about you as the owner in the same way as the information about a contact person.
In short: In App Checkup, our service checks your tool, and Claude, an AI model from Anthropic, assesses it and estimates what it costs to fix the findings. The report is ready right away and is marked as a first assessment: it is made by the service and Claude without a person having looked it over. You see the full report in My account after you have logged in. A person can correct it afterwards and always looks it over before an agreement on fixes. Code you give us is deleted when the review is finished. We never sell information.
1. Who is responsible
Little Red Hen AS, org. no. 818 764 022, Frostveien 18B, 1164 Oslo, is responsible for the information described here.
Questions about privacy: hello@appgarten.ai.
2. When you visit the website
Logs for operations and security
- What: IP address, browser type, time and which pages you visited, in server logs at Google Cloud in Finland.
- Why: so that the website works and is secure.
- Basis: our legitimate interest in running a secure website (Article 6(1)(f) GDPR).
- How long: 30 days.
Measurement with Google Analytics, only if you say yes
The first time you visit the website, we ask whether we may measure your visit. "Accept" and "Decline" are equally easy to choose. If you say no, or do not answer, we do not load Google Analytics, and nothing is sent to Google.
- What: If you say yes, Google Analytics stores a random ID in your browser. It lets us see that several page views belong to the same visit. We see which pages you visit, which page you came from, whether you submit the order form, which country and which region you are in (based on the IP address), and whether you use a mobile phone, tablet or PC, which browser and which language. We do not see who you are. We never send names, email addresses, organization numbers or what you type in forms to Google.
- Not on all pages: Google Analytics is only on the front page, the page "Get your app live" and this page. It is never on My account (konto.appgarten.ai), where you see the report and accept agreements, and never on the pages you reach with the link from the email, where you give us the code and follow the review.
- Why: to see where visitors come from and how many order App Checkup, so that we know what works.
- Basis: your consent (point (a)). We only store and read cookies from Google Analytics when you have said yes (the Norwegian Electronic Communications Act (ekomloven) § 3-15).
- What we have turned off: We have turned off ads, personalized ads, linking to Google Ads and linking the visit to your Google account (Google Signals). We do not collect precise location or details about your device. We do not share the data with Google's other services.
- How long: Google deletes the detailed data about your visit after 2 months. What remains is aggregate figures, for example the number of visits in a month, which cannot be linked to you. The cookies from Google Analytics last for 12 months, or until you delete them or withdraw your consent.
- Changing your mind: Click "Cookies" at the bottom of every page. There you can change your choice at any time. If you withdraw your consent, the measurement stops right away, and we delete the cookies from Google Analytics in your browser. What we measured before you withdrew your consent is deleted after 2 months. Read more at appgarten.ai/en/informasjonskapsler.
- Your choice: We remember your choice in a separate cookie for 12 months, so that we do not ask every time. It only says whether you have said yes or no, and it is not sent to Google. After 12 months we ask again.
3. When you order
- What: name, email, your role in the business, the business's name and organization number, the name of the app and its address if it has one, how many people use it, and where you heard about us. If you came to us from a campaign, we store the campaign code (for example "linkedin"). We look up the organization number in the Brønnøysund Register Centre (Enhetsregisteret) to see that the entity is active.
- The link by email: we only send the link to the App Checkup to your email address. It is not shown on the website after you have submitted the form. Only the person who has the email can start the App Checkup, give us the code and follow the review until the report is ready. This prevents anyone from ordering in your name. We do not store the link itself, only a code we can recognize it by. The link works for 14 days before you have started the App Checkup. When the report is ready, you get an email with a summary and an invitation to My account. There you see the full report after you have logged in (section 11). This ensures that the report reaches the right person.
- Why: to deliver App Checkup, check that the order is a fit for the service and get in touch with you. To ensure that each app gets one App Checkup per 60 days, we store the organization number, or the email address and the app name, in a form that cannot be read back. It is deleted after 60 days.
- Basis: our legitimate interest in delivering the service the business has ordered and having a contact person (point (f)).
- How long: 3 years after the report is delivered. Orders that are not started within 14 days are deleted at that point. If the App Checkup is paused because we have reached capacity before you have given us the code, we wait at most 45 days after the order. If there is still no room by then, we delete the order. If the App Checkup is canceled or stopped, we delete the order after 30 days, but keep the permission (section 5). We do not store orders that are not a fit.
- New App Checkup in My account: If you order a new App Checkup in My account, we store your name, the company, the app, the price and when you ordered, and when the report was delivered. This is the basis for the invoice to the company, and we keep it for 5 years after the end of the financial year, because the Norwegian Bookkeeping Act (bokføringsloven) requires it.
- Notice about the route with a domain: If you asked to be notified when App Checkup for apps with their own domain opened, we only stored your email address, because we have a legitimate interest in notifying you (point (f)). We send the notice once and delete the address when it has been sent, and no later than after 12 months.
4. Only for businesses
App Checkup and App care are for businesses with an organization number. We do not accept orders from private individuals.
5. Permission, and ownership when the app has a domain
Before we look at the tool, we ask for written permission. If the app has a domain, the service also checks that you control it. You place a code we give you in the domain (a TXT record in DNS), on the front page of the app (a meta tag) or in a separate file on the website. We check the code once more right before the scan. If it has been removed, we do not scan. You can remove the code when the App Checkup is finished. If it does not have a domain yet, we scan nothing, and we rely on your confirmation that you own the code and have the right to share it. This prevents anyone from ordering a report about a tool that belongs to others.
- What: the name and role of the person who gives permission, the time, what the permission covers, which version of the terms was accepted, and, with a domain, the ownership check: which method, the code, the time and the result.
- Basis: our legitimate interest in being able to document that we have only looked at what we were allowed to (point (f)). The permission is an agreement with you, or with the business you order for, not consent under the privacy rules.
- How long: 3 years after the report is delivered or the case is closed. If the App Checkup is not started within 14 days, or within 45 days when it is paused before you have given us the code, we delete the permission at that point, together with the order.
6. Intake: the questions we ask
- What: answers to the questions about the tool, the ones you answer after the report. The answers may mention people in the company. We ask for roles ("CEO", "a former employee") and not names, and we never ask for the information stored in the tool.
- Basis: our legitimate interest in delivering the service (point (f)).
- How long: together with the report (section 8). If the case is canceled, the answers are deleted the following night.
7. Scanning and review of the code
Scan of what is public (only when the app has a domain). The service checks what is openly available at the address you have given permission for, and only there: security settings, services the tool uses, login and visible keys. It reads the front page and the scripts on the same address, and tries a few fixed paths, for example whether a file with secrets is openly available. We do not fetch scripts from other addresses. We only store that something is openly available and where, never the content. If we find a key, we only store what type it is and a short fingerprint. We record which fields a form has, but not what is in them. We only read, and we never try to get past a login. The scan comes from the IP address 34.88.75.50 and identifies itself as "Appgarten-Appsjekk/1.0", with a link to appgarten.ai/appsjekk/skanning, which says what we fetch. If the app does not have a domain yet, we scan nothing.
- Basis: legitimate interest (point (f)). How long: raw data for 12 months.
When you give us the code, by connecting one GitHub repo with read access or uploading a zip file (with a domain), or uploading a zip file or pasting in one file (without a domain), the code may contain information about the customers, users or employees of your business. We then process the code on behalf of the business, which is the controller of the information, under a data processing agreement. This means:
- The code is stored temporarily at Google Cloud in Finland while it is being reviewed.
- The service skips folders and files with data, masks keys and only sends what is needed to Claude.
- Do not put lists of customers, employees or other people in the code you give us. We hide email addresses, phone numbers and national identity numbers before anything is sent to Claude, but not everything else.
- We do not fetch the git history.
- The code is deleted when the review is finished, and no later than after 7 days. At Anthropic it is deleted within 30 days.
- When we have read the code, we also store a short technical summary for ourselves: which technology the app is built with, how large the code is, and what the price is based on. It contains no code, no personal data and no keys. Only we, and the person working on your case, can see it. It is deleted together with the report.
- GitHub: You install Appgarten's app at GitHub on one repo. To see that the installation is yours and covers exactly one repo, we use an access from your GitHub login. It is revoked right away and never stored. We fetch the code once, as an archive of the latest version, and store the name of the repo and which version we fetched with the case. Right after fetching, the app removes its own installation, also if the fetching fails. If that does not succeed, we try again and ask you to remove the app yourself.
- If you are a customer or user of a tool we have reviewed, and want to know something about your information, contact the company that owns the tool. We help them answer.
8. The first assessment and the report
- How: Claude from Anthropic, via their business service (API), assesses the ten checkpoints and estimates what it costs to fix the findings. The report is ready right away, without a person having looked it over, and it is marked as a first assessment. Under the privacy rules it is an automated assessment, but it concerns the tool and not you (see below).
- The report in My account: You see the full report in My account after you have logged in (section 11). The email saying the report is ready only has a summary: how many points are red, yellow and green, and the names of the most important points.
- A person afterwards: We are notified of every report and can correct findings and prices. You are then informed. No agreement on fixes is entered into before we have approved the points and the price. You can always ask for a person to look over the assessment.
- No decisions about you: The assessment concerns the tool, not people. We make no automated decisions that have legal effects or similarly significant effects for you (Article 22). The report uses roles and not names.
- Basis: our legitimate interest in delivering the service and documenting the work (point (f)).
- How long: 3 years after delivery. You decide yourself over your own copy.
9. Follow-up and fixes
- What: name, contact details, which points you chose, notes from conversations and whether you want to go ahead. For an agreement on fixes or an App care agreement, also invoicing details.
- When you ask for a quote: we answer your request and may send one reminder about the same quote.
- Other follow-up by email: We do not send other follow-up or offers to sole proprietorships unless you have said yes to it. The reminder about the report below is the exception.
- Reminders about remaining points: When we have delivered the fixes, and there are still points in the report that should be fixed, we send you two emails about it: 14 and 30 days after delivery. To companies we do this because you are our customers. To sole proprietorships only if you have ticked the box for it. Each email has the link "Stop sending", and then you hear no more about it.
- Reminder about the report: When you have ordered App Checkup, we send two emails about the points, 2 and 4 days after the report, if you have not asked for a quote. We stop when you have asked for a quote, or when you click "Stop sending" in the email. This also applies to sole proprietorships.
- Basis: for businesses our legitimate interest in following up (point (f)). For the reminder about the report our legitimate interest in reminding you of an App Checkup you have ordered (point (f)), also for sole proprietorships. For sole proprietorships consent (point (a)). Answer to a request for a quote: steps you have asked for before an agreement (point (b)). For an agreement on fixes: the agreement (point (b)) and the Bookkeeping Act (point (c)). You can at any time say that you do not want to be contacted again.
- Agreement on fixes: when you accept a quote, we store the agreement text you accepted, your name, your role and when you accepted. We keep the agreement for 5 years after the work is delivered, and then we delete it, because we must be able to show what we agreed if a claim arises, and because it is documentation of the sale. We do not store more than this with the agreement.
- When a freelancer does the fixes: Sometimes a freelancer fixes the app for us. The freelancer has their own business, lives and works in the EU/EEA and has a duty of confidentiality and a data processing agreement with us. Before the freelancer gets in touch, you get an email from us with the person's name and email address. The freelancer gets your name and email, and phone number if we have it, and sees the points in the agreement and the findings in the report. The freelancer does not see the price. Email from the freelancer comes from an address on appgarten.ai, with hello@appgarten.ai in copy, and is stored with us like other email with you. We answer questions about price, new points and complaints. If the freelancer uses Claude, it is only through our account at Anthropic (sections 12 and 13). The basis is the same as for the agreement on fixes. If you do not want a freelancer to fix the app, let us know, and we will do it ourselves.
- Log of who views the case: We log every time someone at our end or a freelancer opens your case or sees your contact details, so that we can show who has seen what. The log does not contain the content of the case. The basis is our legitimate interest in protecting your information (point (f)). We keep the log for 3 years.
- How long: if you become a customer, the customer relationship and 3 years after, and accounting records for 5 years after the end of the financial year. If not, the information is deleted or anonymized after 12 months. If you withdraw your consent, the follow-up stops right away. We keep the proof of consent for 3 years.
- If we need to know more before we give you a price, the question comes from the email address of the person at our end who has the case. We store the question with the case.
10. When we look after your app in App care
If the business has an App care agreement with us, we check the app all the time and review it at regular intervals. What is checked, and how often, is set out in the appendix to the App care agreement.
Information about you as a contact person
- What: name, email, your role, the app and the level, when you accepted the agreement, and emails and alerts we send you.
- Why: to deliver App care, send alerts, growth alerts and App care reports, and document what we have agreed.
- Basis: our legitimate interest in delivering the service the business has ordered, and having a contact person (point (f)). What becomes accounting documentation: the Bookkeeping Act (point (c)).
- How long: the accepted agreement for 5 years after it has ended. The App care reports for as long as the agreement lasts and 3 years after. Invoices under the Bookkeeping Act.
- Add-ons: If you turn on an add-on, we store who turned it on and off, when, the price and which version of the text you accepted. This is the basis for the invoice, and we keep it for 5 years after the agreement has ended, like the agreement.
- If you write to us in "Ask for help" or answer "No, it's not fixed" under App care in My account, we store the text with the case. Only we and the partner who has the case see it, and we delete it 12 months after the case is closed.
- Questions about your case come from the email address of the person at our end who has the case.
- If you ask for help, we send your text to Claude (Anthropic), which helps us suggest what should be fixed. Before that we hide passwords, keys, email addresses, phone numbers and national identity numbers, but not everything else, for example names.
- The contingency plan is stored with what you write. We ask for roles, not names.
Information about the users of the app. When we check the app, we may see information the business is the controller of. We then process it on behalf of the business, under the data processing agreement in the App care agreement. This means:
- The code: We fetch the code at each thorough review, with read access through GitHub or as a zip file. It is deleted when the review is finished, and no later than within 7 days, and is never stored from one review to the next. We skip files with data, hide keys, email addresses, phone numbers and national identity numbers, and only send what is needed to Claude.
- The rules for the database (with GitHub): With every change to the code and every week, we fetch only the files with the rules for the database, to see whether any tables are open to anyone. We store only the names of the tables, whether they are open, and which types of information they hold (for example names or email addresses), never the content. The files are deleted when the check is finished, and do not go to Claude. We never connect to the database.
- Every version right away (add-on, with GitHub): GitHub notifies us every time the code changes, and we check the change right away. The notice from GitHub includes the message about the change and the name and email of the person who made it. We only use which repo and which versions it concerns, and do not store the rest. Then we fetch only the lines that have been added, look for keys and passwords, and delete the lines right away. If we find a key, we only store the type, the file and a short fingerprint, never the key itself. We store which versions it concerned for 30 days. The lines do not go to Claude. If the add-on is off, we use the notice from GitHub only to fetch the rules for the database.
- The test account: The tests of what the users do most often only use a test account the business has created, with test data. The login is stored encrypted at Google Cloud in Finland and deleted when the agreement ends. If a test fails, it takes a screenshot of what the test account sees. The screenshots are never sent to Claude and are deleted after 30 days.
- The tests we suggest are made by Claude from the public pages of the app, without logging in. You see them in the appendix and accept them before they are run.
- The uptime checks only fetch the public page. We do not store the content, only the first 47 characters of the text when the keyword we look for is missing. They run from our machine at Google Cloud in Finland. At the highest level, Level 4, we also check from Google Cloud Monitoring, which fetches the public page from several places in the world, also outside the EU.
- The results from the checks are stored for 12 months.
- When a freelancer does work in App care: Sometimes a freelancer does work in the app for us, for example a security update. The freelancer has their own business, lives and works in the EU/EEA and has a duty of confidentiality and a data processing agreement with us. Before the freelancer gets in touch, you get an email from us with the person's name and email address. The freelancer gets your name and email, and phone number if we have it, and sees the findings and what is to be done, but not the price. Email from the freelancer comes from an address on appgarten.ai, with hello@appgarten.ai in copy. We answer questions about price, new work and complaints. If the freelancer uses Claude, it is only through our account at Anthropic. If you do not want a freelancer to do the work, let us know, and we will do it ourselves.
- If you are a user of an app we look after in App care, and want to know something about your information, contact the business that owns the app. We help them answer.
Trying App care. A business can try App care at Level 1 free of charge for 14 days, once per app. We then only check the address you have shown is yours, and only what everyone can see on the web.
- What: who started the trial (the account in My account), when, which version of the text was accepted, the address we check and the email address the alerts go to. The uptime and downtimes for the address during the 14 days. If we show you a banner about App care in My account, we also store the account and how many times you have hidden it.
- Why: to give you the trial, send alerts and two emails about the trial, and be able to show what you said yes to.
- Basis: our legitimate interest in giving the business the trial it has asked for (point (f)). The trial is only for businesses.
- How long: we keep the trial and what you said yes to for as long as the app exists with us, and delete them with the app. For businesses that is 3 years after the last report. We delete how many times the banner has been hidden together with the account.
- The code in the trial: If you give us the code in the trial, with read access to one repo through GitHub or as a zip file, we read it once. We then process the code on behalf of the business, under the data processing agreement for App care (Appendix 2 to the App care agreement), which you accept with a separate checkbox. We store the list of packages with versions, not the code, and an alert if there are keys in the code. Every day during the trial we look for known vulnerabilities in the packages. The code is deleted when it has been read, and no later than within 7 days. The code from GitHub or zip does not go to Claude in the trial. If you connect Appgarten in Claude or Lovable, the section below applies. If the trial stops without you accepting the App care agreement, we delete the package list and which code you chose, and we remove the access in GitHub. We store the checkbox for the data processing agreement, with who, when and which version, together with the trial, and it is deleted with the app.
- The connection in Claude or Lovable: If you connect Appgarten in Claude, Lovable or another AI tool, the tool sends us the files that have changed every time you publish. We then process the code on behalf of the business, under the data processing agreement for App care (Appendix 2 to the App care agreement), which you accept when you connect.
- Before we store anything, we take out .env and files with data, and hide keys. We hide email addresses, phone numbers and national identity numbers before anything goes to Claude.
- Claude reads the files at night and finds what should be fixed. Afterwards we delete the files, and no later than after 7 days.
- We store the list of packages with versions, fingerprints of the files, the findings and a map of how the app fits together. We do not store the code.
- We store which account and which tool connected, and when. You disconnect in My account whenever you want.
- If the trial stops without you accepting the App care agreement, we delete the versions, the findings and the map.
- If you ask Appgarten in Claude or another AI tool, we send the answer to your tool: the same as you see in My account, for the apps your account has access to. The tool is your own, and it is your agreement with the provider that applies to what you get there. We only send what you ask about.
No decisions about you. The reviews are done by the service and Claude and concern the app, not people. A person at our end looks at red findings and writes the comment in the App care report from Level 2 and up.
11. My account and the login
As a customer, you log in to My account, konto.appgarten.ai. There you see your apps, reports, agreements and messages. You log in with an account you already have with Google, Microsoft or GitHub, or with a code we send you by email. We never get your password.
- What we get when you log in with Google, Microsoft or GitHub: your name, your email address and a fixed ID that the provider uses for your account. We only use an email address that the provider has verified. With Microsoft you can only use a work or school account. We do not ask for access to your email, files, calendar or contacts, and we keep no access to your account with the provider.
- Code by email: If you choose "Get a code by email", the email address is what we recognize you by. The code works for 10 minutes, and we only store it in a form that cannot be read back. We delete the information about the attempt after 24 hours.
- What we store about the account: your name, the email address the account was created with, when the account was created and when you last logged in, and which login methods you use. For each login method we store the email address the provider gave us the last time you logged in with it. We also store which customers you have access to, with your role (owner of the company, owner of an app or user), who gave you the access and when. We update the name and address from the provider when you log in.
- The address we send email to: Email from My account goes to the address the account was created with, that is, the one the invitation went to. It does not change when you later log in with a different address.
- Invitations: You only get access to a customer with an invitation by email, from us or from an owner. If you have ordered an App Checkup, we invite you as the owner of your own app. You become owner of the company when an App care agreement is accepted, or when we approve it. The link works once. The invitation after an App Checkup works for 7 days, other invitations for 24 hours. We store the email address the invitation went to, who sent it, and when it was used. We do not store the link itself, only a code we can recognize it by. If you are owner of the company, you can invite colleagues to the whole company. If you are owner of an app, you can invite colleagues to that app. You then give us their email address, and we send the invitation.
- Emails from My account: the invitation, the code when you log in with a code by email, a notice when someone logs in to your account in a new way, a notice to all owners of the company when the company gets a new owner in My account, a notice when there is a new message from us, and a receipt when you have deleted your account.
- List of logins: For each login we store the time, which provider you used, what kind of device and browser (for example "Chrome on Mac") and a shortened IP address, where the last part is removed (for IPv4 the last of the four numbers, for IPv6 everything after the first three groups). We also store when someone gets or loses access. If an event concerns a customer, we store a number for the customer, not the company name. You see the list under Settings, and there you can log out everywhere with "Log out everywhere".
- Messages: In My account you can write to us, and we answer in the same thread. We store the name of the person who wrote, and the text. You and we can attach images, for example a screenshot. We remove hidden information in the image, such as location and camera, before it is stored. The email about a new message says that a message has arrived, but does not contain the text or the images.
- Download everything: You can download everything we have about the app in one zip file from My account. Before the download we ask you to log in again.
- Protection against misuse: To stop those who try to get in, we count login attempts and invitations per IP address and per email address. We only store them in a form that cannot be read back, and delete them after at most 24 hours.
- Why: so that only those who have been given access see the information, so that you and we can talk about the app, and so that you and we can detect and stop misuse.
- Basis: our legitimate interest in giving the business a secure login to My account and knowing who has access (point (f)). The list of logins and the protection against misuse are based on our legitimate interest in keeping My account secure (point (f)).
- How long:
- You are logged in until you log out, for at most 30 days without use and at most 90 days in total.
- We keep the list of logins for 12 months. It is deleted with the account.
- We delete invitations 7 days after they have been used or have expired.
- If the account has no access to any customer, we delete it 30 days after the last login.
- We keep the messages for as long as the customer has an account with us, and delete them with the customer. We delete images in the messages after 90 days.
- Deleting an app: The owner of the app or the owner of the company can delete an app in My account when it does not have an App care agreement in force. The app disappears from My account right away. After 7 days we delete it for good, and until then you can undo it. We then delete the App Checkup, the reports, the findings, the checks and the measurements, the messages about the app, the invitations and the access to the app, and the connection to the code. We keep accepted agreements on fixes and App care and the basis for the invoices for 5 years, because the Norwegian Accounting Act (regnskapsloven) requires it.
- Deleting the account: Under Settings you can delete your account yourself. We then delete right away the account, your logins, all logged-in devices, your access, the list of logins and invitations you have sent that have not been used. There is no period to undo it. The messages you have written belong to the company and remain for as long as the customer has an account with us, but with "Deleted user" instead of your name. We keep accepted agreements and the basis for the invoices for 5 years, because the Accounting Act requires it. If you are the only owner of a company with apps or with other users, or of an app, you must first make someone else the owner or delete the apps. We only keep your address until we have sent the receipt, and for at most 24 hours.
- Cookies: In My account we only use cookies that are needed for the login to work, and therefore we do not ask for consent there (Electronic Communications Act § 3-15).
__Host-kontokeeps you logged in, for at most 90 days.__Host-konto_innkeeps the login together while you are at Google, Microsoft or GitHub, for 10 minutes.__Host-konto_kodekeeps the login with a code by email together, for 10 minutes.__Host-konto_invremembers the invitation while you log in, for 30 minutes.__Host-csrftoken_kontoprevents other websites from submitting forms in your name. Read more at appgarten.ai/en/informasjonskapsler. - No measurement: In My account we do not use Google Analytics or scripts from others.
- The provider you log in with: Google, Microsoft and GitHub are not our providers. They are themselves responsible for the account you have with them, under their own privacy policies. When you log in, they see that you are logging in to Appgarten. If you use a work account, the IT administrators in your company can also see it. We do not send other information about you to them.
12. Who we share information with
We never sell personal data. These providers process information on our behalf and have a data processing agreement with us:
| Provider | What they do for us | Where data is stored |
|---|---|---|
| Google Cloud (Google Cloud EMEA Limited) | Running the website, My account and the service, scanning, temporary storage of code, reports, checks of apps we look after in App care and the logins to test accounts | Finland (europe-north1) |
| Anthropic Ireland, Limited (Claude API) | The first assessment in App Checkup and hour estimates, reviews of apps we look after in App care, including the code from the connection in the AI tool, and help for the person fixing your app | Processing in the USA, on the basis of the EU standard contractual clauses |
| Google Ireland Limited (Google Analytics) | Measurement of visits to the website, only if you have said yes | Processing in the USA at Google LLC, on the basis of the EU–US Data Privacy Framework (checked 2026-10-25) |
| Google Workspace (Google Cloud EMEA Limited) | The mailbox hello@appgarten.ai and the emails we send | Google's data centers in the EU/EEA and other countries, with the EU standard contractual clauses |
| Freelancers with their own business | Fix the app under an agreement on fixes, do work in App care, and clarify the work with you | EU/EEA, in accounts we own |
You get the name of the freelancer who fixes your app by email before the person gets in touch.
When we invoice fixes, our accounting system processes the invoicing details on our behalf. Contact us if you want to know which system we use.
Google Analytics never gets your code, your answers, the report or your contact details.
GitHub (GitHub, Inc.) is not our provider, but the place where you yourself keep the code, under your own agreement with GitHub. If you connect GitHub, we fetch the code from there. We store nothing at GitHub and do not send information about you there. If you log in to My account with GitHub, section 11 applies. GitHub sees that our app is installed, fetches the code and removes itself. If the app has an App care agreement, GitHub also notifies us when the code changes (section 10).
Login to My account: If you log in with Google, Microsoft or GitHub, it is you who has chosen the provider, and they are themselves responsible for your account there. They are not our providers and get no information about you from us, but they see that you are logging in to Appgarten. We get your name, your email address and a fixed ID for the account (section 11).
We may also have to give information to authorities when the law requires it.
13. Transfers outside the EU/EEA
The service and the storage are in Finland. These are the cases where information is processed or fetched outside the EU/EEA:
- Anthropic processes what is sent to Claude in the USA, on the basis of the European Commission's standard contractual clauses.
- GitHub: If you connect GitHub, we fetch the code from GitHub to Finland. We do not send personal data to GitHub.
- Login: If you log in with Google, Microsoft or GitHub, we fetch your name, email address and ID from them to Finland. We do not send personal data to them.
- Google Analytics: If you have said yes to measurement, the data about your visit is processed by Google LLC in the USA. The basis is the European Commission's decision that the EU–US Data Privacy Framework provides an adequate level of protection, and that Google LLC is certified under the framework (checked 2026-10-25). Google's terms also include the European Commission's standard contractual clauses. If you say no, nothing is sent to Google Analytics.
Uptime check for apps we look after in App care: At Level 4 we also check that the app responds, with Google Cloud Monitoring. It fetches the public page from Google's data centers in several countries, also outside the EU/EEA, for example the USA and Asia. It only sees what everyone can see on the page, never pages behind a login, and only stores whether the page responded and how fast. The basis is the European Commission's standard contractual clauses in Google's data processing terms.
In some cases Google may provide support for Google Cloud and Google Workspace from countries outside the EEA, on the basis of the European Commission's standard contractual clauses in Google's data processing terms. Contact us if you want a copy of the basis.
14. Your rights
You have the right to:
- know what information we have about you, and get a copy (access)
- have errors corrected
- have information deleted when we no longer need it, or if the processing is not lawful
- ask us to restrict the processing while something is unresolved
- object to processing based on legitimate interest, and always to marketing
- receive information you have given us, in a common format, where this applies. You can also download everything we have about the app yourself in one zip file from My account (section 11)
- ask for a person to look over the first assessment, which is made without a person having looked it over
- withdraw consent, where we rely on consent, for example to measurement with Google Analytics or to follow-up by email. You withdraw consent to measurement with the "Cookies" link at the bottom of the page. This does not affect App Checkup or what we did before you withdrew it
Send an email to hello@appgarten.ai. We answer within one month. We may ask you to confirm who you are, but do not ask for more than necessary.
15. Security
We protect the information with encrypted storage in Finland, two-step login, as little access as possible, deletion of code, and logins to test accounts stored encrypted in Secret Manager, which only the tests can read. You only find the reports, the agreements and the downloads in My account after you have logged in, and only for the customers you have been given access to. We never store your password. If something still goes wrong and it may affect you, we notify you and the Norwegian Data Protection Authority (Datatilsynet) as the law requires.
16. Complaints
If you believe that we process your information in breach of the rules, we would like to hear from you first. You can also complain to the Norwegian Data Protection Authority: www.datatilsynet.no.
17. Changes
We update the policy when we change how we process information. The date at the top shows when it was last changed. For major changes we notify customers we have an active relationship with.
If the Norwegian and English versions differ, the Norwegian version applies.