Privacy information
Image credits, source links and rights complaints
We store voluntarily entered image credits and source links and the ‘Created with AI’ flag with the wish. Upon publication these details are visible in the image to others, including visitors without an account. They may include names. Only enter information needed for attribution and links suitable for public access; do not include private contact information, credentials or confidential documents. Source links are not automatically loaded as external images. Opening a source link sends connection information to the destination website under its own privacy notice.
Storage and display support the requested publication and attribution (GDPR Article 6(1)(b)). We process rights complaints, explanations and recorded review decisions to clarify and enforce legitimate rights and protect the platform (Article 6(1)(f); Article 6(1)(c) where specific legal obligations apply). Reports are not displayed on the public wish. Responsible admins and necessary technical providers have access within their tasks. Relevant moderation reasons may be shared with the submitter; confidential evidence should not be reproduced publicly.
Details and previous versions may remain in the review history. Deletion, backups and necessary retention follow the storage and deletion rules described below; public display ends when the wish is removed. Contact support@iwanitoo.com about rights complaints or these details. A private in-app document upload for licence evidence is not currently provided.
Optional push notifications · Updated 20 September 2026
You can enable push notifications per device in Settings. The app registers a private device token only after your choice and system permission. Support and wish-status alerts can be selected separately. Activity remains available without push permission.
Delivery uses Apple's Push Notification service on iOS and Google's Firebase Cloud Messaging on Android. The relevant provider receives the device token, generic notification text and internal wish and recipient identifiers. Push messages do not include names, wish text, images or moderation reasons. Providers also process technical connection and delivery information under their privacy notices (apple.com/legal/privacy and firebase.google.com/support/privacy); exclusively European processing is not promised. Google Analytics is disabled.
iwanitoo privately stores the token with your account, sign-in session, installation and preferences. Disabling push, signing out or deleting your account removes the server-side delivery registration. Your push choice and notification categories remain saved per account on this device, including after sign-out or switching between personal and company profiles. Signing back into the same account restores delivery only if system permission is still granted. Turning push off withdraws your choice; clearing local app storage removes it. Sign-out alone does not withdraw this saved choice. Optional push delivery relies on GDPR Article 6(1)(a); storing the explicitly requested setting implements that choice (section 25(2)(2) TDDDG). Registrations expire after 30 days without renewal by the app. Technical delivery records are removed after seven days. You can also revoke system permission in device settings.
Controller and contact
Atilla Sayan, sole proprietor trading as iwanitoo, Augustenstraße 46, 70178 Stuttgart, Germany; support@iwanitoo.com.
Data processed
Registration and sign-in use your email address, password or provider authentication, confirmation status and session. Other data includes profile name, username, optional bio and profile photo, language settings, wishes with text/images/video, support actions, private Saved entries, reports, notifications and recorded moderation actions.
Technical services also process connection information such as IP addresses, timestamps and error/security information. The app stores the sign-in session locally to keep you signed in. To vary Discover, the app stores up to 500 briefly displayed wish identifiers and timestamps per account on this device, together with the last feed entry. These records are not transmitted and are ignored after 30 days; older entries are removed on the next write. Clearing local app storage also removes them. No advertising or analytics SDKs are currently used.
Optional sign-in with Google or Apple
If you choose this sign-in method, Google or Apple confirms your identity to our Supabase authentication service. We process a provider-specific identifier, email address and verification status, plus the name supplied by the provider and, for Google, a profile picture where supplied. iwanitoo does not receive your Google or Apple password. We request only permissions needed for sign-in and a basic profile, not access to Gmail, contacts, calendar or Drive. Apple may supply a relay address instead of your personal email address.
Processing for your requested sign-in and account security relies on GDPR Article 6(1)(b). When you start sign-in, the provider receives technical connection data and information that you are signing in to iwanitoo. Its own processing follows Google's privacy information (policies.google.com/privacy) or Apple's (apple.com/legal/privacy/), and may involve processing outside the EEA. Email and password remain an alternative where configured for your account.
For an Apple-linked account, permanent account deletion requires a fresh Apple sign-in and revocation of the authorization at Apple. The required Apple token is briefly sent to Apple for verification and revocation; we do not keep it in a separate persistent token database. A record limited to the confirmed session and time window allows recovery from technical failures.
Purposes and legal bases
Accounts, sign-in, submission, display and support of wishes and handling your contractual requests serve the agreement for the free service (GDPR Article 6(1)(b)). Security, abuse prevention and accountable moderation serve our legitimate interest in a safe, respectful service (Article 6(1)(f)); we give particular consideration to the interests of minors. Statutory disclosure and retention duties rely on Article 6(1)(c). Optional public display of your Joined list relies on your withdrawable consent (Article 6(1)(a)).
Required fields are necessary for accounts and submissions. Photo, bio and public Joined visibility are optional. Optional wish emails are currently disabled and are separate from account emails.
Visibility and moderation
Profile name, username, bio and profile photo are designed to be public. Wishes become public only after approval. Saved stays private; Joined is public only when enabled.
Admins can review submitted wishes and media through the logged moderation workflow. This differs from separately authorized access to private support content. Infrastructure administrators technically have broader capabilities. AI moderation is currently disabled; no wish content is sent to an AI provider through it.
Providers and transfers
Hetzner Online GmbH hosts the separate test and production environments and media processing. Supabase Pte. Ltd. provides the database, authentication and media storage; both separate iwanitoo projects use the Frankfurt region. Resend (Plus Five Five, Inc.) sends account and confirmation emails.
Data may also be processed outside the EU/EEA, particularly by Supabase and email provider Resend (Plus Five Five, Inc., USA). A Frankfurt project region does not ensure exclusively European processing of all logs, support and subprocessor data. The published processing agreements of Supabase and Resend provide for EU Standard Contractual Clauses for applicable international transfers. Contact support@iwanitoo.com for information on the providers and safeguards used. We do not promise exclusively European processing by all services.
Device storage, consent and optional location
The app currently sets no own HTTP cookies and uses no advertising or analytics SDKs. Essential sign-in data is held in local app/browser storage under iwanitoo-staging-auth or iwanitoo-production-auth, depending on the environment, until sign-out or storage deletion; temporary PKCE/OAuth data supports the sign-in flow you start. Access protection and explicitly requested sign-in rely on section 25(2)(2) TDDDG. Optional purposes are not enabled in advance. You can sign out under Privacy & consent.
Only after your voluntary consent (GDPR Article 6(1)(a) and, where applicable, section 25(1) TDDDG), your click and system permission is location requested once to suggest a country for Top Wishes. The app resolves the country locally using a bundled map. It does not retain coordinates or send them to iwanitoo or a geocoding service. There is no background access. Operating-system location services may involve their own providers. Manual selection is always available. You must confirm the suggestion; it does not change the country of your wishes.
For signed-in accounts we privately store your optional location choice and confirmed country in account settings. Changes to location and public Joined consent are recorded with user ID, purpose, notice version and server time, including withdrawal. This record serves our legitimate interest in demonstrating accountability (GDPR Article 6(1)(f)), is accessible only to you and authorized infrastructure administration and is deleted with the account. Guests store only their current choice, version and timestamp locally under iwanitoo-device-privacy until changed or deleted. Turning location off under Privacy & consent prevents further lookups and removes a location-derived country. You can separately revoke system permission in device settings. Optional consents are separate from acceptance of the terms.
Analysis of published wishes
The internal Admin Studio can group published wishes by topic and aggregate their support. Each person is counted once per bundle; identifying supporter lists and private Saved entries are not returned. This analysis supports potential implementation projects based on our legitimate interest in developing the service. Verified companies can view associated published wishes, respond publicly and ask optional questions. The company workspace shows aggregate metrics, not supporters’ personal contact details or private Saved lists.
Retention and deletion
Account data and published wishes are processed for your participation or until the relevant content is deleted. Records of open complaints, security incidents and statutory duties are retained only as necessary to resolve the case, establish or defend specific claims, or meet a legal retention duty; they must then be deleted or anonymised. The operator regularly reviews continued necessity. Provider logs and backups additionally follow the relevant provider retention periods; their specific configuration is being verified separately. Immediate complete removal from all backups is not promised.
Under Settings → Account and data, after confirming your sign-in again using your password or sign-in provider, you can export active account data as JSON with media download links valid for one hour, or permanently delete your account including your wishes and media from active systems. Earlier requests are not executed automatically. Backups and provider logs are not immediately covered; contact support for additional access requests.
Your rights
Subject to the applicable legal conditions, you have rights of access, rectification, erasure, restriction, portability and objection. You can withdraw consent for the future. Contact support@iwanitoo.com. You may also complain to a supervisory authority, particularly where you live or work or where an alleged infringement occurred.
Company workspace and optional questions · updated 20 September 2026
For company access we process company name, website, business email, job title, affiliation and authority evidence and the review decision. A matching email domain alone grants no rights. Platform administration reviews independently; company roles permit only their assigned functions. Do not enter identity document copies or confidential documents in free text.
Survey answers are linked to your account to prevent repeated responses. Companies receive only aggregated answer counts. Participation, joining and subscribing to updates are separate voluntary actions. Answers are not purchase or participation commitments. Small samples are not representative. Personal data is not sold to companies.
Company and wish updates you voluntarily subscribe to appear in your activity. This does not permit marketing emails. You can unsubscribe on the respective page. The current company workspace collects no pilot interests and tracks no external purchase or usage actions.
Applications, answers, memberships and subscriptions are included in your account export. Account deletion removes private applications, personal answers, memberships and subscriptions; published company responses remain company contributions without individual author attribution. Deleting a Company Owner suspends verification pending resolution. Review and change logs evidence authorized company actions; access and erasure requests for these are handled via support@iwanitoo.com.
Processing provides the company workspace you requested, your chosen questions and protection of authorized access. Logos from public sources identify brands, not confirmed partnerships. Files are served by iwanitoo without automatic image requests to Wikipedia.
Shared wishes and their origins
Admins can connect related published wishes into a shared wish with an editorial title and summary. The general feed then shows the shared wish instead of the connected individual wishes. The underlying wishes remain accessible through the detail view while they remain published. Their original profile name, creation date and, where recorded, join count at the time of merging are shown. This records provenance within the platform, not legal authorship or exclusive rights to an idea.
The current total counts each supporting account once across the connected wishes. The connection, time and administrative action are also recorded. Presentation provides the requested publication and support functionality (GDPR Article 6(1)(b)); accountable editorial grouping and provenance serve our legitimate interest in an understandable platform protected against abuse (Article 6(1)(f)). Private Saved lists do not become public as a result.
When an original wish is deleted or no longer published, it is no longer returned in the public origins view. Deletion removes its connection. An editorial shared wish may remain because other contributions remain. If its summary still contains your personal information or protected content, you can request review and removal at support@iwanitoo.com; your statutory rights remain unaffected.
Recommendations, similarity search and technical caching
For You ranks published wishes using text similarity to your saved, supported and own published wishes. Recency, chosen country, support counts and variety also affect the order. Calculation takes place on your device using data available to your account and provides the requested personalized view (GDPR Article 6(1)(b)). It creates no separate server-side interest profile and does not share private Saved lists with companies. New offers chronological ordering instead.
When creating a wish, similar published wishes are suggested. The semantic similarity search in Admin Studio processes loaded published texts using a locally executed model; it does not send those texts to an external model API. Suggestions do not replace human review or automatically merge wishes or make moderation decisions.
Images, short-lived media links and public company data are technically cached to reduce reloading during navigation. Media metadata and links are reused in running app memory for up to 110 seconds; public company data for up to 60 seconds. The operating system and browser may additionally store image and model files according to their cache rules. The media metadata cache is cleared on account changes. Caching serves the requested display, not advertising or cross-device identification (GDPR Article 6(1)(b); where necessary section 25(2)(2) TDDDG). Local files and settings can be removed through app or device storage management.
Opening a notification saves its read status against your account to keep activity and unread indicators current (GDPR Article 6(1)(b)).
Company roles, logos and analytics
Depending on their role, company members can manage the company profile, logo, responses, questions and team assignments. We process account assignments, roles, invitation details and changes for this purpose. Company logos are public and may be technically cropped for circular display. Private application and review material is not part of the public company profile.
Company access and requested features rely on GDPR Article 6(1)(b). Authority checks and accountable access records rely on Article 6(1)(f), with the legitimate interest of preventing unauthorized company representation. Where third-party business contacts are provided or obtained from official sources for verification, only necessary business contact details and review results are processed. Those affected can contact support@iwanitoo.com for access or to object.
Custom questions collect selected answers and their account association. Processing voluntarily submitted answers provides the requested question feature (GDPR Article 6(1)(b)). Companies see aggregate results and metrics with their respective data bases, not named respondent lists through those results. Aggregation does not guarantee that no inference is possible in very small groups. Do not disclose health data or other particularly sensitive personal information through questions. Expressions of interest are not orders, payments or contractual participation commitments.
Business, surveys and purchases
For optional follow-up questions, we store your selection and time with your account to manage participation and prevent duplicate answers. Companies see aggregate selections, not which profile selected an option. Authorised team members receive an activity notification and internal history event for a new response. Research and Campaign store voluntary Joins and responses; free-text answers are shown without profile identifiers only after five participants. Avoid sensitive or identifying information: even text without a profile name may identify its author.
Participation you request, company administration and purchases rely on GDPR Article 6(1)(b). Internal review and security records serve legitimate interests in preventing abuse and resolving specific claims under Article 6(1)(f). Purchase records are also retained where legally required under Article 6(1)(c). Deleting your account removes your participation answers from active systems; company purchases and necessary transaction records are kept separately.
Apple processes payments under its own privacy terms. iwanitoo receives product and transaction identifiers, status, duration, timestamps and a random key linking the purchase to the selected company. These verify purchases, renewals, restores and refunds. iwanitoo receives no card or banking details from the Apple purchase. Necessary purchase assignments persist when company representation changes.
Advertising is labelled within iwanitoo. No data is sent to third-party advertising networks and no cross-app advertising profiles are created. Any available reach measurement is identified as impressions or clicks; unavailable measurements are not displayed as real counts. Opening an external destination sends technical connection data to its operator, whose privacy terms apply there. The Advertising Policy describes permitted content and placement.
Impressions are counted when at least half of a post is visible for one second. Post and action clicks are counted separately. Each event type is recorded once per signed-in account, UTC day and post edition; team views are excluded. Companies see totals, not viewer identities. Measurement takes place only within iwanitoo. Underlying records are removed on account deletion.
International privacy requests and rights procedures
You may exercise privacy rights through support@iwanitoo.com without an account. Where US state privacy laws apply, these may include access, correction, deletion, portability, applicable objection or opt-out rights, and review of a denied request. Authorized agents may contact us with suitable authorization. Identity and authority checks are proportionate; we do not routinely require identity documents or discriminate for exercising applicable privacy rights. Statutory response deadlines depend on the applicable law.
Under the current service model we do not sell personal information or share it for cross-context behavioral advertising. Rights complaints may contain names and email addresses; a formal US counter-notice requires further contact information and declarations. These are not publicly displayed but may be provided to the opposing party or competent authorities where necessary in an applicable legal procedure. The legal basis and any required international-transfer safeguards must be assessed before disclosure; a US procedural requirement does not replace the GDPR.
The service is intended for people aged 16 or older. Indications of younger children using it are reviewed; actual knowledge of data collected from a child under 13 requires handling under applicable children's privacy rules and ending processing where required. A minimum age stated in terms alone does not replace this review.
Evidence of acceptance of terms
We store your user ID, accepted version, language and server-recorded acceptance time. For acceptances from version 2026-09-26-test-12 we also store the notice version, displayed notice and confirmation text, source and confirmation method. The corresponding legal documents are archived by version. This serves our legitimate interest in evidencing the contract and defending against unfounded claims (GDPR Article 6(1)(f)). We do not store an additional IP address for this evidence. You can inspect your receipts under Legal; authorised product administrators can access them in user administration. Receipts are deleted with the account, subject to any necessary case-specific statutory retention or preservation of claims. Historical receipts are not retrospectively interpreted as acceptance of new texts.
Checking for contact details
To protect against unwanted contact, spam and publication of personal data, the app checks titles and descriptions locally; the same rule-based check also runs on the server when saving. This rule-based check does not use an external AI service. No separate directory of detected email addresses or phone numbers is created. Rejected text is not saved as a wish by that save operation. Previously saved versions and technical operational logs remain subject to the other retention rules described here.
This check is based on our legitimate interests in privacy and abuse prevention (GDPR Article 6(1)(f)). Text submitted for moderation is also subject to the moderation procedures and retention described in this notice. You may request human review and exercise your privacy rights through support@iwanitoo.com.
Personal blocking data
We store the identifiers of the blocking and blocked accounts and the time to apply your block across devices. GDPR Article 6(1)(b) is the legal basis for this requested function. The active block entry is deleted when you unblock or either account is deleted. Backups follow the general deletion periods in this notice.
The associated report contains your account identifier, the affected wish and its version, and a note that you blocked its author. It is available to authorised moderators and is not public. Processing for abuse prevention is based on GDPR Article 6(1)(f). Unblocking does not withdraw the report; the moderation retention and deletion rules in this notice apply. You can exercise privacy rights at support@iwanitoo.com.
Optional measurement of our iOS app advertising with Meta
If you allow Meta app advertising measurement under “Privacy & consent” and grant Apple tracking permission, we measure app starts and the first acknowledged installation signal to assess our Meta advertising. The app works without either permission. Measurement is off by default and requires signing in to the app. Accepting the terms or website cookies does not enable it.
We send the iOS advertising identifier (IDFA), a random app-installation identifier, event type, event ID and timestamp, bundle identifier, app version/build and iOS version. An authenticated iwanitoo service in Supabase's Frankfurt region relays the data to the Meta Conversions API. Sign-in credentials and internal account IDs protect access to our service and are not forwarded to Meta as measurement data. This integration does not forward the device IP address to Meta. The servers involved process technical network data needed for the connection. This integration does not send wish content, images, profile details, email addresses, registrations or purchases. Additional events and Meta SDK collection are not part of this measurement.
The recipient is Meta Platforms Ireland Limited, Block J, Serpentine Avenue, Dublin 4, Ireland. Meta may combine measurement data with other information and a Meta account and use it for advertising measurement, delivery and personalization, security and product improvement. Omitting a name does not make individual measurement data anonymous. The joint-controller agreement under GDPR Article 26 applies to the relevant collection and transmission; Meta is separately responsible for subsequent processing. See https://www.facebook.com/legal/controller_addendum and https://www.facebook.com/privacy/policy/. You can exercise your rights with iwanitoo at support@iwanitoo.com and with Meta.
Our optional measurement relies on your consent under GDPR Article 6(1)(a); corresponding device access relies on section 25(1) TDDDG. ATT permission is additionally required. You can withdraw consent under “Privacy & consent” at any time and manage system permission separately in iOS Settings. The integration then starts no further transmissions, aborts our in-flight requests and discards pending captures. Withdrawal cannot retrospectively recall data already accepted before withdrawal. Meta's Business Tools Terms provide a maximum two-year retention period for event data; we do not promise immediate deletion of all previously transmitted data after withdrawal or a test. https://www.facebook.com/legal/technology_terms
On your device we retain only your current consent choice with notice version and timestamp, a random installation identifier created after permission, and an acknowledgment marker for the installation already measured. Withdrawal removes the installation identifier; the marker prevents counting another installation. Local data also ends when app storage or the app is deleted. This integration does not persist IDFA or event payloads on the device or in our own event table. Offline events are not stored in a queue for later transmission.
To prevent abuse, our server also stores your internal account ID, the current hourly window and a request counter, but no IDFA or event content. Each account may make at most 60 measurement requests per hourly window. A dedicated hourly cleanup removes windows older than 24 hours; during normal operation, deletion occurs within 24–25 hours of the window starting. Account deletion also removes the counter. The cleanup job's own technical history is removed after seven days. Access protection and abuse prevention rely on our legitimate interest in operating a secure service (GDPR Article 6(1)(f)). Advertising measurement itself still requires both voluntary permissions.
Transfers to the USA and other countries outside the EEA may occur. For transfers to Meta Platforms, Inc. covered by its certification, Meta relies on the EU-US Data Privacy Framework and the adequacy decision under GDPR Article 45. The official participant list currently shows Meta as active; covered categories include Meta Business Tools such as the Conversions API and App Events. Further safeguards and rights are described in Meta's privacy information and applicable transfer arrangements. See https://www.facebook.com/privacy/policies/data_privacy_framework/ and https://www.dataprivacyframework.gov/participant/4452. The Frankfurt region does not guarantee exclusively European processing by every provider.