Privacy Policy

Last updated: 1 November 2026

This policy explains what information Assembly 3D (“the app,” “we”) collects, how it’s used, and your choices. It covers the mobile app published on Google Play by XP Developer as Furniture Assembly 3D Guide, with package id com.xpdev.assembly3d.

1. Summary (plain English)

• Assembly 3D shows animated 3D assembly guides for furniture. It doesn’t need a user account. The guides, the product catalog, your list of builds and your settings are all on your phone, and the guides work offline. We have no servers of our own apart from a small relay for what you choose to send, and the app has no analytics or crash reporting of its own. The exceptions are the report you choose to send with “Doesn’t match my box” (section 2.6) and an app-development request you choose to send (section 2.8).
• The free app shows one banner ad from Google AdMob. Where the law requires it (the European Economic Area, the UK, Switzerland and other regulated regions), Google’s consent form (UMP) asks you first. You can change your choice at any time in Settings → Privacy choices.
• Remove ads is a one-time purchase made through Google Play. Google’s own terms and privacy policy apply to that purchase.
• Settings → “Need your own app?” lets you ask the developer to build an app for you. Only what you type there (your name if you give it, how to reach you, and what you would like built) is sent, and only when you tap Send (section 2.8).

2. Information we collect

Nothing, ourselves, apart from the report (section 2.6) and the app-development request (section 2.8) you choose to send. We don’t collect, receive, or store any other information from your use of the app on any server of ours. The free app does contain Google’s advertising software (AdMob), which collects some information itself; section 2.3 explains what. This section also describes what the app keeps on your device and what happens when you use its features.

2.1 Stored on your device

• My builds: the guides you have opened, so you can come back to them. For a catalog product it keeps the product’s article number; for a guide made by type and size it keeps the furniture type and the sizes you entered. Each build also keeps the step you reached.
• Your settings: language, units (centimetres or inches), whether read aloud is muted, and whether the one-time hint about a missing voice has been shown.
• Whether Remove ads is unlocked.

All of the above is stored in the app’s private storage on your device and is never sent to us — we don’t have servers for it.

If backup is turned on in your Android settings, Android may include this data in your own Google account backup, so it can come back when you reinstall Assembly 3D or move to a new phone. That backup is managed by Android and your Google account, and we can’t see it.

2.2 Guides, search and read aloud (on your phone)

The product catalog and the 3D drawings are inside the app. When you search, the app looks in that catalog on your phone: what you type is not sent anywhere. The page that draws the 3D guide is part of the app and loads nothing from the internet, so the guides work offline.

Read aloud uses the speech engine already installed on your phone. The app hands the text of the current step to that engine and records no audio. The engine is a separate app, usually from Google or the phone maker, with its own privacy policy, and whether it speaks on the phone alone or uses an online voice is up to that engine and your phone’s settings.

2.3 Advertising (Google AdMob)

The free app shows ads served by Google AdMob: one banner at the bottom of the home screen and of the guide screen, never over the 3D drawing or the step buttons. There are no full-screen, app-open or video ads. Remove ads takes the banner away.

To show, measure, and protect these ads, AdMob may receive your device’s advertising ID, an approximate location worked out from your IP address, your interactions with ads, and diagnostic information. Where consent is required, ads are personalised only if you agree to it; otherwise they are limited or non-personalised. You can reset or delete your advertising ID in your Android settings.

Google’s handling of this data is described in its Privacy Policy and in How Google uses information from sites or apps that use our services.

2.4 Consent (Google UMP)

Where the law requires consent for ads, Assembly 3D shows Google’s consent form, from Google’s User Messaging Platform (UMP), and asks first: no ad is requested before you have answered. The form stores your choice on your device. You can change it at any time in Settings → Privacy choices.

2.5 Purchases (Google Play Billing)

If you buy Remove ads, the purchase is processed by Google Play. We receive no payment details. The app only asks Google Play whether your account has bought Remove ads, when it starts and when you tap Restore purchase, and keeps a yes/no flag on your device so the ads stay off when you are offline. The purchase screen and the connection to Google Play come from Google’s Play Billing Library, so Google’s own terms and privacy policy apply to that processing: Google Play Terms of Service and Google Privacy Policy.

2.6 “Doesn’t match my box” reports

Every guide step has a “Doesn’t match my box” button, for when a drawing differs from the furniture in front of you. Nothing is sent until you tap Send. The app never sends a report in the background, never keeps one to send later, and does not retry: if sending fails, your note stays on screen.

• What is sent: which guide you were viewing (a catalog product’s identifier, or the furniture type for a guide you made by type and size), its size, the step number, the app version and build, the app language, and a note: the one you wrote, or the words “Doesn’t match my box” if you leave it empty. The sheet lists the exact lines before you tap Send.
• What is never sent: what you searched for, your other builds, your email address (the report has no email field), any identifier of you or your phone (no install id, no advertising id), or your location.
• Where it goes: over an encrypted connection to a small relay that the developer runs on Cloudflare Workers, which forwards it to the developer’s Telegram account. Cloudflare and Telegram handle it only to deliver it, under their own terms and privacy policies. The relay does not store or log the text of your report; it keeps only a count of messages per day and a short-lived rate-limit counter tied to your IP address, to stop abuse.
• How long it is kept: the report stays in the developer’s Telegram chat until it is deleted. It is used to check the guide for that furniture and size and to fix it. It is not used for ads, analytics or profiling, and it is not shared.
• Deleting it: email xpnazar@gmail.com and ask, and the developer will delete your report.

