Feedback Owed · Last updated: 10 November 2026
Privacy notice
How Feedback Owed handles work-email and colleague-invitation entry.
Encrypted legal traffic records
A separate encrypted legal traffic archive is being prepared. After offline-key backup, activation and publishing, dynamic requests reaching the application can record encrypted IP addresses, request times and methods. The archive excludes account IDs, email addresses, content IDs, URLs, request bodies and tokens. Administrators cannot read it through the site; the operator keeps the decryption key offline. Legally valid court or competent-authority requests may require disclosure. Timing can enable correlation; anonymity is not absolute.
The archive is configured for one calendar year, with legally required preservation exceptions. Expired records are removed on subsequent captured requests. Independent scheduled deletion, hosting/authentication traffic coverage, required fields and international-transfer safeguards still require verification. This preparation is not a guarantee of full compliance with Law No. 5651.
Who is responsible
Feedback Owed is operated by its founder as an individual project; it is not yet a registered company. The data controller is the Feedback Owed operator. You can reach the controller for any privacy question or request at privacy@feedbackowed.com. If the service is later incorporated, the registered legal entity will be added here.
Information we collect
For work-email accounts we process your work email, email domain, account type, authentication credentials and verification records. For invitation accounts we do not request a real email, name or employer. A random private access key is used to sign in through an internal, non-deliverable credential. The authentication service stores a credential derived from that key; it cannot send recovery mail. For work-email accounts the authentication service keeps the email for sign-in and recovery; verification does not delete it. Passwords are handled by the authentication provider, not shown publicly.
We process the content you submit (posts, employee replies and official company replies), company names, country and categories you choose, timestamps and case status. A work-email post stores the email domain; an invitation post stores no email or domain. Posts record which entry method was used, but neither stores an author account ID. Employee replies do not store a writer account ID, but record whether the writer used a work email or an invitation. Your private account holds a key used to find and update your posts. Likes are linked to the account that made them; official company replies are linked to the company representative's account.
The site also uses essential sign-in/session storage and a local language preference. User IP addresses are not linked to posts, employee comments or profiles in the application database; posts remain anonymous. Infrastructure, hosting and authentication providers may process technical traffic records (such as IP addresses and request times) strictly within the legal framework, for system security and to meet mandatory legal obligations such as Law No. 5651.
Why we use it
We use account information to verify work-email ownership or a single-use referral, provide sign-in (and email recovery only for work-email accounts), and prevent abuse; posts and replies to run the workplace-feedback service; case data to track responses and resolution; and technical data to keep the service secure. Depending on applicable law, the grounds may include performing the service you request, legitimate interests in security and moderation, and legal obligations. This notice is not a request for marketing consent. We do not currently send emails about posts or monthly check-ins; those are shown in the site.
Who can see it
Posts, employee replies, company replies, timelines and company records are visible to signed-in members (with plan-based limits for company accounts). Work-email verified and colleague-referred posts carry different labels; a referral does not prove employment at any company. Your full email is not displayed next to your posts. Company representatives can read feedback about their company and, on eligible plans, reply officially. Service providers operating hosting, authentication and transactional email may process data on our behalf; disclosure may also be required by law.
Anonymity is not absolute: your chosen wording, workplace, country, timing, or voluntarily shared details could identify you. Your employer may be able to see that a verification message was sent to your work inbox. Never include names or personal details of others in posts.
Retention and transfers
For work-email accounts, the work email remains in the account while it exists. Invitation accounts have no real email and cannot use email recovery; losing the access key can permanently prevent access. Single-use invitation records retain a hashed code, issuer account and redemption status to control abuse. Posts may remain visible after account closure because posts and employee replies are not directly linked to accounts; removal or correction may require your private post access and a manual review. Data is processed by our hosting, authentication and email providers, which may involve processing outside your country; these providers apply contractual safeguards. We do not claim that deleting an account automatically deletes all past content.
Your rights
Depending on where you live, GDPR and Türkiye's KVKK may give you rights to learn whether data is processed, access it, request correction or deletion, object or restrict processing, and complain to your data protection authority. GDPR may also provide portability and withdrawal of consent where consent is actually used. Some requests are limited by law or by the fact that a post is intentionally separated from your identity. A verified account or private post access may be needed to identify content you control.
To exercise these rights, email privacy@feedbackowed.com from your registered work address, or for an invitation account provide proof of control of the private key without sending the key itself. We aim to answer within 30 days.