Netzr Expo

Privacy Policy

How personal data is processed in the Netzr Expo mobile app and on the docs.netzr.store document surface.

Bu sayfayı Türkçe okuyun

Version: 1.0 Effective date: 1 September 2026 Last updated: 23 September 2026

1. Who we are and how to reach us

Netzr Expo (the “app”) is operated by CUSTEL FİNANSAL TEKNOLOJİ ANONİM ŞİRKETİ (“we”).
Address: Söğütözü Mah. Söğütözü Cad. No:27 İç Kapı No:2 Çankaya/Ankara, Türkiye

For any question, request or application concerning your personal data: hi@custel.co.

Two terms used throughout this policy

The app is multi-tenant: each organization (tenant) sees only its own data. Throughout this policy two sets of data are treated separately, because they are not the responsibility of the same party:

  • Account Data — the data that identifies you as a user: your name, work email address, the organization you belong to, your role, your session credentials and technical records. We determine the purposes of processing this data, as the operator of the service.
  • Organization Data — everything you put into the app on behalf of the organization you work for: the documents you capture, business cards, lead records, events and notes. The organization you work for decides why it is collected, who may see it and how long it is kept; we host and process it on their instructions.

In practice this means: requests about your Account Data come directly to us, while deletion or correction of Organization Data is your organization’s decision (section 9).

2. What this policy covers

Netzr Expo is a business tool that lets sales teams collect brochures, datasheets, business cards and product photos at trade fairs and on site, share their own digital business card, reach a shared brochure library, and track leads. This policy covers the iOS and Android apps, the backend services they connect to, and the public document surface at docs.netzr.store.

You sign up with your corporate email address and a password. The organization you belong to is determined automatically from your email domain. Free email providers (gmail, outlook, yahoo, yandex and the like) are not accepted; a registration made with such an address is deleted on the server. Your organization’s administrator can also create an account for you by invitation.

3. What data we process and why

3.1 Account and organization data

  • Account: your name, work email address, whether that email is verified, your organization’s code and your role (Member · Admin · super admin). Purpose: authenticating you, isolating each organization’s data, and authorization.
  • Organization (tenant) record: the organization’s code, display name, email domain and status. Purpose: determining which user belongs to which organization.
  • Access request record: when you request “Admin” rights in your organization, the request, any note you wrote, the decision and who made it are recorded. Purpose: keeping authorization auditable.

3.2 Content you capture

  • Documents and photos: brochures, datasheets, technical documents, product photos and stand images, as PDF or JPEG. Purpose: archiving, text recognition (OCR), automatic classification and search.
  • Business card images: kept separately from other documents because they carry personal data. Purpose: creating lead records and archiving. See 3.3.

3.3 Business cards and lead records

When you scan a business card, text is recognised in the image and the name, job title, organization, phone number, email address and website are extracted from it. This becomes a lead record, together with which event the card was scanned at and by whom, its status (hot / pending / closed) and any follow-up notes you add.

This data mostly belongs not to you but to the third party who handed over the card. Their rights are described in section 10.

3.4 Events, notes and data derived from content

  • Events: the event’s name and type, which organization it belongs to, and the identity of the user who created it (user id, email, name).
  • Notes: free-text notes you attach to a capture. If you dictate a note, the audio is transcribed on your device; only the text is sent to the server.
  • Derived from content: the text recognised in the image; the result of automatic classification (document type, company, product, contacts, tags, summary and language); data generated for search, and a technical fingerprint of the file. Purpose: making the archive searchable and preventing the same document being recorded twice.

3.5 Data that stays on your device and is never sent to us

  • Location (optional): when you start an event your approximate location may be read, and it is used only to decide when the event should close by itself. It never leaves your device and is never sent to our servers. If you decline the permission, the event is still created.
  • Your own digital business card: the contact details you share by QR code and vCard are stored on your device and are not sent to our servers.
  • Audio: no recording of your dictation is stored or transmitted.
  • Session credentials: your sign-in keys are held encrypted in the device’s secure key store, behind a biometric gate.
  • Local queue and file copies: so the app works offline, every capture is first written to your device’s disk and upload queue. These copies are cleaned up automatically, as space is needed, once the upload has been verified on the server.

