Where your customer data actually lives

The claim, and what backs it

Any app can say it respects privacy. What matters is whether the architecture makes the claim structural or merely a policy that could change in the next release.

Here it is structural. The single-user app has no networking path for customer data — there is no endpoint it could be sent to. The team feature deliberately uses infrastructure you already own and control, rather than ours, which means the question "what could Deepliy do with my customer list" has the same answer as "what could Deepliy do with the files in your Drive": nothing.

What this means under GDPR and KVKK

If you keep customer records in personal mode, the app is not transferring personal data to a third party at all — the data stays in your possession on your device, and your obligations are the ordinary ones you already have for a phone that holds customer information: keep it locked, keep a backup, do not lose it.

In team mode, the storage provider is Google Drive under the manager own Google account, on the manager own terms with Google. Deepliy is not introduced as an additional processor holding the records. This is a description of the architecture, not legal advice — if your sector has specific record-keeping duties, check them against your own obligations.

• No customer data is sent to Deepliy in either mode
• No advertising SDK and no ad identifier in the build
• No e-mail address or profile is collected from the app user
• Uninstalling removes the local data along with the app
• Backups are files you hold, not copies we keep

Being precise about the exceptions

Two things do use the network, and both are worth naming rather than hiding. Anonymous crash and usage reporting helps fix the bugs that only appear on devices we do not own; it carries no customer records. Purchases go through Google Play, which is where subscription state lives. Neither touches the customer database.