Skip to main content

Privacy Policy

Anacan privacy policy: information about data collection, use, advertising services, and your choices.

Effective date: 5 March 2026 · Version: 1.0

1. Summary

Anacan never sells your health data, never uses it for advertising, and processes it only with your explicit consent. This Policy applies to the anacan.az website, the Anacan mobile app (iOS and Android) and related services (hereinafter the "Service").

Our commitmentWhat it means
Health data is not soldWe do not sell or rent pregnancy, cycle, symptom or child health data to anyone, and we do not pass it on to advertising networks, insurance companies or employers.
Explicit consentHealth data is processed only with your separate, explicit consent; you can withdraw your consent at any time.
Data minimisationWe collect only what is necessary for a feature to work.
Restricted staff accessOur staff may see your health data only at your request, with your consent, for a limited time and with logging.
Strong protectionTLS 1.2+ encryption in transit and AES-256 encryption at rest.
You are in full controlYou can download and correct your data in the app and delete it completely using the delete account button.
Global standardThe app is distributed in all countries where the App Store and Google Play are available; we apply the strictest standard — the EU General Data Protection Regulation (GDPR) — as the baseline for all users. Where local law requires more protection, local law prevails (Section 13).

Anacan is not a medical device and does not replace a doctor's advice. The rules for using the Service are set out in the separate Terms of Use.

2. Who we are and to whom this Policy applies

The controller of your data (within the meaning of Article 4(7) GDPR) is "ANACAN" LLC, registered in the Republic of Azerbaijan (TIN 1407578211; hereinafter "Anacan", "we").

RoleDetails
Controller"ANACAN" LLC, TIN 1407578211, 150 Shamil Azizbeyov St., Baku, Azerbaijan
Data Protection Officer (DPO)Jamil Sultanli, privacy@anacan.az
EU representative (Art. 27 GDPR)Appointment in progress; will be listed here once appointed. Currently: privacy@anacan.az
UK representative (Art. 27 UK GDPR)Appointment in progress; will be listed here once appointed. Currently: privacy@anacan.az
Other local representativesAppointed where required by local law and listed here

Users in the EU and the United Kingdom may contact our representative instead of, or in addition to, us on any data protection matter (until a representative is appointed, please write to privacy@anacan.az).

What this Policy covers

  • The anacan.az website and its subdomains
  • The Anacan mobile app (App Store, Google Play and other app stores)
  • Newsletters, push notifications, customer support, surveys and campaigns
  • The Anacan.AI assistant and community (forum) features
  • Cookies and similar technologies used on the website and in the app

What it does not cover

  • Third-party websites and services opened via links from the Service (their own policies apply)
  • Data of Anacan employees and job applicants (separate internal policy)
  • Data processed by Apple, Google and payment services themselves as independent controllers

3. What data we collect

We obtain data in three ways: you provide it, it is generated automatically when you use the Service, and in limited cases we receive it from partners (e.g. subscription status from the app store).

CategoryExamplesSourceMandatory?
Account dataName (or nickname), e-mail, password hash, sign-in method (Apple, Google), language, countryYouYes, to create an account
Profile dataLife stage (planning, pregnancy, parenthood)YouNo
Health data (special category)Pregnancy week, estimated due date, menstrual cycle, ovulation, symptoms, mood, weight, blood pressure, test results, medications, fetal movements, contractions, IVF, pregnancy loss, type of deliveryYouNo — only with explicit consent
Data about the childName (optional), date of birth, sex, height, weight, feeding, sleep, vaccinations, developmental milestones, photosYou (the parent)No
AI assistantQuestions you write to Anacan.AI and the answersYouNo — only with consent
Community contentForum posts, comments, likesYouNo
Payment dataSubscription type, purchase date, country, transaction ID. We do not see or store your card number — payments are processed by Apple, Google or, on the website, Epoint (bank payment page)App store, payment providerYes, for paid features
Device and technical dataDevice model, operating system, app version, language, time zone, IP address, error logs, push tokenAutomaticYes, for technical operation
Usage dataScreens opened, features used, session duration (without health content)AutomaticIn the app with analytics consent; on the website by default, with the option to opt out
Approximate locationCountry and city based on IPAutomaticYes (for language, law and content)
Precise locationGPS (e.g. map of nearby maternity hospitals and pharmacies)DeviceNo — only with permission, not stored
Contact and supportRequests, correspondence, feedbackYouNo

