Wazlop · Last updated: September 22, 2026
Wazlop is the product name. The operator is responsible for the app and these documents. Operator legal name: [REQUIRED BEFORE PUBLICATION]. Postal contact address: [REQUIRED BEFORE PUBLICATION]. Support telephone: [REQUIRED BEFORE PUBLICATION]. Contact email: libeowazlop4845@gmail.com.
This Policy explains information processed when you use Wazlop, a flower-arrangement app with hosted inspiration, recipes, preparation lists, making records, profiles, comments, a prepared-content assistant, subscriptions and virtual-gift purchases. It distinguishes device-local information from information sent to hosted services. Reading this Policy is not consent to unrelated processing or a waiver of privacy rights.
Supabase Auth processes your email address or generated account alias, password, account identifier and authentication requests to register and authenticate your account. Wazlop stores authentication tokens and a cached profile as part of its session in this device’s Keychain. It does not maintain the separate protected profile file described in the previous template.
Profile editing lets you change your nickname, personal signature and avatar. Saving these changes sends them to the hosted profile service. A selected avatar is encoded for upload to Storage. The current implementation uses public avatar URLs, not private, expiring signed links. Public profile details and avatar URLs can accompany works or comments and may be visible to other people. Do not use sensitive images or private information in your public profile.
The system photo picker gives the app access to images you select. Selecting an avatar and saving it uploads that avatar; selecting a photo for a making record stores that record photo locally. These are separate uses. Wazlop does not need unrestricted access to your photo library for these selections. Original photos remain under your control in Photos.
The Apple option uses the user identifier returned by Apple to locate saved Supabase email-and-password credentials in this device’s Keychain. A first registration generates an alias under wazioporg.com and a random password. This alias is neither an Apple private-relay address nor a personal mailbox assigned to you. Verification requirements depend on the authentication service and access to the domain mailbox.
These saved credentials use device-only Keychain storage and are not synchronized through iCloud Keychain. The backend does not return a password based only on the Apple identifier. Losing the local credentials or changing devices can prevent access through this flow; it is not a cross-device account-recovery service. Signing out retains the generated credentials for later sign-in. Confirmed account deletion attempts to remove matching credentials. Loss of access does not remove your right to contact us about your personal data.
Recipes, applied assistant recipes, material quantities, shopping plans, purchase checkmarks, preparation and making progress, notes and record photos are stored on this app installation. Saved-work identifiers are shared with the Inspiration screen and stored on the device. These collections are not promised to be account-isolated or synchronized across devices.
Signing out or deleting an account does not automatically erase these device-local collections. Other people using the same installation may be able to view them. Where an individual delete control is available, you can use it to remove that item; otherwise removing the app’s local data removes the local collection. System backups may retain or restore copies according to your device settings.
Wazlop uses assistant messages only to match prepared floral content and operate the requested recipe workflow.
Matching runs locally against a prepared library downloaded from Supabase. The assistant does not call a live generative-AI provider. Messages are not sent as prompts to Supabase or an AI service by this feature. Replies can include recipes, techniques, care instructions and clarification suggestions; applying a recipe creates an editable local recipe.
Assistant conversations, drafts and applied recipes are stored locally on the device; the prepared content library is served from Supabase and cached locally.
Conversation histories and drafts are keyed by the current account identifier or a guest scope. This is local organization, not cloud synchronization or a separate security boundary for people who share an installation. Signing out or deleting an account does not currently clear these histories or drafts. They remain until the relevant local app data is removed. A sent draft is cleared from the composer, while its message remains in the history.
The assistant library is normally considered fresh for 24 hours, with older cached content available if a refresh fails. This is a refresh rule, not a guaranteed deletion deadline. Other catalog and image caches may persist until refreshed, evicted or the app’s local data is removed.
Hosted account and profile information is retained while needed to provide your account and requested features, subject to deletion requests and lawful retention. Hosted comments and reports may be retained to display the conversation, address safety issues or meet legal requirements; their treatment after account deletion must follow the actual server configuration and applicable law. Contact us to request deletion of associated comments or reports.
Local subscription transaction identifiers and product identifiers, and gift transaction identifiers, product identifiers and transaction dates, are retained on the installation to record purchases and avoid duplicate recording. Gift records are stored in Application Support; subscription records use local preferences. Account deletion does not automatically erase these records or Apple’s transaction records.
[REQUIRED BEFORE PUBLICATION: confirm production database and Storage regions, operational-log retention, backup retention, legal-retention exceptions, deletion processing for comments/reports and backups, and any provider-specific purge schedule. Do not claim an unverified deadline.]
Hosted works, covers, publisher information and comments are downloaded to display inspiration and detail pages. Submitting a comment sends its text, your account identifier, the work identifier and a comment identifier to the hosted service. Public comments can be read and copied by other users. Do not include confidential or third-party personal information without permission.
Reporting or using the current Block action sends your account identifier, the work identifier and the selected reason to the hosted reporting service. A successful report also hides that work for your account, with locally cached hidden-work identifiers. The current Block action hides the selected work; it is not a promise to block all content by its publisher or prevent all future contact. A report receipt does not guarantee a particular moderation outcome or processing time.
Displaying a work in My works does not itself upload your local recipes or record photos. The current client does not automatically publish those local collections as public works.
Subscriptions and virtual gifts use Apple’s in-app purchase system. Apple processes payment and Apple Account information under its own policies. Wazlop does not receive your full payment-card number. The app receives product information, localized prices and transaction states and identifiers to process purchases and maintain local records.
Gift purchases currently create a local purchase record. They do not transmit an allocation to a creator account or provide a creator payout service. Restoring subscription purchase history is not proof that every historical subscription remains active. Consumable gifts are not restored through the subscription restore button.
Deleting a Wazlop account or uninstalling the app does not cancel an Apple subscription. Manage or cancel subscriptions in your Apple Account subscription settings. Apple may retain transaction records separately from Wazlop.
Wazlop does not sell or share assistant message content with advertisers or third-party AI providers.
Supabase processes authentication, hosted profiles, avatars, content, comments and reports for the requested services. Apple provides authorization, system photo selection and in-app purchases. Requests to these services and to policy/media hosting can involve IP addresses, request times, resource paths, response details and security logs. Provider retention is not the same as local app retention.
Public profiles, avatars and comments are intentionally accessible as described above. We do not use the current assistant feature to train third-party AI models. We may disclose information where legally required, to protect people and service security, or in a lawful business transfer with required notices and safeguards. We remain responsible for our own legal obligations and processing by providers on our behalf.
Where applicable, we process information to provide requested account and service features or perform a contract, comply with legal duties, and protect the service through proportionate legitimate interests where recognized by law. Consent is used where required. Optional device permissions do not waive your rights; withdrawal of consent does not affect earlier lawful processing.
Hosted information may be processed outside your country. [REQUIRED BEFORE PUBLICATION: identify actual production processing locations and applicable international-transfer safeguards, and explain how users can obtain information about them.] We do not assert a data-residency guarantee without verification.
You can close this explanation, delete local app data by removing the app, and use the existing account controls to sign out or delete your account.
While signed in, Settings offers Sign out and Delete Account with confirmation. Sign-out clears the active session after the service request completes, but retains local Apple credentials and local collections. Delete Account requests server-side account deletion and then removes matching local credentials and the active session after confirmation. Network, server or local-storage failures may leave cleanup incomplete; retry or contact us. Uninstalling must not be relied upon to erase Keychain items, provider backups, public copies or Apple purchases.
Depending on applicable law, you may request access, correction, deletion, portability or restriction, object to certain processing, withdraw consent, and complain to a competent supervisory authority. Contact libeowazlop4845@gmail.com and identify the relevant account or records. We may request proportionate verification; do not send passwords or tokens. We will respond within applicable legal time limits and explain any lawful exception.
We use platform security and authenticated network requests where appropriate, but no system guarantees absolute security. Public avatar URLs and public comments are not confidential storage. Protect your device and credentials.
The service is not directed to children under 16. A parent or guardian should contact us if a child has provided personal information. We will take appropriate steps under applicable law. Where a higher age or parental consent requirement applies, that requirement controls. This age policy must be aligned with the app’s actual audience and store disclosures before release.
We may update this Policy and its date as the service changes. Material changes receive notice or consent where legally required; an update does not retroactively authorize incompatible processing. External sites have their own privacy practices, without removing our responsibilities for providers processing on our behalf.
Wazlop is the product name. The operator is responsible for the app and these documents. Operator legal name: [REQUIRED BEFORE PUBLICATION]. Postal contact address: [REQUIRED BEFORE PUBLICATION]. Support telephone: [REQUIRED BEFORE PUBLICATION]. Contact email: libeowazlop4845@gmail.com.