Privacy

Two groups of people use I Want To. Developers run a project and a feedback widget on their site. Visitors leave ideas, problems, questions and thanks through that widget.

For the developer console we decide how data is used. For feedback left on a developer’s site, the site owner decides to collect it and we host it for them. You can ask either of us about your data.

When you leave feedback

• Email address. Only to sign you in with a six-digit code and to email you when the team replies. It is never shown to other visitors.
• Name (optional). Shown next to your feedback and comments. Without it you appear as “Anonymous”.
• Your feedback. Title, message, type, section, comments, the ideas you agreed with, and attachments (images, up to 5 files of 5 MB).
• Sign-in with Google (optional). Your name and verified email from Google, if the project turns it on.

Sent with each item

The widget adds technical context so the team can understand and reproduce what you describe: page path and title, where you came from, screen size, device type, browser, language, widget version, time on the page and how far you scrolled. Query parameters are removed from the address except those the project allows. The site owner can add data of their own, for example your plan.

Only the project’s team sees this context. Other visitors never do.

When you run a project

Company or team name, work email, project settings (name, site address, allowed origins, moderation mode, colours), the team’s replies and moderation actions.

• No passwords. You sign in with a code that works once and expires in 10 minutes.
• No cookies on your site by default. The widget keeps your sign-in token in your browser’s local storage on that page. Only if the project owner turns on Campaigns does it also set one cookie, described under Campaigns.
• No ads, no trackers, no selling data. Feedback and context are used to run the service, nothing else.

Some projects use Campaigns: short surveys, announcements and requests to accept new terms. Campaigns are off by default. Only a project owner on the PRO plan can turn them on, and the console warns them about the cookie described below before they do.

For campaign answers the project owner decides how the data is used, and we process it on their behalf. For the developer console we decide.

What changes on a site that turned Campaigns on

• A visitor cookie. The widget sets a first-party cookie called iwanto_vid on the project’s own domain. It holds a random identifier, not your name, email or IP address, and lasts up to 12 months. It tells us whether you already saw or answered a campaign, so we do not show it again, and whether you are a new or returning visitor.
• Consent. The owner chooses whether the cookie is set only after their site tells us you agreed (the default) or right away. The owner is responsible for describing the cookie in their own cookie policy and banner.
• Local and session storage. The widget remembers in local storage which campaigns you closed or answered, for up to 12 months, and keeps the pages you saw during one visit in session storage until you close the tab.
• Your answers. If you answer, we store your answers, the page address, device type and language. If the owner turned it on, we also store your country and city. If you are signed in, your answers are linked to your account. We never store your IP address.
• Acceptances. If a project asks you to accept new terms, we record that you accepted, which version of the text and when, so the owner can show it.

The files we use

• iwanto_vid (cookie). Random visitor identifier. Up to 12 months.
• iwanto:c:… (local storage). Which campaigns you saw, closed or answered. Up to 12 months.
• iwanto_s (session storage). Pages seen during this visit. Until you close the tab.

Answers are kept for 24 months unless the owner sets another period, campaign statistics for 13 months, and acceptance records for 5 years. If the owner turns Campaigns off, the cookie is no longer set and the existing one is removed on your next visit. To delete answers linked to you, ask the project owner or write to us.

• Other visitors: title, message, your display name or “Anonymous”, agree counts, comments and the team’s official replies, once the item is approved.
• The project’s team: everything above plus your email, the sent context and the site owner’s own data.
• Our staff: only when needed for support, security or abuse handling.

Sign-in codes, a note when your idea is published or the team replies (you can switch this off at sign-in or in your account menu, or stop emails about one idea), and team invitations. Sign-in codes are not optional because you cannot sign in without them.

We use hosting, email delivery and file storage providers who process data on our instructions, and Google if you choose Google sign-in. To suggest similar ideas while you write, the title and details of ideas, and the title and details you are typing, are sent to an AI provider (OpenAI), which turns them into a numeric vector so we can match by meaning. It is used only to find similar items, not to train models. Data may be processed outside your country; we use contractual safeguards where the law requires. The current list is available on request.

Feedback stays while the project exists. When a developer deletes a project, its feedback, comments and attachments go with it. Sign-in codes expire after 10 minutes. You can ask us to delete your account data at any time.

You can ask to see, correct, export or delete your data, and to stop emails. Your own feedback is listed under “My feedback” in the widget’s account menu. Write to us and we will answer within 30 days.

Traffic is encrypted. The widget works only on origins the developer has registered. Uploaded files are checked by content, stripped of location metadata, stored privately and served through short-lived links.

If this page changes in a way that matters, we update the date above and tell developers by email.