Jifron / Privacy notice · 14 October 2026
Learn what information Jifron uses, why we use it, and what choices you have.
This draft describes the current app. We still need to confirm hosting locations, provider agreements, and retention details before publishing the final notice.
Contact details updated on 6 November 2026.
Technical information updated on 7 November 2026.
Profile visibility, blocks and message settings are yours to change.
Only the photos you pick are uploaded. Calls start when you join.
Stored chats are not end-to-end encrypted. Downloaded copies cannot be recalled.
Jifron is a product of Wehrtens GbR, represented by Ben Jakob Wehrmann and Johann Anton Mertens, Saarstraße 1, 21029 Hamburg, Germany. Wehrtens GbR is the controller of the personal data described here. This notice covers Jifron, not every other Wehrtens product.
For questions about privacy or to exercise your rights, email privacy@jifron.com. You can also email the Jifron team at contact@jifron.com, email the operator at kontakt@wehrtens.de, or write to the postal address above.
We receive information you enter, information generated as you use Jifron, and content that other members share with you or about you. Optional features generate additional data when you use them.
We use account, content, learning, and communication data to provide the features you request, manage your account, and fulfill bookings or paid memberships where applicable. The legal basis is the performance of a contract or steps you request before entering into one (Article 6(1)(b) GDPR). You need an email address, a username, and a password to create an account and use features that require signing in. Most profile details, chats, uploads, and calls are optional.
We use proportionate security logs, abuse prevention, moderation, support correspondence and aggregate product or creator metrics for our legitimate interests in keeping Jifron safe, reliable and useful (Article 6(1)(f) GDPR). You may object to processing based on legitimate interests; we will assess your request.
Where a feature requires consent, we ask separately and rely on Article 6(1)(a) GDPR. You can withdraw your consent at any time. Withdrawal does not affect the lawfulness of processing that took place before you withdrew it. Giving your browser access to your camera or microphone is a technical permission. It does not grant consent to other processing. We process records required by applicable law under Article 6(1)(c) GDPR.
Feeds, search and discovery use information such as selected subjects, follows, visibility choices and available content to show relevant results. Jifron does not make solely automated decisions with legal or similarly significant effects about you.
Profile visibility, post visibility, message settings and blocks control what other members can see or do. Profile discovery and public profile pages are currently unavailable. Public posts remain visible to their permitted audience, including through search, with author attribution. Signed-in members can access permitted profile pages through direct links and existing conversations. Private groups and rooms are restricted to current authorised members. Other members may still copy, download or screenshot content they can access.
Emails, password hashes and private learning notes are not displayed as public profile information. Authorised personnel may access data when necessary for support, administration, security or moderation. Reports can include the content being reported.
If you choose to share an online or focus status, its configured audience can see it. Creator insights show aggregate counts, not a named list of everyone who viewed a profile or post.
Chats and uploaded files are stored on Jifron's servers and delivered to authorised conversation or room members. Chat messages are not end-to-end encrypted. Do not use Jifron chats to send secrets or highly sensitive information.
When read receipts are enabled, Jifron records which visible messages you read and when you read them. Other current participants can see the read status. You can turn off future read receipts in your chat settings. Turning them off does not erase previously recorded events.
Choosing a photo sends only the file you select, not your entire photo library. Chat image uploads are resized and re-encoded; embedded image metadata, including EXIF location data, is removed by that processing. PDFs and other supported media can still contain information or metadata you included; check them before sharing.
'Delete for me' and clearing a chat affect your view, not other participants' history. 'Delete for everyone' removes the message body and linked attachment from the active chat and queues stored-file deletion. A removed-message marker can remain for up to 30 days before cleanup. Hiding a conversation does not leave the group. Deleting a room closes access and calls immediately; its archived messages and files are scheduled for erasure after 30 days. None of these actions can recall copies already downloaded or captured.
Your camera and microphone start only after you choose to join and grant browser permission. Jifron uses WebRTC peer-to-peer connections for audio and video; this version does not implement call recording. Your browser encrypts the media transport, but this is separate from the privacy of stored chats.
To establish a call, Jifron processes participant identifiers, connection offers and answers, network candidates, media state and short-lived presence. Participants can receive network information needed for the connection, potentially including your IP address. The configured Google STUN service (stun.l.google.com) helps discover network addresses and can receive your IP address and connection requests. It is not used to store your chat messages or as a media recording service.
Only current authorised members can use a room's call. Leaving the call stops Jifron's local media tracks. You can also revoke camera and microphone access in your browser. Other participants can use external recording tools; Jifron cannot prevent this.
Jifron uses a necessary sign-in cookie, jifron_session, with a maximum lifetime of 30 days. It is HTTP-only, restricted to the same site and marked secure in production. You can end your session by logging out.
Local storage remembers language and appearance settings you choose. The Plus welcome is remembered on this device only if you select ‘Don't show this welcome again on this device’. Without that choice, dismissal and the short logo introduction are remembered only in the running page's memory, which is reset when the page reloads. Saved preferences remain until you change or clear them. These settings are not advertising or cross-site tracking identifiers.
This implementation does not install advertising pixels or third-party marketing analytics. Aggregate post statistics and security checks are handled by Jifron's own services. Essential storage enables the service you request; preference storage remembers choices you make. Clearing or blocking storage may reset preferences or stop sign-in from working.
Other members receive data according to the features and audiences you choose. Service providers receive the information necessary to operate their part of Jifron; authorities or advisers may receive information when required by law or necessary to establish, exercise or defend legal claims.
Hosting, email and payment providers may process data outside the European Economic Area, including in the United States. A European-facing website does not by itself mean that all processing takes place in Europe.
Transfers require an applicable GDPR transfer mechanism, such as an adequacy decision or the European Commission's standard contractual clauses, with any necessary supplementary measures. Netlify's published data processing agreement includes transfer provisions. The actual hosting regions, processor agreements and mechanisms used for Jifron must be confirmed for the production deployment before this review draft is finalised. Ask us for the applicable safeguards and how to obtain a copy.
Account, profile, active conversations, content and learning data generally remain while your account or the relevant feature is in use, until you delete them or request erasure, subject to applicable legal exceptions. Chat deletion and clearing have the different effects described above. Archived rooms and their messages and attachments are eligible for erasure 30 days after closure. Removed-message markers are eligible for erasure after 30 days. Active conversations are not deleted merely because they are old.
Sign-in sessions expire after at most 30 days. Password reset links expire after 30 minutes and can be used once. Expired sessions and expired or consumed reset tokens are removed during scheduled cleanup. Sign-in attempt records are retained for 7 days; write-rate-limit and password-reset-request records for 24 hours; raw in-app activity events for 30 days; call connection signals for 10 minutes; notifications for 90 days; and daily aggregate post statistics for 365 days. These are Jifron's operational retention choices, not a claim that the law requires each period.
Unused image or document uploads and unlinked or unfinished video uploads are eligible for removal after 24 hours. An hourly cleanup task processes bounded batches after this version is published. Large backlogs continue in later runs. Failed file deletions remain in a durable queue and are retried with increasing delays, capped at 24 hours between attempts. A resumable inventory scan also checks supported older file locations for missing database references, allowing a 24-hour grace period and rechecking references before deletion. Temporary upload leases protect writes in progress.
Account deletion revokes sessions and removes credentials, private learning data, owned content and file references in a database transaction. Linked file deletion is queued in that same transaction. Files whose references have been removed are no longer available through Jifron's download endpoints while physical cleanup is pending. A deactivated, de-identified account record and necessary booking or order records can remain. Completed file-deletion receipts immediately discard file keys; receipt counts and maintenance-run records are kept for 30 days. Provider outages can delay physical erasure and are visible in the protected admin status view.
These application cleanup rules do not establish deletion times for hosting backups, infrastructure logs or support mailboxes operated by providers, or override applicable record-keeping obligations. Their production-specific retention periods, restoration procedures and contractual arrangements must still be verified before this review draft is finalised.
You can edit your profile, change visibility and message settings, block members, switch off future read receipts, leave groups and delete your account in Jifron. You can also contact privacy@jifron.com or kontakt@wehrtens.de to request access, correction, erasure, restriction or a portable copy of your personal data, where the GDPR conditions apply.
You may object to processing based on legitimate interests and withdraw consent where consent is the basis. We may request proportionate information to verify your identity. Requests are normally answered within one month; permitted extensions will be explained within that period.
You may complain to a supervisory authority, including the authority where you live, work or consider a violation to have occurred. For our Hamburg location, this is the Hamburg Commissioner for Data Protection and Freedom of Information (HmbBfDI).
We update this notice when Jifron's processing changes. Material changes will be communicated through an appropriate channel before the new processing starts. The review date appears at the top. Please contact us if something is unclear.