3.6 Technical records

  • Upload records: each capture’s identifier, size, state and timestamps. Purpose: making sure no capture is lost and no file is uploaded twice.
  • Audit record: operations on a document, tenant assignment and CRM transfers are written to an append-only ledger. Purpose: being able to show afterwards what happened.
  • Server logs: structured diagnostic records are kept in our hosting provider’s logging service. Logs for the registration and authorization endpoints never contain names or email addresses; only the user id, organization and role are written. Logs are kept for 90 days.

3.7 What we do not process

The app contains no advertising and uses no tracking technology. We do not collect advertising or device identifiers, and we use no usage analytics, crash reporting or profiling tools. We do not access your contacts, calendar, messages, health or financial data. The iOS app contains no third-party software libraries at all; the only Google component in the Android app is the document scanner, which runs on the device.

4. Legal basis for processing

We process your account and identity data to perform the agreement with you and your organization (KVKK art. 5/2-c; GDPR art. 6(1)(b)). We process document, event and lead data on the basis of our legitimate interest in recording sales activity (KVKK art. 5/2-f; GDPR art. 6(1)(f)). Business card owners’ data is treated under the same legitimate interest, because the card was handed over in order to establish a business relationship.

5. Who we share data with

We do not sell your data and we do not share it with anyone for advertising. The following service providers act only on our instructions, so that we can deliver the service:

Service providers and what each one sees
ProviderWhat it seesPurposeWhere
Amazon Web Services Account and identity data, all document and business card files, all metadata, the audit record and server logs Hosting, storage, database, authentication, secret management and logging Germany (Frankfurt, eu-central-1)
Google Cloud Vision The full image of every document and business card you capture Recognising the text in the image (OCR) Google (United States based)
Anthropic The image and the recognised text Classifying the document automatically, extracting contact details from a business card, and producing event summaries Anthropic (United States based)
Google Drive and Google Sheets A copy of document and business card files; the name and email address of the person who uploaded each file; the event summary sheet A best-effort backup copy and event summary in the organization’s shared drive Google (United States based)
HubSpot Only the contact and company details extracted from a business card, plus the identifier of the related document — no document or card image is sent Transferring the lead into the organization’s CRM Portal hosted in the EU region; provider United States based

About the HubSpot transfer

The CRM transfer does not happen by itself. A lead record is written to the CRM only if (a) the feature is switched on for your organization and (b) you left the “Send to HubSpot” option enabled while scanning the card. The transfer is additive only: fields already filled in on existing CRM records are never overwritten, and no record is ever deleted.

Apart from these, we disclose personal data only where we are legally obliged to do so (a lawful request from a competent public authority).

The app offers no third-party account sign-in — there is no option to sign in with a Google, Apple or other account. Authentication happens only on our own infrastructure.

6. International transfers

Our servers are located in Germany (Frankfurt, eu-central-1); account data, document and business card files, metadata and audit records are held there.

Of the providers listed in section 5, Google Cloud Vision, Anthropic, Google Drive/Sheets and HubSpot are established outside Türkiye, and using these services means personal data is transferred abroad. This includes business card images and the contact details extracted from them.

These transfers are subject to KVKK art. 9 and Chapter V of the GDPR.

7. Retention and deletion

This section describes what the system actually does today.

Retention by type of data
DataHow long it is kept
Account and identity recordUntil the account is deleted. You can delete your own account from inside the app (section 8).
Documents, brochures, datasheets, product photosFor as long as our service relationship with your organization continues. When it ends, your organization is given 90 days to export its data, after which the data is deleted.
Business card images and lead records365 days from the creation of the record. Your organization may set a shorter period. At the end of the period the record and the card image are deleted.
Access request records365 days from the date of the request.
Audit record2 years from the date of the operation, kept in append-only form throughout.
Server logs90 days.
Local copies on your deviceDeleted automatically, as space is needed, once the upload has been verified on the server.

We want to state this plainly

The periods above are binding commitments. Today, however, deletion at the end of those periods is carried out manually by us rather than automatically; an automatic destruction mechanism is being built. To request deletion before the period ends, see section 9.

8. How to delete your account

From inside the app

Go to Settings → Account → “Delete my account”. Once you confirm, your identity record (your user account) is permanently deleted, your session ends, and that account can no longer sign in. If you are your organization’s only administrator, you are warned about this before the deletion.

On the web

If you cannot reach the app, you can request deletion of your account and your data by writing to hi@custel.co. So that we can verify the request, please write from the work email address the account belongs to. Requests are handled within 30 days at the latest.

