Nektar LogoNektar

Nektar · Data

Data Processing Notice

A concise notice about the main personal-data processing carried out across Nektar’s website and mobile services.

Last updated
17 July 2026
Controller
Ömer Doğan (Nektar)
Rights contact
destek@nektar.dev

Important note for your region

United States: COPPA warning

Before collecting from a child under 13, COPPA can require direct parental notice and verifiable parental consent. Parents should be able to review, delete and stop further use.

US Federal Trade Commission (FTC)

This short alert is not a complete statement of federal or state law.

1. Purpose of this notice

This notice explains the core personal-data processing carried out when you use Nektar. The controller is Ömer Doğan (Nektar). It is provided for information and is not a request for consent. Where an optional purpose legally requires consent, that choice is presented separately and freely.

2. Data, purposes and legal bases

  • Account and profile data is used to create and secure the account, perform the user agreement, provide requested features and remember choices. Depending on the processing, the basis may be contract, steps requested before contract, legal obligations, legitimate interests or consent for genuinely optional processing.
  • Learning, community, AI prompts and selected scan images are used to return explanations, store progress, prevent misuse and keep the service reliable. The basis may be contract, legitimate interests, legal duties or separate consent where required.
  • Waitlist and contact data is used to record your request, send requested early-access updates, reply and investigate technical issues. The basis may be your request, pre-contract steps, legitimate interests or consent depending on the communication.
  • Device, network, security, notification, analytics, advertising and subscription data is used to operate and protect Nektar, measure it, deliver permitted ads and manage payments. The basis depends on the technology and country and may be contract, legal duty, legitimate interests or consent.

3. Collection method

Data is received directly from you, electronically from your device while you use a feature, through web forms and storage technologies, and from the sign-in, store or subscription provider you select. Non-essential website analytics and marketing tools remain off until you choose.

4. Recipients and transfers

Relevant data may be disclosed for the stated purpose to Supabase, OpenAI, Google services, Microsoft Clarity, Meta, Expo, Apple, Adapty, authorised infrastructure providers and legally competent authorities. Profile fields you deliberately make public can be visible to other users.

International transfers must use the route required by applicable law, such as adequacy, standard contractual clauses, binding corporate rules, an approved undertaking or another appropriate safeguard. An exceptional consent route must be separate and informed.

5. Retention and rights

Data is kept while needed for the purpose and account relationship, then only for the limited period required for security, disputes, payments, backups and legal records before deletion or anonymisation.

Depending on where you live, you may request access, correction, deletion, restriction, objection or a copy; withdraw consent without affecting earlier processing; and complain to your local authority. Send requests to destek@nektar.dev. We may verify identity proportionately.