← Quatsch it!

Privacy Policy

Last updated: 10 November 2026

### Controller and contact
The controller for the processing described here is Liudmila Girlea, Attemsgasse 44/3/2, 1220 Vienna, Austria. Privacy requests: privacy@quatschit.com. General contact: support@quatschit.com.

### Anonymous, aggregate page-open counts without analytics cookies
For ordinary page-document requests to quatschit.com, we increment a server-side daily counter. The counter stores only the date and number of page opens, not IP addresses, user IDs, cookies, device information, page paths or referrers. Repeat opens count again; this is not a count of unique people. Known bots and preview or administrative pages are excluded where possible. This counter does not set or read identifiers on your device and operates regardless of your choice about optional analytics. The hosting infrastructure may still process connection data necessary for operation and security. The purpose is to measure aggregate use so we can improve the service; where personal data is involved in technical processing, we rely on legitimate interests under Art. 6(1)(f) GDPR, with the applicable rights of data subjects. Separate, detailed usage analytics still requires consent.

### Data, purposes and legal bases
We process contact and account details, sign-in information, profile information and submitted posts, comments, reactions and community associations as necessary for requested functions. Article 6(1)(b) GDPR applies where processing is necessary to perform the service contract. Necessary security, abuse-prevention and moderation processing may rely on Article 6(1)(f); the legitimate interests are protecting users, securing the service and enforcing lawful rules, balanced against your rights. Applicable legal retention, binding orders and other legal obligations rely on Article 6(1)(c).

Technical data may include IP addresses, timestamps, browser and device information, session identifiers and error logs. Voluntary bug reports include your description and, where supplied, a page path, category and contact address. Do not send passwords or unnecessary information about others. We handle requests and bug reports to provide requested support or pursue our legitimate interest in a secure, functioning service.

Optional usage analytics requires prior consent under Article 6(1)(a) and applicable device-access rules. Refusing it does not prevent use of essential functions. Withdraw consent in “Cookie choices”; withdrawal does not affect the lawfulness of earlier processing.

### Public content and anonymity
Public posts, comments, profile details and images may be seen by others, including visitors without accounts, and may be indexed by search engines. Check visibility before publishing. Third-party copies can remain outside our control. Anonymous contributions may remain internally associated with an account; anonymity does not guarantee untraceability.

Avoid unnecessary disclosure of specially protected data, including health, political or religious beliefs, or sex-life information, and do not disclose such data about others. Publication is not general consent to advertising use. Any future feature intentionally collecting or analysing such information requires a specifically established purpose and applicable Article 9 conditions.

### Recipients and providers
Other users receive access to published content according to visibility settings. Hosting, database, media, email and security providers may process data needed for their tasks. Authorised administrators access data as necessary for support, moderation, security and legal duties. Authorities, courts and professional advisers receive data only with an appropriate legal basis. We do not sell personal data.

External GIFs, embedded media and links can connect to other providers, whose own services have their own privacy information. Where consent is required before loading external content, a prior choice must be offered; a link in this policy does not replace consent.

### Retention and deletion
Account data is processed during the active account's life where needed for the service. Deletion handling takes account of the data concerned, pending reports, statutory retention and establishing, exercising or defending legal claims. Necessary continued retention is limited in purpose, scope and time. Security and moderation records cannot be kept indefinitely merely because they were collected. Contact privacy@quatschit.com for specific retention information concerning your data.

### Your rights
Subject to legal conditions, you have rights of access, rectification, erasure, restriction, portability and objection to processing based on legitimate interests. You may object to direct marketing at any time and withdraw consent for the future. Send requests to privacy@quatschit.com; proportionate identity verification may be necessary. We normally respond within one month and explain any legally permitted extension in time.

You may complain to the Austrian Data Protection Authority, Barichgasse 40–42, 1030 Vienna, Austria, https://www.dsb.gv.at, or another competent authority, including in the country of your habitual residence, work or alleged infringement.

### Required information and minors
We cannot provide an account without information necessary for registration and security. Optional profile information and contributions are not required simply to register. Accounts are available from age 14, subject to higher local requirements and necessary legal-representative consent. Under-18s may not use adult-only areas. Report suspected ineligible child accounts to safety@quatschit.com.

### Connect, messages and managed communities
Connect stores invitations, participants, message text, timestamps, reports and community membership records. Sending messages requires acceptance of the invitation. Messages are not end-to-end encrypted. Participants can read the conversation; authorised administrators may review reported messages and their context. Public profile images remain public. Archiving a conversation does not erase its history. Managed membership is administered manually; the present managed-community features do not automatically charge a payment method.

### Providers used by enabled features
The application supports Vercel for hosting and delivery; PostgreSQL for account and content storage; Supabase Storage for uploaded images and avatars; Cloudinary as an alternative or legacy image provider; Resend for service emails; GIPHY for requested GIF search and delivery; DeepL for requested translations; and OpenAI's moderation API for automated text and image safety screening when configured. A provider receives only the data needed by the enabled integration: for example email address and email content, translation text, or submitted text and an image URL for moderation. Media delivery also exposes the requesting device's connection data to the media provider. Provider availability depends on deployment configuration. This list does not mean every optional integration is active for every visitor.

Local safety rules and, when enabled, automated moderation signals may withhold content or route it for review. These checks can make mistakes. Request a human review through /appeal or support@quatschit.com. We do not promise that all content is manually checked before publication.

### International processing
Using providers and their subprocessors can involve processing outside the European Economic Area, including in the United States and, depending on the provider, other countries. Provider contracts describe processing locations and available transfer safeguards. Where Chapter V GDPR applies, a permitted transfer mechanism must cover the processing; a server located in the EU does not alone exclude overseas access. You may request information and a copy of the applicable safeguards from privacy@quatschit.com. Provider information: https://vercel.com/legal/dpa ; https://supabase.com/legal/dpa ; https://resend.com/legal/dpa ; https://openai.com/policies/data-processing-addendum/ .

### Account deletion and stored media
Account settings provide data export and password-confirmed account deletion. The current deletion process removes the account and related database records according to their relationships and queues cleanup of user-owned media. Storage cleanup can require retries; legacy Cloudinary images require manual handling. Backup copies, provider records and legally necessary records are subject to their applicable retention and deletion process. Contact privacy@quatschit.com if you need help or cannot use the account function.

### Optional browser notifications
If you enable browser notifications, we store the push endpoint and subscription keys associated with your account to deliver notifications. Delivery uses your browser's push provider, which may be operated by Google, Mozilla, Apple or Microsoft. Disable notifications through platform notification settings or browser permissions. This is separate from optional visit analytics.