What happens when you delete your account

  • Deleted: your identity and sign-in record.
  • Not deleted: the documents you captured and the lead records you created on behalf of your organization are organizational data and remain with your organization; your user id, name and email address remain on those records as the “created by” information.
  • If you want that content deleted as well, say so explicitly in your request; it is assessed with your organization’s agreement and carried out manually.

9. Your rights and how to exercise them

Under KVKK art. 11 you have the right to learn whether your personal data is being processed; to request information if it is; to learn the purpose of processing and whether the data is used for that purpose; to know the third parties in Türkiye or abroad to whom it has been transferred; to have incomplete or incorrect data corrected; to request erasure or destruction; to have correction and erasure notified to the third parties the data was transferred to; to object to an adverse outcome arising solely from automated analysis; and to claim compensation for damage caused by unlawful processing.

If you are covered by the GDPR, you also have the rights of access (art. 15), rectification (art. 16), erasure (art. 17), restriction of processing (art. 18), data portability (art. 20) and objection (art. 21). You may object at any time to processing based on legitimate interest.

Where to send a request depends on which data it concerns (section 1):

  • Account Data — write to us directly. You can also delete your account yourself from inside the app (section 8).
  • Organization Data — this is controlled by the organization you work for. Going to your organization’s administrator is the fastest route; requests that reach us are passed on to them.

How to apply: write to hi@custel.co with information that lets us identify you. Applications are answered within 30 days under the KVKK and within one month under the GDPR.

If you are not satisfied with the outcome, you may lodge a complaint with the Turkish Personal Data Protection Board, or — if you are covered by the GDPR — with the data protection authority of your country.

10. People whose business cards were scanned

Even if you are not a user of the app, if you handed your business card to a Netzr user, the image of your card and the contact details on it may exist in the system as a lead record.

All the rights in section 9 apply to you as well. Write to hi@custel.co to ask whether a record about you exists, and to have it corrected or erased. On request, the record and the card image are deleted.

The details taken from your card may also have been transferred to the relevant user’s CRM system, if their organization enabled that feature and the user chose to transfer (section 5). Your deletion request covers that record too.

11. Security

  • Organization isolation: which organization you belong to is read on every request from your verified sign-in credential; the app cannot assert it itself. Members and Admins alike see only their own organization’s data. An Admin’s extra rights concern user and role management inside the organization, not data access.
  • Encryption: all traffic is protected with TLS; files are encrypted at rest with AES-256 and the storage is closed to the public internet.
  • On the device: sign-in credentials are held in the operating system’s secure key store, bound to that device and readable only while the device is unlocked, behind a biometric gate.
  • Keys stay on the server: access keys for our service providers never reach the app.
  • Access and auditing: the raw text recognised from a document is shown in the interface only to a platform administrator, and operations on a document are written to an append-only ledger.

No system offers absolute security; the measures described here reduce risk.

12. Cookies and docs.netzr.store

The mobile app uses no cookies.

The document surface at docs.netzr.store (this page, product document links and the document catalogue) is public and sets no cookies at all. The pages load no external scripts, fonts, images or analytics tools; there are no advertising or tracking cookies.

The only exception is the password-protected document upload portal, used by authorised people only. When you sign in to the portal with the password, a single strictly necessary session cookie is set:

  • It is named __Host-nzp and lasts 12 hours.
  • It carries nothing but the validity of the session; it does not identify a person, does not track, and is not shared with third parties.
  • It is sent over HTTPS only, cannot be read by browser scripts, and is not sent with requests coming from other sites.

The portal also holds the IP address of the request temporarily in server memory in order to limit password guessing attempts; it is not stored permanently.

13. Who the service is for, and minors

Netzr Expo is made available for corporate use only. Opening an account requires a corporate email address belonging to an organization, and registrations made with free email providers are rejected by the system (section 2). The service is therefore not directed at consumers generally or at anyone under 18, and it is not designed to process the personal data of minors.

If we establish that a user is under 18, the account is closed and the identity record is deleted.

14. Changes to this policy

This policy is updated whenever the app’s behaviour changes. The current text is always published on this page and the “Last updated” date at the top of the page changes. Material changes are announced in the app.

15. Contact

CUSTEL FİNANSAL TEKNOLOJİ ANONİM ŞİRKETİ
Söğütözü Mah. Söğütözü Cad. No:27 İç Kapı No:2 Çankaya/Ankara, Türkiye
hi@custel.co

↑ Back to top