Special notes on sensitive data

  • Under Article 9 GDPR, health data is a "special category" of data and is stored at the highest level of protection.
  • Menstrual cycle, pregnancy and pregnancy loss data may carry legal risk in some countries. We therefore disclose such data only where required by law and only after it has passed the review described in Section 7.4.
  • We do not collect biometric data, facial recognition data, genetic data, or data about race, religion, political opinions or sex life. The Face ID / fingerprint check for the app lock is performed on your device and is not transmitted to us. Please do not enter such information in free-text fields.
  • We access your photo gallery, camera and microphone only at the moment you open the relevant feature and only with your permission.

4. Purposes and legal bases

Every processing operation is based on one of the legal bases in Article 6 GDPR and, for health data, additionally on Article 9(2)(a) (explicit consent). We do not rely on "legitimate interest" for health data.

PurposeData categoriesLegal basis
Creating and managing the accountAccount, devicePerformance of a contract — Art. 6(1)(b)
Personal pregnancy, cycle and baby calendars, reminders, tracking toolsHealth, childExplicit consent — Art. 9(2)(a) and Art. 6(1)(a)
Personalising content by pregnancy week or child's ageHealth, childExplicit consent — Art. 9(2)(a)
Anacan.AI assistantYour questions, the context you selectExplicit consent — Art. 9(2)(a) and Art. 6(1)(a)
Subscriptions and paymentsPayment, accountContract — Art. 6(1)(b); legal obligation for tax records — Art. 6(1)(c)
Technical support and responding to requestsAccount, contact; health only with your consentContract — Art. 6(1)(b); Art. 9(2)(a) for health
Security, fraud prevention, abuse detectionDevice, technical, accountLegitimate interest — Art. 6(1)(f)
Bug fixing and stabilityDevice, technicalLegitimate interest — Art. 6(1)(f)
Analytics to improve the productUsage (without health content)In the app: consent — Art. 6(1)(a); on the website: legitimate interest — Art. 6(1)(f), with the right to opt out (consent in the EEA, UK and Switzerland)
Advertising and ad measurement in the free versionAdvertising identifier, device (without health content)Consent for personalised advertising and measurement — Art. 6(1)(a); legitimate interest for non-personalised advertising — Art. 6(1)(f)
Anonymised, aggregated statisticsAnonymous dataAnonymous data is not personal data; the original consent for the anonymisation process itself
Service notices (security, changes to terms)AccountContract — Art. 6(1)(b); legal obligation — Art. 6(1)(c)
Marketing e-mails and push notificationsAccount, contactConsent — Art. 6(1)(a); opt out at any time
Community moderation and tackling illegal contentCommunity contentLegitimate interest — Art. 6(1)(f); legal obligation under the EU Digital Services Act — Art. 6(1)(c)
Defending legal claims, lawful requestsTo the extent necessaryLegal obligation — Art. 6(1)(c); Art. 9(2)(f)
Protecting vital interests in a medical emergency (exceptional case)Minimum necessaryVital interest — Art. 6(1)(d), Art. 9(2)(c)

How we obtain explicit consent

  • Consent is obtained on a separate screen, with options that are not pre-ticked, explaining in plain language which data will be used and for what purpose.
  • Consent is separated by purpose (health data, AI assistant, marketing, analytics). Consent to one does not mean consent to another.
  • Analytics and marketing consent is not a condition for using the Service.
  • The date, version and type of consent are recorded as evidence.
  • Withdrawing consent: in the app, Profile → Privacy → Consents. Withdrawal does not affect the lawfulness of prior processing. When you withdraw health consent, you can request deletion of the related data; we carry out your request within 30 days and, if you wish, let you export it first.

About legitimate interest

We rely on legitimate interest only for security, technical stability, non-personalised advertising and moderation. A legitimate interest assessment (LIA) has been carried out and documented for each of these; we provide a short summary on request. You may object to this processing under Article 21 GDPR.

5. Cookies, SDKs, analytics and advertising

On the website (anacan.az) Google Analytics 4 is on by default: it measures site traffic and link clicks on the basis of legitimate interest, and you can switch it off at any time through the "Cookie settings" link at the bottom of the site. For visitors from the European Economic Area, the United Kingdom and Switzerland, analytics cookies are activated only after consent. In the app, non-essential SDKs are activated only after you give your consent. Health data is never passed to any advertising or analytics SDK.

