Privacy Policy
Vemro helps you document old drawers, keep reusable parts, generate local workshop layouts, and record your builds. This policy describes the data handled by the app and the connected Vemro service.
1. Data we handle and why
- Workshop content: project titles, wood types, dimensions, damage notes, reusable parts, layout selections, build logs, selected images, and audio notes are saved locally to provide project planning and record keeping. The current planning service does not upload this content.
- Profile and interaction data: your display name, selected avatar, follow choices, community posts, message text, conversation lists, reports, and blocked-user choices are stored locally in the current implementation. Current publishing and messaging actions do not transmit these records to other users or a community server; they must not be treated as confirmed remote delivery. Built-in community examples are illustrative content.
- Installation identifier: the app generates a random UUID and stores it in local preferences and the device Keychain. It is sent with the app version for sign-in, session initialization, sign-out, account-deletion requests, configuration requests, and purchase verification. It is not an advertising identifier or a hardware fingerprint. Keychain storage may preserve it after the app is uninstalled.
- Purchases: Apple processes payments. Vemro handles the product and transaction identifiers, transaction verification representation, an order reference, coin balance, and coin activity to verify purchases and prevent duplicate delivery. Verification information is sent to the Vemro service. Unresolved verification records may be retained locally for reconciliation. The app does not receive your full payment-card details.
- Network requests: the Vemro service at vemro.cyclevemro.top receives requests for account operations, legal-document and image configuration, and purchase verification. Remote images and online legal pages may be delivered by hosting or content-delivery providers, including Cloudflare when used for these sites. Such requests expose the requested URL, IP address, request time, and standard HTTP client information to the serving infrastructure. These are used to deliver and secure the requested service, not for advertising in the app.
2. Permissions and your choices
- Camera: requested when you photograph a drawer’s condition or reusable parts before dismantling.
- Photos: the system photo picker gives the app the images you choose for your avatar or project’s before-and-after log, rather than unrestricted access to your library.
- Microphone: requested when you record a spoken build-stage update. Recordings are saved to your project on the device.
You may decline camera or microphone access and continue using measurements, parts, and other features that do not require that resource. Review or revoke permission in iOS Settings; the app’s Privacy and permissions screen provides a Permissions button. Revoking permission does not automatically delete media you previously saved. The current app does not request location, address-book, health, or tracking access.
3. Sharing, providers, and tracking
Vemro does not sell your personal data, show targeted advertisements, or track you across other companies’ apps or websites. It does not send your project content to third-party AI services. Kingfisher is used to retrieve and cache configured remote images; it is not an advertising or analytics service.
Apple handles App Store payment processing under its own privacy terms. Hosting and delivery providers process necessary network data to operate the connected service. Any provider acting on Vemro’s behalf must be restricted to the stated purposes and provide protection at least equivalent to this policy and applicable Apple requirements. Information may also be disclosed where legally required or necessary to address fraud or security incidents, subject to applicable law.
The bundled legal pages use no analytics, remote fonts, advertising, or JavaScript. The app uses an ephemeral WebView data store for online legal pages rather than retaining a persistent browser history or cookie store.
4. Retention and deletion
Local workshop and interaction data remains on the device until removed through supported app actions, account deletion, or removal of app data. Signing out does not delete your local projects. Device backups managed by Apple or you may contain app data and are governed by the backup settings and provider’s policies.
To request account deletion, go to My Studio → Delete account and local data and confirm. The app first sends an account-deletion request. When the service accepts that request, the app removes its current local projects, measurements, media, profile, interaction records, and local coin balance. If the request fails, local data is not removed, so you can retry. Acceptance of a request is not independently verified proof that all server records have already been erased.
The current deletion action does not clear the Keychain installation identifier, separately stored remote configuration, image caches, or all pending purchase-verification records. Apple maintains its own purchase records. Records required for transaction reconciliation, legal obligations, or fraud prevention may be retained only as necessary for those purposes. Ask the developer for the applicable server retention period, deletion completion status, or help with residual data; do not assume uninstalling removes Keychain records or server records.
5. Security and processing location
Service requests use HTTPS. The installation identifier is stored in Keychain as well as local preferences. Other app data is stored in the app’s device container; no system can guarantee absolute security. Avoid including sensitive personal information in photos, recordings, captions, or messages.
Online requests may be processed in locations used by the service and its hosting providers, which may differ from your country. Applicable privacy-law safeguards must be maintained. This policy does not claim a specific hosting country or fixed server retention schedule that has not been confirmed by the operator.
6. Your rights and contacting the developer
Depending on your location, you may have rights to access, correct, delete, restrict, or object to processing of your personal data, obtain a portable copy, withdraw consent, and complain to your local privacy authority. You can edit your profile and project details in the app, revoke optional device permissions in Settings, and request deletion as described above. Withdrawing optional permission does not affect the lawfulness of earlier permitted processing.
The service operator is the developer identified on Vemro’s App Store product page. For privacy requests, residual-data removal, purchase issues, or safety reports, use the developer’s contact information available through App Support on that product page. Include enough information to locate your request, but do not send passwords, full payment-card details, or private project media unless necessary. A verified direct contact address and operator details must be published by the operator before public distribution.
7. Children and policy changes
Vemro is not designed for children under 13 and is not a Kids Category app. Users must meet the App Store age rating and any applicable local minimum age; minors should use workshop tools only with appropriate adult supervision. If you believe a child has provided personal data without required authorization, contact the developer to request review and deletion.
Updates will be reflected in the date above. Material changes to data uses or sharing will require appropriate notice and, where required, consent before the new processing begins. The copy bundled with your installed app may be older than a newly published online version.