> ## Documentation Index
> Fetch the complete documentation index at: https://docs.newly.app/llms.txt
> Use this file to discover all available pages before exploring further.

# Security and data

> Where Newly stores your app's data, who can see it, how it is protected, and how to request a Data Processing Agreement.

This page answers the security and data protection questions people ask most about Newly (app.newly.app). The legal terms are in the [Terms of Service](https://newly.app/terms) and the [Privacy Policy](https://newly.app/privacy-policy).

## Short answers

| Question | Answer |
| - | - |
| Who operates Newly? | Small Scale Labs AB, a Swedish company. The GDPR applies to Newly directly. |
| Is there a Data Processing Agreement (DPA)? | Yes, on request. See [Request a DPA](#request-a-dpa). |
| Where is my app's data stored? | The app database is in the United States. See [Where your data is stored](#where-your-data-is-stored). |
| Who are the sub-processors? | The current list is public at [newly.app/subprocessors](https://newly.app/subprocessors). |
| Is data encrypted? | Yes, in transit and at rest. Secrets get a second layer of encryption. |
| Who owns the code and the data? | You do. You can export both at any time. |
| Does Newly have SOC 2, SOC 3 or ISO 27001? | Not yet. See [Certifications](#certifications). |
| Is my users' personal data used to train AI? | No. See [AI and your data](#ai-and-your-data). |
| What happens to deleted data? | A deleted project or account can be restored for 30 days. After that it is erased for good. |

## Who is responsible for what

| Data | Your role | Newly's role |
| - | - | - |
| Your Newly account, billing and product usage | Customer | Controller, as the [Privacy Policy](https://newly.app/privacy-policy) sets out |
| Your app users' data in your Newly Backend: sign-ins, database rows, uploaded files | Controller. You decide what your app collects and why. | Processor. Newly hosts the data to run your backend. |

Three things stay with you:

* Your app needs its own privacy policy that tells your users what you collect.
* You need a lawful basis for the personal data your app stores.
* You answer your own users' requests to see or delete their data.

### Request a DPA

Newly signs a DPA with customers who need one. Ask in the support chat, or email [support@newly.app](mailto:support@newly.app) from the email address you sign in with. A person on the team sends it to you. The support assistant can't send the DPA itself.

### Sensitive data

The [Terms of Service](https://newly.app/terms) ask you not to store certain data in Newly, such as health records, financial account numbers, government identifiers and biometric data. If your app needs data of that kind, or is aimed at children, contact support before you build.

## Where your data is stored

| Data | Location |
| - | - |
| App database: your tables and your app users' sign-ins | United States |
| Uploaded files: photos, documents | Chosen automatically. You can pass a location hint when you deploy. |
| Your backend's code: the API and sign-in services | Runs on a global network, near the person making the request |
| Your Newly account, projects, chats and billing records | United States |
| Card payments | Handled by Stripe. Newly never receives full card numbers. |

There is no EU-only database option today. If you need your database in the EU or another region, contact support and say which one.

### File location hint

The Newly CLI accepts a region when you deploy: `newly deploy --region weur`. The values are `weur` (Western Europe), `eeur` (Eastern Europe), `enam` and `wnam` (North America), `apac` (Asia Pacific) and `oc` (Oceania).

The hint is a placement preference for your uploaded files. It is not a contractual data residency guarantee, and it does not move the database.

### Transfers outside the EEA, UK and Switzerland

Newly is a Swedish company that stores data with providers in the United States. Those transfers rely on the EU Standard Contractual Clauses, the UK and Swiss equivalents, or the EU-U.S. Data Privacy Framework. The [Privacy Policy](https://newly.app/privacy-policy) has the details.

## Sub-processors

The full, current list is at [newly.app/subprocessors](https://newly.app/subprocessors). That page is the source of truth, and Newly updates it when a provider is added or removed.

Some services are yours, not Newly's. When you connect your own GitHub, RevenueCat, Apple or Google account, that provider works under your agreement with it.

## How your data is protected

### Encryption

* **In transit:** Newly, your backend's API and the database accept connections over TLS (HTTPS).
* **At rest:** the app database, uploaded files and Newly's own records are encrypted where they are stored.
* **Secrets:** your backend secrets, App Store and Google Play publishing credentials and push notification keys are encrypted a second time by Newly, each under its own key.

Secret values never come back out of Newly, from the app or from the API. Newly never stores your Apple Account password. See [Production and secrets](https://docs.newly.app/backend/production-and-secrets.md).

### Isolation

* Each project gets its own database, its own file storage and its own backend services. Projects do not share tables.
* Each project has a development backend and a production backend, each with its own database and file storage. The development backend cannot read or change production data. See [Data, accounts and Newly Backend](https://docs.newly.app/backend/overview.md).

### Who can see production data

| Role | Development database | Production database |
| - | - | - |
| Owner | View and edit | View |
| Admin | View and edit | No access |
| Can edit, Can view | No Database tab | No Database tab |

Secret columns, such as session tokens and password hashes, show as hidden in the Database tab, even to the owner.

Only the project owner can export the production database connection URL. The export needs an email verification code. The owner can rotate the credentials at any time, which invalidates every exported URL.

### What the AI agent cannot do

The Newly agent works on your development backend. It cannot deploy to production, change production secrets or read production logs. A person on your team makes every production change.

### Certifications

Newly does not hold a SOC 2, SOC 3 or ISO 27001 certification yet. There is no audit report or certificate to share today.

## AI and your data

Newly does not use raw or identifiable personal data to train AI models. The [Terms of Service](https://newly.app/terms) set the rule.

The Terms do let Newly use data that is not personal to run and improve the service, including AI models. The same goes for personal data once it is anonymised and aggregated. To opt out, email [support@newly.app](mailto:support@newly.app) from the email address you sign in with.

AI is used in two places:

| Where | What is sent to an AI provider | Whose data |
| - | - | - |
| The Newly agent that builds your app | Your prompts and the project's code | Yours, as the maker |
| AI features inside your app | The content of each request your app user makes | Your app users' |

AI providers receive only what a request needs, and process it under their own terms. Every AI provider Newly uses is named on the [sub-processor list](https://newly.app/subprocessors).

## Ownership and export

You own your app, its code and its data. The [Terms of Service](https://newly.app/terms) say so, and you can take all of it out of Newly.

| What | How to export it |
| - | - |
| Code | Download it, pull it with the Newly CLI, or keep it in your own GitHub repository. See [Get your code](https://docs.newly.app/code/get-your-code.md) and [Connect GitHub](https://docs.newly.app/code/github.md). |
| Database, including app users' sign-ins | Export the owner connection URL and run `pg_dump`. See [Database backups](https://docs.newly.app/backend/database-backups.md). |
| Uploaded files | There is no one-click export today. Contact support. |
| Secrets | Values cannot be read back out of Newly. Keep your own copy of each key. |

The app is a standard React Native and TypeScript project, and the database is standard Postgres. Nothing in the export depends on a Newly-only format.

## Retention and deletion

| What | How long it is kept |
| - | - |
| A deleted chat | Gone at once. It cannot be restored. |
| A deleted project | Restorable for 30 days, then erased for good. |
| A deleted account | Restorable for 30 days, then erased for good. |
| A backend with no plan and no credits | Paused after 7 days. Erased 90 days after the pause. |
| Billing and tax records | Kept as long as the law requires |

See [Delete a chat, project or account](https://docs.newly.app/account/delete.md) and [Out of credits](https://docs.newly.app/billing/out-of-credits.md).

Your app users' records live in your own database, so you control them. Your backend code can delete one user's rows when they ask.

## Backups

Backups of your app's database are manual. You take snapshots with the Newly CLI, and Newly runs no backup schedule for your app's database. Snapshots cover the database only, not uploaded files. **Restore to here** in the chat brings back your code only.

See [Database backups](https://docs.newly.app/backend/database-backups.md).

## App Store and Google Play privacy forms

You fill in Apple's App Privacy form and Google Play's Data Safety form yourself, because the answers depend on what your app collects. Newly does not submit them for you. Use this list as a starting point. It is not legal advice.

| Part of your app | Data it handles |
| - | - |
| Sign-in, if your app has accounts | Email address, password, and the name and ID from Google or Apple sign-in |
| Your app's own tables | Whatever your app saves. Check your schema in the Database tab. |
| File uploads | The photos and documents your users upload |
| AI features, if your app has them | The text or files in each request, sent to the AI provider |
| Push notifications, if connected | A device push token and identifiers, held by OneSignal |
| In-app purchases, if connected | Purchase history and an app user ID, held by RevenueCat |

Your backend is served over HTTPS, so data is encrypted in transit. Both stores expect you to offer account deletion in your app.

## Still have a question?

Ask in the support chat. See [Getting help](https://docs.newly.app/help/getting-help.md).


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.