DD Bio Maker Privacy Policy

1. About this policy

This Privacy Policy explains how DD Bio Maker, an Android application provided by GB Tech Studio (GBTECHSTUDIO), handles information when you create, edit, export, back up or restore marriage biodatas. The Android package is com.gbtechstudio.ddbiomaker.

Core document creation, editing and export work on your device without an Internet connection. Advertising and Google services have separate data practices described below. The app does not require a user account or provide a developer-operated cloud synchronization service.

For privacy questions, contact support@gbtechstudio.com. This app-specific policy describes DD Bio Maker; other GB Tech Studio apps have their own policies.

2. Biodata, photographs and local storage

You choose the information entered in a biodata. This may include names, birth dates, age, addresses, phone numbers, email addresses, education, employment, income, family details, religion or community, custom information and photographs. Some of this information can be sensitive. Include another person's information only when you have appropriate permission.

Documents and imported photographs are stored in app-private storage on your device. We do not upload this biodata content or your photographs to a developer-operated server, and the app does not attach them to advertising or custom telemetry requests.

Photograph cropping is nondestructive: the original photograph can remain in private storage alongside crop settings. Hiding a field, section or photograph controls visual output; it does not delete the underlying editable information. Hidden information can remain in the editable document and its backup. Review what is visible before sharing.

3. Photo selection, files and permissions

You select photographs and backup files through Android's system selection interfaces. You also choose export and backup destinations through Android's file picker. The app uses access granted for these selections rather than requiring unrestricted access to all of your files.

The current app does not request camera, contacts, microphone or precise-location access. Internet and related permissions support Google advertising, consent, Analytics and Crashlytics services. Google SDKs can declare advertising-ID, ad-services, installation-referrer and background-operation permissions. Their presence does not give the app access to your biodata as advertising content.

You can review available permissions in Android Settings. Restricting network access may affect ads and consent services while core local document features remain available.

4. Exports, sharing and printing

The app generates PDF, PNG and JPG outputs locally. These ordinary exported files are not password-encrypted by DD Bio Maker. Anyone who can access a saved or shared copy may be able to read its contents.

Save As, Android's share sheet and print services allow you to choose destinations and recipients. A selected destination may be local storage, a cloud drive, a print provider or another app. Those providers process files under their own terms. Sending an export to a cloud drive is a sharing action you choose, not automatic cloud synchronization by DD Bio Maker.

Deleting a local draft does not delete copies already saved outside the app, shared with other people or sent to a printer. Manage those copies with the relevant destination, recipient or provider.

5. Encrypted editable backups and restore

Optional password-protected .ddbio backups contain editable documents, including hidden fields and original photographs. The backup format uses authenticated AES-GCM encryption with a password-derived key using PBKDF2-HMAC-SHA256.

Your backup password and encryption key are not sent to us. There is no password recovery service. Choose a strong password, keep it separately from your backup and protect every copy. This is password-based file encryption, not a claim that all app data or every app operation is end-to-end encrypted.

You choose where to save a backup. Restore validates a selected archive and imports documents as new local documents. Recovery warnings can require inspection before retrying. Remove unwanted backup copies through the storage provider where they were saved.

6. Google AdMob advertising

DD Bio Maker integrates Google AdMob, with Banner advertising enabled in the current release configuration. Interstitial and App Open integrations are also present, although automatic full-screen display is currently disabled. Advertising requests, including eligible preloading, depend on the app's consent and SDK-readiness checks. Native Ads are not used.

Google's Mobile Ads SDK can collect and share IP addresses, app/ad interactions, performance diagnostics and device or account identifiers for advertising, measurement and fraud prevention. An IP address can indicate approximate location. Data handling depends on consent, device settings and enabled Google features. Google describes encryption of its SDK data in transit using TLS.

We do not attach biodata text, document IDs, photographs, backup passwords, file names or private file paths to ad requests. Non-personalized or limited ads should not be understood as a guarantee that no data is processed.

Read Google's Privacy Policy and Google Mobile Ads data disclosures for further details.

7. Advertising consent and privacy choices

Google's User Messaging Platform (UMP) is used to check advertising consent requirements and present applicable privacy messages. The message shown and choices available depend on your region, prior choices and the privacy messages configured for the app.

When Google requires a privacy-options entry point, Ad privacy options is shown in the app's Settings so you can revisit your advertising choices. You can also use Android's advertising-ID controls and Google's advertising controls.