2.7 Links to other sites

The cover of a guide for a catalog product has a button that opens the maker’s own website in your browser, on a search for that product’s article number. Settings → Privacy policy opens this page. In both cases the app only passes a web address to your browser. The sites you reach there have their own privacy policies, and the app sends them nothing about you.

2.8 App-development requests you send

Settings → “Need your own app?” opens a form for asking the developer to build an app for you. Nothing is sent until you tap Send. The app never sends it in the background and never keeps a request to send later.

• What is sent: your name, only if you type one (it is optional); the contact you type so the developer can reply (an email address, a phone number for WhatsApp, or a Telegram username); the description of the app you would like built; and, so the developer knows where the request came from, the app’s name and version and the language the app is shown in.
• What is never sent: anything else from the app or your phone: not your builds or what you searched for, no identifier of you or your phone (no install id, no advertising id), and not your location.
• Where it goes: over an encrypted connection to a small relay that the developer runs on Cloudflare Workers, which forwards it to the developer’s Telegram account. Cloudflare and Telegram handle it only to deliver it, under their own terms and privacy policies. The relay does not store or log your request; it keeps only a count of requests per day and a short-lived rate-limit counter tied to your IP address, to stop abuse.
• What it is used for: only to read your request and reply to you through the contact you gave. It is not used for ads, analytics or profiling, it is not added to any mailing list, and it is not shared or sold.
• How long it is kept, and deleting it: the request stays in the developer’s Telegram chat until it is deleted. Ask for its deletion by email to xpnazar@gmail.com, or by replying through the contact you gave, and the developer will delete it within 30 days and confirm.

3. How we use the data

• Show your guides and let you resume where you stopped.
• Remember your settings and whether Remove ads is unlocked.
• Decide when the banner ad may be shown.
• Read and act on the reports you choose to send.
• Read and answer the app-development requests you choose to send.

Nothing is used for analytics or profiling by us.

4. Data we never receive

• Your name, email address, or phone number, unless you type them into the app-development request form (section 2.8).
• Your contacts or your photos.
• Your precise location.
• What you search for, and your builds — they stay on your phone. The only guide we ever see is the one in a report you send (section 2.6).
• Payment card or account details. Google Play handles the Remove ads payment (section 2.5).

What Google AdMob collects (section 2.3) goes to Google, not to us. AdMob only gives us totals, such as how many ads were shown.

5. Your choices

• Privacy choices — where consent applies, change your ad choice at any time in Settings → Privacy choices.
• Android’s ad settings — reset or delete your advertising ID, or opt out of ad personalisation, in your phone’s settings.
• Remove ads — a one-time purchase that removes the banner. On a new phone, use Settings → Restore purchase. You can also see your purchases in Google Play.
• Reports — nothing is sent unless you tap Send, and the note is optional (section 2.6).
• Read aloud — mute it at any time on the guide screen or in Settings.
• Your builds — remove any build from My builds inside the app.
• Uninstall — removes your builds and settings from your phone. If you use Android backup, your Google account may keep a backup copy until Android removes it or you delete it in your backup settings.
• App-development requests — nothing is sent unless you tap Send, and your name is optional (section 2.8).

6. Children

Assembly 3D is a tool for people who put furniture together and is not directed at children. Its target audience is 18 and over. We collect no personal information ourselves, from anyone, apart from what someone chooses to write in a report (section 2.6) or an app-development request (section 2.8), and we don’t knowingly collect any from children under 13. If a child has sent us a report or a request, email us and we will delete it.

7. Data retention and deletion

This section covers Furniture Assembly 3D Guide (Assembly 3D, package com.xpdev.assembly3d) by XP Developer on Google Play. The app has no accounts.

To have your data deleted:

1. Email xpnazar@gmail.com with the subject “Delete my Assembly 3D data”.
2. Say roughly when you sent the report, and which guide and size it was about, so we can find it.

What is deleted: every report you sent (section 2.6), with the guide, size, step and note in it. They are deleted from the developer’s Telegram chat within 30 days of your request, and we reply to confirm. We keep none of it, and apart from an app-development request (next paragraph) we hold no other data about you.

An app-development request (section 2.8) is deleted the same way: say roughly when you sent it and the contact you gave. It is deleted from the developer’s Telegram chat within 30 days of your request, and we reply to confirm.

Data the app stores stays on your device (and in your Android backup, if you use it) until you remove it in the app, clear the app’s storage or uninstall Assembly 3D. Google Play keeps your purchase record under its own policy. Information that Google collects for ads is kept by Google under its own policy; you can reset or delete your advertising ID in your phone’s settings.

8. Third parties and international transfers

The app’s own code sends no data to any server of ours, except the report (section 2.6) and the app-development request (section 2.8) you choose to send, which go through Cloudflare to Telegram. Google services run inside the app: AdMob serves the banner ad, the User Messaging Platform shows the consent form, and Google Play handles the Remove ads purchase. They run on Google’s global infrastructure, including servers in the United States, under Google’s own terms and privacy policy. The speech engine on your phone is a separate app with its own privacy policy (section 2.2).

9. Changes to this policy

We may update this page when we add features or change providers. The “Last updated” date at the top of the page reflects the most recent revision. Material changes will be announced in the app’s Play Store release notes.

10. Contact

Questions, requests to delete data, or anything else:
xpnazar@gmail.com