CategoryPurposeConsent required?Example tools
EssentialSign-in, security, language selection, remembering consent choices, cartNoOur own cookies and local storage (localStorage), Google Cloud
AnalyticsUnderstanding which sections are usedApp: yes; website: no, you can opt out (yes in the EEA, UK and Switzerland)Google Analytics 4 on the website; Google Analytics for Firebase in the app
Advertising (free version of the app only)Showing ads and measuring ad performanceYes, for personalised advertising and measurementGoogle AdMob; Meta App Events (only with "Ad measurement" consent)

Third-party SDKs we use in the app: Google Analytics for Firebase, Firebase Cloud Messaging, Customer.io, RevenueCat, Google AdMob and Meta App Events. Advertising and analytics SDKs operate only in line with your choices; Premium subscribers are not shown ads.

Managing consent

  • On your first visit to the website a cookie banner is shown: the "Accept" and "Essential only" buttons are the same size and at the same level. If you make no choice, website analytics stays on (except in the EEA, UK and Switzerland); choosing "Essential only" switches it off.
  • You can change your choice at any time via the "Cookie settings" link at the bottom of the website or in the app under Profile → Privacy.
  • Consent is requested again every 6 months; if you decline, we remember that choice and do not ask again on every visit.
  • We recognise your browser's "Global Privacy Control" (GPC) signal and treat it as a rejection of non-essential cookies and as an opt-out of "sale/sharing".
  • On iOS we do not collect the advertising identifier (IDFA) without Apple's "App Tracking Transparency" permission. In the app, consent for personalised advertising is requested via Google's consent dialog.

Our advertising rules

  • Health data, pregnancy or cycle status, and sensitive events such as pregnancy loss are not passed to advertising networks, social media pixels or data brokers — not even as "events".
  • Ads shown in the free version are not based on your personal health profile; personalised ads are shown only with your consent.
  • We send Anacan's own product recommendations (e.g. an offer matched to your pregnancy week) by push or e-mail only if you have given separate marketing consent.
  • Personalised ads are not shown to users we know to be under 18.
  • When a pregnancy loss is recorded, all pregnancy- and baby-related marketing notifications are stopped immediately.

6. Age limit and data about children

The minimum age for independent use of Anacan is 16; if the law of your country requires a higher age (the digital age of consent), that age applies.

Age limit

  • During registration we ask you to confirm that you are over 16; users who do not confirm cannot use the account.
  • We do not knowingly collect data from children under 13 (including as required by COPPA in the US).
  • For users who are above the minimum age but under 18, no personalised advertising or marketing profile is created, and content is presented in an age-appropriate way.
  • If we learn that a person below the minimum age has created an account, we delete the account and data as soon as possible. Please report such cases to privacy@anacan.az.

Child data entered by a parent

In features such as the baby diary, development calendar and vaccination reminders, data about your child is entered by you — the parent or legal guardian.

  • By entering this data you confirm that you are the child's parent or legal guardian and that you have the right to give consent on the child's behalf.
  • Child data is stored at the same (highest) level of protection as your health data and is not used for any advertising or profiling.
  • Your child's photos are stored privately in your account only; they are not visible to anyone unless you yourself share them in the community. We recommend that you take care when sharing a child's photo in the community.
  • You can delete a child profile separately at any time.
  • If two parents use a shared profile (the "Partner invitation" feature), the inviting person chooses which data is shared and can stop sharing at any time.

7. Who we share data with

We share your data only in the cases below, on the basis of a written contract and to the minimum extent necessary. We never sell your personal data.

7.1. Processors (services acting on our behalf)

CategoryPurposeReceives health data?Provider
Cloud hosting and databaseOperation of the ServiceYes, in encrypted formGoogle Cloud (Google LLC), Belgium
E-mail and push notification deliveryNotificationsNo (texts are written neutrally)Customer.io, Inc.; Firebase Cloud Messaging (Google LLC)
SupportRequestsOnly if you write itGoogle Workspace (Google LLC)
AnalyticsProduct improvementNoGoogle Analytics, Firebase (Google LLC)
Subscription managementVerification of store purchasesNoRevenueCat, Inc.
Card payments on the websitePayments for subscriptions, books and cakesNoEpoint (bank payment page)
Advertising (free version)Showing and measuring adsNoGoogle AdMob (Google LLC); Meta Platforms (only with "Ad measurement" consent)
Security and CDNProtection against attacksNoGoogle Cloud (Google LLC)
Enterprise AI serviceAnacan.AI assistant (Section 12)Only with your consent; the provider does not use the data to train its own modelsGoogle Gemini, Vertex AI (Google LLC)
Translation of community postsDisplaying posts in other languagesOnly if you write it in a post yourselfAnthropic, PBC; Microsoft Azure OpenAI