Firebase Analytics and Crashlytics are enabled separately in the release app; advertising consent does not control their collection. Declining or being unable to complete advertising consent does not make core biodata editing and local export depend on viewing an ad.

8. Analytics and crash diagnostics

The release app enables Google Analytics for Firebase and Firebase Crashlytics automatically. Analytics measures app usage, sessions, approximate location derived from IP, app-instance identifiers and technical device/app information. Our custom events record only biodata creation, template selection and successful local export generation, without document content or custom event parameters.

Crashlytics processes crash stack traces, relevant app/device state, installation/session identifiers and diagnostic information to help us understand failures and improve stability. Analytics events can appear as crash breadcrumbs. Our custom nonfatal report contains only a fixed export-failure category; we do not deliberately attach biodata, photos, passwords, filenames, private paths, user IDs or custom free-text logs. Automatic SDK crash reports can contain technical exception details.

Analytics advertising-ID collection, automatic screen reporting and Analytics ad-personalization signals are disabled in the app configuration. AdMob advertising has its own separate processing. Debug/QA builds keep Firebase collection disabled. Release collection has no in-app opt-out switch; advertising consent choices do not control this separate usage/crash collection. Core editing and export remain usable offline; SDKs can transmit queued information when connectivity returns.

Google processes this service data under the relevant service terms and settings, using encryption in transit. Retention and optional account-level integrations depend on the Google service settings. See Firebase privacy information and Analytics data disclosures. Contact us about privacy requests; we may need additional information to locate a pseudonymous installation and cannot remotely access local-only biodatas.

9. Sharing, service providers and support

Information leaves your device when you choose to export or share it with another provider or recipient, or when enabled Google advertising, consent, Analytics and Crashlytics services process their service data. DD Bio Maker does not provide a marketplace for biodatas or sell the biodata files you create.

If you email support, we receive the information you choose to include, such as your email address, message and attachments. We use it to respond and investigate the request. Do not send passwords, complete biodatas, private photographs or encrypted backups unless an appropriate support process has been agreed.

We may disclose information actually held by us when necessary to respond to a valid legal requirement, protect rights or address security issues. We cannot supply biodata files that remain only on your device. Google and your chosen providers handle their own data under their terms.

10. Retention, deletion and your control

Local documents remain until you delete them or app storage is removed. Photos no longer referenced by documents and internal temporary outputs may be removed during later cleanup; cleanup is best effort and files can remain after an interrupted operation.

You can edit or delete local biodatas, remove photographs and change output visibility. Normal Android uninstall or Clear storage removes app-private data and can be irreversible without a usable backup. Android application cloud backup and device-transfer participation are disabled in the app's configuration; operating-system and device-manufacturer behavior may vary.

Exported files, shared copies, saved backups and print-provider copies remain under your or the recipient/provider's control. Delete them separately. We cannot remotely erase copies on someone else's device or recover forgotten backup passwords. Retention of Google service data follows the relevant Google service settings and policies; this policy does not promise a fixed retention period for data held by Google.

11. Security

We use app-private storage, limited file-sharing permissions, authenticated backup encryption and validation of selected restore files. Ordinary local documents and exports are not described as encrypted by the backup password. No system or storage destination is completely secure.

Use a screen lock, an up-to-date device, trusted sharing destinations and strong backup passwords. Review outputs before sending them. If a file operation is interrupted, check the chosen destination for incomplete files before relying on the result.

12. Children, international processing and rights

DD Bio Maker is intended for adults preparing marriage biodatas and is not directed to children under 13. Do not use the app to solicit children's sensitive information. If you believe a child's information has been improperly disclosed, contact us so we can review the report and take appropriate action concerning information under our control.

Google and providers you select may process information outside your country. Depending on where you live, you may have rights to request access, correction, deletion, objection, restriction or withdrawal of consent. Contact us about requests relating to information we hold, or use the relevant provider's controls for its data. These requests cannot give us remote access to local-only documents.

13. Changes and contact

We may update this policy when app features, Google services or data practices change. The revised date appears at the top of this page. Where required, significant changes will be accompanied by additional notice or consent choices.

Developer: GB Tech Studio (GBTECHSTUDIO)
App: DD Bio Maker
Email: support@gbtechstudio.com
Website: gbtechstudio.com