Soft-D Lab does not require a user account and does not directly ask for your name, phone number, contacts, precise location, photos, messages, payment-card details, or health information in the current applications. The applications do include AppsFlyer for installation attribution and measurement and Firebase Crashlytics for stability diagnostics. Those SDKs automatically process limited device, identifier, app-interaction, and crash information as described below. Contacting support also gives us the information you choose to include in your message.
1. Scope and controller
This Privacy Policy applies to mobile applications published by Soft-D Lab (the “Apps”), the public pages at softdlab.com (the “Website”), and related support communications. “Soft-D Lab,” “we,” “us,” and “our” refer to the developer and operator identified as Soft-D Lab in the applicable app-store listing.
For data-protection laws that use the terms “controller” or “business,” Soft-D Lab determines why and how the processing described here occurs, except where a provider independently determines its own purposes under its privacy terms.
Email: privacy@softdlab.com
General legal inquiries: support@softdlab.com
2. Information processed
The exact data available to an SDK can vary by operating system, device settings, SDK version, consent status, and our configuration. We use data minimization and do not intentionally configure either SDK to receive names, email addresses, phone numbers, precise GPS location, contact lists, payment data, health data, message content, or other sensitive content.
| Source | Categories and examples | Purpose |
|---|---|---|
| AppsFlyer | App-install and launch information; attribution and limited engagement events; timestamps; app version; device type and model; operating-system version; language, time zone, carrier and network status; IP address and user agent; AppsFlyer installation identifier; and, when available under platform rules and your settings, advertising identifiers such as IDFA or GAID. | Attribute installations to a source, measure whether distribution efforts work, produce aggregate product insights, and detect attribution fraud. We do not use AppsFlyer data to identify you by name. |
| Firebase Crashlytics | Crash and non-fatal error stack traces; exception type and message; relevant application state; crash timestamp; app identifier and version; device model, CPU architecture, memory and disk status; operating-system version; root or jailbreak state; Crashlytics Installation UUID; Firebase installation ID; and Firebase session ID. Developer-defined diagnostic logs or keys may be attached, but we do not intentionally place direct identifiers or user content in them. | Detect, group, reproduce, prioritize, and repair crashes and stability problems; measure how many app installations are affected. |
| Support and privacy requests | Your email address, message, app/platform information, and any files or diagnostic details you voluntarily send. Please do not send passwords, authentication codes, payment-card data, government identifiers, or unrelated sensitive information. | Respond to the request, troubleshoot a reported issue, verify and complete a privacy-right request, keep necessary records, and prevent abuse. |
| Website infrastructure | Standard request and security data that hosting or network providers may process, such as IP address, browser or user agent, requested URL, response status, and timestamp. Public legal pages do not use advertising cookies. Essential authentication cookies may be used only if an authorized administrator signs in. | Deliver the Website, maintain availability, diagnose errors, and protect the service against fraud, abuse, and attacks. |
Apple and Google separately process information when you download, purchase, update, or review an App. Their processing is governed by their own privacy notices and is not controlled by this Policy.
3. Purposes and legal bases
We limit processing to the purposes shown above. For people in the European Economic Area, United Kingdom, or another jurisdiction requiring a legal basis, we rely on:
- Consent where the law or platform rules require permission for an advertising identifier, tracking, or similar measurement. Consent can be withdrawn through the available in-app or device control without affecting earlier lawful processing.
- Legitimate interests in keeping the Apps secure and reliable, understanding aggregate installation performance, preventing fraud, and improving stability, balanced against your rights and expectations.
- Contract or steps at your request when we respond to support you asked us to provide.
- Legal obligations and legal claims where records are necessary to comply with law, protect rights, or establish, exercise, or defend a claim.
We do not use the described data for automated decisions that produce legal or similarly significant effects about you.
5. Retention
- Crashlytics: Google states that Crashlytics crash stack traces, extracted minidump data, and associated identifiers are retained for 90 days before removal from live and backup systems begins; NDK minidump data is held temporarily for processing.
- AppsFlyer: AppsFlyer states that end-user data is retained for no more than 24 months unless a customer directs otherwise or a longer period is permitted or required by law. We do not direct AppsFlyer to retain identifiable end-user data longer than necessary for the purposes in this Policy. Aggregated, irreversibly de-identified statistics may be retained longer.
- Support and privacy correspondence: normally up to 24 months after resolution, and longer only where necessary for security, a legal obligation, or a legal claim.
- Website security records: only as long as reasonably needed for delivery, troubleshooting, and incident response; where we control the setting, we aim to keep identifiable logs no longer than 90 days unless an incident or law requires more time.
Deletion from encrypted backups or vendor systems may occur on the provider’s normal rotation schedule. We restrict further use while deletion is pending, except as required by law.
6. International data transfers
Soft-D Lab and its providers may process information in the United States, Israel, the European Economic Area, and other countries where they operate. When European or UK personal data is transferred to a country without an adequacy decision, we rely on an appropriate safeguard made available under applicable law, such as approved Standard Contractual Clauses, together with supplementary security measures where required. You may contact us for information about the relevant safeguard.
7. Security
We use administrative, technical, and organizational safeguards appropriate to the limited data and risk, including encrypted transmission, access controls, least-privilege administration, software and dependency updates, separation of production access, logging for security, and providers with contractual security commitments. No internet or storage system is perfectly secure, so we cannot guarantee absolute security.
8. Your choices and privacy rights
Device choices
- Use iOS tracking controls or Android advertising-privacy settings to restrict access to advertising identifiers where available.
- Reset or delete the device advertising identifier through the operating system.
- Uninstalling the App stops future SDK collection from that installation, but does not automatically delete information already retained.
EEA, UK, and similar rights
Subject to legal conditions and exceptions, you may request access, correction, deletion, restriction, or portability; object to processing based on legitimate interests; withdraw consent; and complain to your local data-protection authority. You also have the right not to be subject to a solely automated decision with legal or similarly significant effects.
United States state privacy rights
Residents of California and other states may, where the applicable law covers our processing, request access or knowledge, correction, deletion, and portability; opt out of sale, sharing, targeted advertising, or qualifying profiling; limit certain uses of sensitive information; appeal a refusal; and exercise rights without unlawful discrimination. We do not sell personal information, share it for cross-context behavioral advertising, or use sensitive personal information to infer characteristics.
To exercise a right, email privacy@softdlab.com. State the App, platform, type of request, and enough context to locate the relevant record. Do not send an advertising identifier or other sensitive identifier in your first email; we will provide a proportionate verification method if one is needed. An authorized agent may submit a request where local law permits. We will respond within the time required by applicable law.
9. Account and data deletion
The current Apps do not create Soft-D Lab user accounts, so there is ordinarily no account profile to delete. You may still ask us to delete support correspondence or SDK data that can reasonably be linked to your installation. Follow the instructions on our Account and Data Deletion page.
Where a record can be located and no exception applies, we will delete it or instruct the relevant processor to do so, including by using provider deletion tools such as AppsFlyer’s privacy-request framework. Some crash records may be incapable of being linked back to you, and properly de-identified data cannot be associated with an individual. We may retain the minimum record needed to document the request or comply with law.
10. Children’s privacy
The Apps and Website are general-audience services and are not directed to children under 13 in the United States or under the applicable digital-consent age elsewhere. We do not knowingly collect personal information directly from children. Parents or guardians who believe a child provided information should contact privacy@softdlab.com.
If we learn that covered child data was processed without required authorization, we will stop the relevant processing, delete the data where it can be identified, and take reasonable steps required by law. An App specifically offered to children or through a Families program will receive separate disclosures and age-appropriate SDK configuration before release.
11. Changes and contact
We may update this Policy when an App, SDK, provider, or law changes. We will publish the new version here with an updated date and provide additional notice where a material change requires it. Earlier processing remains governed by the version in effect at the time, unless law permits otherwise.
This Policy describes the current disclosed configuration. App-store privacy labels and Google Play Data safety declarations must be reviewed whenever the App’s code, SDK configuration, events, or partner integrations change.