A data processing agreement (DPA) in accordance with Article 28 GDPR is concluded with each processor. Suppliers that process health data undergo a security review in advance. When we add a new processor, we update this table at least 15 days in advance.

7.2. Independent parties

  • Apple, Google and payment providers — for processing payments; they are independent controllers acting under their own policies.
  • Exports by you — when you yourself send data to your doctor or to services such as Apple Health / Health Connect.
  • Professional advisers — lawyers, auditors (bound by confidentiality obligations).
  • Merger or sale of the company — in that case the new owner will have to accept the obligations in this Policy; we will notify you in advance, and health data may not be used for a different purpose without new consent.

7.3. What we never do

  • Pass data to data brokers, insurance companies, credit institutions or employers.
  • Share health data for advertising or "cross-context behavioral advertising" purposes.
  • Share identifiable data for scientific research without your separate consent.

7.4. Requests from public authorities

Requests from law enforcement and other public authorities are handled only by our legal team and the DPO.

  • Data is disclosed only in the manner prescribed by law, on the basis of an official written request and to the minimum extent.
  • We verify the lawfulness of each request and challenge overly broad or unfounded requests.
  • We pay particular attention to requests concerning reproductive health data (cycle, pregnancy, pregnancy loss) and use all available legal remedies.
  • Unless prohibited by law, we inform you about the request.
  • Every request is recorded in a register; we publish the number of requests in an annual transparency report.

8. International transfers

Your data is stored on Google Cloud infrastructure, on servers located in the European Union (Belgium); transfers outside your country take place only under one of the legal mechanisms below and with supplementary safeguards.

Transfer directionLegal mechanism
EU/EEA → country with an adequacy decision (e.g. UK, Switzerland, Japan, Canada)European Commission adequacy decision — Art. 45 GDPR
EU/EEA → USAIf the provider is certified under the EU–US Data Privacy Framework — Art. 45; otherwise Standard Contractual Clauses
EU/EEA → other countries, including AzerbaijanEuropean Commission Standard Contractual Clauses (SCC, 2021) — Art. 46(2)(c) and a transfer impact assessment (TIA)
UK → other countriesUK International Data Transfer Agreement (IDTA) or the UK Addendum to the SCC
Türkiye → abroadStandard contract under KVKK; notification to the Personal Data Protection Authority within 5 business days after the contract is signed
Other countriesMechanism recognised by that country's law (standard contract, consent, etc.) — Section 13

Supplementary safeguards

  • Encryption in transit and at rest; access to encryption keys is strictly limited.
  • Where possible, data is pseudonymised before transfer.
  • Requests from foreign public authorities are reviewed and challenged in accordance with Section 7.4.
  • You can obtain a copy of the Standard Contractual Clauses by sending a request to privacy@anacan.az (parts containing trade secrets may be redacted).

9. Retention periods

We keep data only for as long as necessary for the purpose; when an account is deleted, health data is deleted from active systems within 30 days and from backups within 90 days.

DataRetention periodAfterwards
Account dataWhile the account is activeDeleted within 30 days after the deletion request
Health and child dataWhile the account is active and consent remains in effectDeleted within 30 days when the account is deleted or when you withdraw consent and request deletion
BackupsUp to 90 daysAutomatically overwritten; deleted data is deleted again upon restoration
Inactive account24 months of inactivityThe account is deleted 30 days after a warning
AI chat historyWhile the account is active; you can delete it at any timeDeleted when the account is deleted
Community postsUntil you delete themDeleted when the account is deleted
Payment recordsThe period required by Azerbaijani tax and accounting legislationDeleted
Support requests2 years after closureDeleted
Technical and security logsUp to 90 days; for incident investigation, not exceeding 12 monthsDeleted
Analytics data14 monthsAggregated or deleted
Consent records3 years after consent is withdrawn (as evidence)Deleted
Register of public authority requests5 yearsDeleted

