A little insight.
Only with your choice.

Where this notice applies

Orro Group operates the public TakeApp website and its optional marketing measurement. This notice also describes the optional measurement controls in Android version 1.0.2-meta and later versions that include those controls. It does not add tracking to older installed versions. The device-only version 1.0.0 remains covered by its existing app privacy policy. Online accounts and the CRM are covered by our online account privacy notice.

Other Android data and features

The Android update stores its business workspace on your device. Products and photos, sales, invoices, ledger entries, expenses, tasks, staff records and reservations are not uploaded by the measurement feature or by signing in. Camera access is used when you choose barcode scanning or a photo feature. Exporting a PDF or sharing a bill through WhatsApp or another app sends the chosen file to the destination you select, under that destination's terms.

Optional online email, Google or Facebook sign-in creates or connects a server account. Its identity information, session security, retention and account deletion are described in the online account privacy notice. Clearing Android storage or uninstalling removes local app data; it does not remove server accounts or exported copies. For account deletion or assistance with records under our control, email support@takeapp.in from your registered address. Export records you need before deleting local data.

Optional device-local WhatsApp

Linked WhatsApp sending is separate from Meta marketing measurement and is optional. A desktop browser requires the TakeApp local connector and a paired WhatsApp Web tab; Android uses an account-specific private WebView profile with Android backup disabled. Pairing, sender identity, WhatsApp authentication, messages, PDFs and local reminders stay on the selected device for this feature. TakeApp receives only account/device/platform ownership and lease metadata. Explicitly confirmed sends and consented foreground reminders go directly from the device to WhatsApp; they are not uploaded to TakeApp for delivery or scheduling. Browser reminders support one-time, monthly and yearly schedules and use encrypted IndexedDB. Android reminders currently support one-time schedules stored with Android Keystore encryption.

Keep the relevant browser tabs open with TakeApp active, or keep the Android app in the foreground. Backgrounding, closure or sleep pauses new sends. Missed or uncertain attempts need review; there is no automatic server continuation or blind retry. Existing server credentials and schedules are not automatically migrated. WhatsApp handles received content under its own policies, independently of your analytics choice. See the online account privacy notice and the Android app's bundled privacy policy for storage, disconnection and deletion details.

Your choice comes first

Optional Meta measurement starts off. On the landing website and web CRM, choose Allow analytics or Decline. CRM choices are separate from the landing website and can be changed at https://app.takeapp.in/login?privacy=1, also linked from login, Settings and Preferences. You can change the choice using Privacy choices in the footer. In the Android update, choose whether to allow first-open and app-open measurement, and change it in Settings. Refusing measurement does not prevent downloading the app, signing in, or using its business tools.

Allowing measurement shares the events described below with Meta Platforms. Changing the choice to off stops new measurement requests from TakeApp; it cannot withdraw events already received by Meta. Choices apply separately to each browser and app installation. Clearing storage resets the saved choice. If saving a choice fails, measurement stays off for the current session and the app or website asks you to try saving it again. An older saved choice may still apply after restarting until the new choice is saved successfully.

Public website events

After you allow measurement on takeapp.in, a Meta Pixel image request records a public landing page view and a click on the Android APK download button. We send a fixed public page address and the event type. We do not send private CRM pages, login callback parameters, names, email addresses, customer or supplier details, invoice contents, sales values, staff records or other business records. Automatic advanced matching and automatic server-side Conversions API connections are not enabled by this integration.

Meta receives the request's IP address and browser/network information and may receive cookies already available to its own domain, subject to your browser's settings. Those technical details can identify or associate activity with a browser or Meta account. The website choice is stored locally in your browser. A download-button click measures an attempt to download, not a completed download or an Android installation.

Optional web CRM visits

On app.takeapp.in, optional analytics start off and require a separate CRM choice in this browser. After consent, a PageView image request reports a generic CRM visit with the fixed address https://app.takeapp.in/, the event type and time. The actual route, query, fragment and HTTP referrer are excluded. OAuth callbacks, API routes, storefront routes and unknown document paths are not measured. We do not send account IDs, email addresses, credentials, form entries, screen contents, customer or supplier information, sales values, invoice details, staff records, payment events or other business records.

No Meta JavaScript is loaded by this integration. Meta can receive the network IP, browser details and its own available cookies. The choice is kept in this browser for up to 180 days and can be withdrawn through CRM Privacy choices. Landing-site consent does not enable CRM tracking. The shop at shop.takeapp.in has no Meta tracking from this integration.

Android first measured opens and app opens

The measurement update attempts to send one first-measured-open event per app installation after you opt in, and app-open events while measurement stays allowed. An existing installation can produce its first measured open after an update. This is not a count of new installations or every Google Play download. No events are collected before your choice. Events are not replayed in the background; an unavailable connection can result in a missing event.

TakeApp sends a random app-instance identifier, its app ID/package and version, event time, and the first-measured-open or app-open event type through a direct HTTPS request to Meta's App Events service. Meta also receives the request's IP address and network information. TakeApp does not collect an advertising ID or copy installation referrers for these events, and does not initialize the Meta Android SDK. Business records, login tokens, email addresses, screen text, purchases and payment amounts are excluded. This limited measurement does not provide complete advertising campaign attribution, and does not by itself add display advertisements or a payment feature.

Purpose, recipients and retention

We use the resulting reports to understand how people find and start using TakeApp and assess marketing performance. Meta processes received information for measurement and advertising-related purposes under its privacy policy and Business Tools Terms. Events may be processed outside your country. Reports and identifiers are not anonymous merely because they omit a name.

TakeApp remembers the consent preference locally. Meta retains received event information under its policies and controls; we do not promise a fixed deletion period or that uninstalling erases Meta's records. Contact support@takeapp.in for questions or deletion requests concerning information under our control, and use Meta's privacy controls for information held by Meta. Do not send passwords or unnecessary customer, employee or financial information with a request.

Server workspace storage

Signed-in website and Android accounts save business records to TakeApp servers over HTTPS. Android keeps an encrypted pending copy for interrupted saves and uploads resized product photos. Website and Android records use separate account documents; this release does not merge their different formats. Revision checks reject conflicting saves. Existing device copies are retained for recovery, and a conflict requires your choice before replacement. WhatsApp pairing credentials and device dispatch remain on the device. Server account and record deletion can be requested at support@takeapp.in.