Once the period expires, data is deleted or irreversibly anonymised. If a legal dispute or lawful request is ongoing, the relevant data is kept in blocked form only until that matter is concluded.

10. Security and incidents

We protect health data as the highest risk category and, in the event of a data breach, we notify you without waiting.

Technical and organisational measures

  • Encryption: TLS 1.2+ in transit, AES-256 at rest (server disks and backups); encryption keys are held by Google Cloud's managed key service.
  • Access control: principle of least privilege, multi-factor authentication for staff; access to health data is logged and regularly reviewed.
  • Protecting your account: option to lock the app with a PIN, Face ID or fingerprint; e-mail verification.
  • Secure development: code review, vulnerability scanning of dependencies, an independent penetration test at least once a year.
  • Staff: confidentiality undertakings are signed and annual data protection training is completed.
  • Assessment: a data protection impact assessment (DPIA) is carried out for every new feature that processes health data — Art. 35 GDPR.

If a data breach occurs

  1. We immediately contain the incident, investigate its cause and record it.
  2. If there is a risk, we notify the supervisory authority within 72 hours of becoming aware of it (Art. 33 GDPR); in other countries we comply with the deadline set by local law.
  3. If the breach poses a high risk to your rights and freedoms, we inform you without undue delay of what happened, which data was affected and how you can protect yourself (Art. 34 GDPR).
  4. If health data is affected, we inform the affected users regardless of the risk level.

If you have found a vulnerability, please write to security@anacan.az. We do not bring legal claims over vulnerabilities reported in good faith.

11. Your rights and how to exercise them

Wherever you live, we guarantee all users the rights below; we respond to requests free of charge and within 1 month.

RightWhat it meansHow to exercise it
Access (Art. 15)Learn which of your data we process and why, and receive a copyProfile → Settings → Data export; privacy@anacan.az
Rectification (Art. 16)Correct inaccurate or incomplete dataEdit directly in the app or contact support
Erasure (Art. 17)Complete deletion of your data or accountProfile → Settings → Privacy & Data → Delete account; you can also delete individual entries and the child profile separately
Restriction of processing (Art. 18)Suspend the use of data until a dispute is resolvedprivacy@anacan.az
Portability (Art. 20)Receive data in a machine-readable format (JSON) or transfer it to another serviceProfile → Settings → Data export
Objection (Art. 21)Object to processing based on legitimate interest and to direct marketingProfile → Privacy → Consents; privacy@anacan.az
Withdrawal of consent (Art. 7(3))Revoke any consent given at any timeProfile → Privacy → Consents
Not to be subject to automated decisions (Art. 22)Not to be subject to decisions with legal effects based solely on automated processingSection 12
Complaint (Art. 77)Lodge a complaint with a supervisory authoritySection 14

How requests are handled

  • You can submit a request from the app or by writing to privacy@anacan.az.
  • We verify your identity by sign-in to your account or via your registered e-mail; we do not ask for more documents than necessary.
  • The response time is 1 month; for complex requests it may be extended by 2 months, with the reason explained. Where local law requires a shorter period, that period applies (Section 13).
  • An authorised representative may submit a request on your behalf with a written power of attorney.
  • If we refuse a request, we inform you in writing of the reason and of your right to complain.
  • Exercising your rights does not change your level of service or price.

12. AI features and automated decisions

Anacan does not make fully automated decisions about you that produce legal or similarly significant effects; the AI assistant provides only informational answers and does not make diagnoses.

Anacan.AI assistant

  • The AI assistant is an optional feature; separate consent is requested on first use. If you do not consent, the rest of the Service works fully.
  • What you write to the assistant and the context used to make the answer more accurate (e.g. pregnancy week) are transmitted to Google's Gemini service (Section 7.1). Google does not use this data to train its own models and retains it only for the limited period provided for in the contract terms, to prevent abuse.
  • You can view and delete your chat history in the app.
  • We do not use your chats to train our own AI models.
  • AI answers may be wrong. If urgent symptoms are mentioned (bleeding, severe pain, reduced fetal movements, etc.), the assistant advises you to contact a doctor or emergency services immediately.
  • In the EU this feature operates in accordance with the transparency requirements of the EU AI Act: it is clearly indicated that you are interacting with AI.

Personalisation and profiling

Selecting content by pregnancy week or child's age is done using simple rules based on the stage information you enter and has no legal effect on you. No profile is created on the basis of health data for decisions such as credit, insurance or employment.

Community

What you write in the forum is visible to other users. We recommend posting under a nickname and not sharing recognisable photos of your face or your child, or information such as your address and phone number. Automatic filters are used in moderation, but the final decision is made by a moderator; you can appeal a decision.

13. Additional regional provisions

This Policy is based on the GDPR; the table below shows only cases where local law grants additional rights or different time limits. In case of conflict, the rule that gives you greater protection applies.

RegionLawAdditional provisions
AzerbaijanLaw "On Personal Data" (2010)Consent is obtained in written or electronic form; complaints may be filed with the competent public authority or a court
EU / EEAGDPR; Digital Services Act; AI ActRight to lodge a complaint with the supervisory authority of the country where you live, work or where the infringement occurred; the EU representative will be listed in Section 2 once appointed
United KingdomUK GDPR, Data Protection Act 2018Complaints — Information Commissioner's Office (ICO)
SwitzerlandFederal Act on Data Protection (FADP)Complaints — Federal Data Protection and Information Commissioner (FDPIC)
USA — CaliforniaCCPA / CPRARight to know, delete, correct, opt out of "sale/sharing" and limit the use of sensitive information. We do not sell personal data and do not share health data for cross-context advertising; the GPC signal is recognised. Response time 45 days
USA — Washington, Nevada, Connecticut and other statesWashington My Health My Data Act, Nevada SB 370 and state consumer privacy laws"Consumer health data" is collected and shared only with separate consent; we do not sell health data; we do not use geofencing (virtual boundaries) around healthcare facilities. Right to appeal a refused request
USA — federalCOPPANo data is knowingly collected from children under 13 (Section 6)
CanadaPIPEDA; Quebec — Law 25Person in charge of privacy: Jamil Sultanli, privacy@anacan.az; complaints — Office of the Privacy Commissioner of Canada or, in Quebec, the Commission d'accès à l'information
BrazilLGPD (Law 13.709/2018)Data protection officer (encarregado): Jamil Sultanli, privacy@anacan.az; response to a full data request within 15 days; complaints — ANPD
TürkiyeKVKK (Law 6698)Explicit consent (açık rıza) for health data and a separate information notice (aydınlatma); response to requests within 30 days; contact us first, then the KVKK Board. For users in Türkiye, the Turkish-language KVKK Aydınlatma Metni and Açık Rıza Metinleri apply
Gulf countriesSaudi Arabia PDPL, UAE PDPLHealth data is a sensitive category; transfers abroad in accordance with local rules
IndiaDigital Personal Data Protection Act (DPDP, 2023)Grievance officer: Jamil Sultanli, privacy@anacan.az; ability to manage consent in the app; complaints — Data Protection Board of India
Japan, South KoreaAPPI; PIPASeparate consent for transfers abroad where required
Other countriesLocal lawAdditional requirements of local law apply together with this Policy

14. Changes, contact and right to complain

We notify you of material changes to the Policy at least 30 days in advance; you can send your questions and complaints to privacy@anacan.az.

Changes to the Policy

  • We inform you of material changes (a new purpose, a new data category, a new type of recipient) 30 days in advance by in-app notice and e-mail.
  • If a change involves using health data for a new purpose, we obtain your new explicit consent; if you do not consent, your data continues to be processed under the previous rules.
  • Minor amendments (clarifications, typos, contact details) take effect on the day of publication.
  • You can obtain previous versions by writing to privacy@anacan.az.

Contact

MatterContact
Privacy requests and your rightsprivacy@anacan.az; in the app under Profile → Privacy
Data Protection Officer (DPO)Jamil Sultanli, privacy@anacan.az
Security vulnerabilitiessecurity@anacan.az
Postal address"ANACAN" LLC (TIN 1407578211), 150 Shamil Azizbeyov St., Baku, Azerbaijan
EU / UK representativesSection 2

Right to complain

We ask that you write to us first: we investigate complaints and reply in writing within 1 month. If you disagree with our response, or without writing to us, you may at any time lodge a complaint with the data protection authority of the country where you live (Section 13). A list of EU supervisory authorities is published on the website of the European Data Protection Board (EDPB).

Language and entry into force

The Policy is published in all languages supported by the app. In the event of any discrepancy between the texts, the Azerbaijani text prevails, unless local law requires otherwise.

Effective date: 5 March 2026 · Version: 1.0

privacy@anacan.az