privacy, in plain language
Privacy Policy
This policy explains what heyka processes when you use the service, who can see information you share, how long information remains, and the choices and rights available to you.
Who is responsible
The controller is Rafal Borzemski, with service address Wrocław, Poland. The controller decides why and how personal data is processed through heyka.
Questions and privacy requests can be sent to privacy@heyka.app. Safety and abuse notices can be sent to abuse@heyka.app. This policy applies to the heyka website, installable web app, public profile links, and public event pages.
Information I process
You provide most information directly. Other information is produced when you use a feature, such as sending a message, joining an event, requesting a meet verification, or enabling browser notifications.
Email sign-in requests use Cloudflare Turnstile to reduce automated abuse. The Turnstile challenge sends a token and ordinary network, browser, and device signals to Cloudflare under Cloudflare's privacy policy at cloudflare.com/privacypolicy. Google sign-in is handled by the authentication provider and is not protected by Turnstile. heyka does not receive or store your Google password or an email-account password.
- Account data: email address, authentication provider identifiers, sign-in metadata, and account timestamps.
- Profile data: display name, birthdate, derived age, gender, biography, photos, username, what you are open to (dating, making friends, doing things together), optional relationship goal, height, city, occupation, lifestyle choices, interests that you choose to provide, and your preferred interface language.
- Connection data: introductions, first messages, the invitation label you chose, request status, conversations, chat messages, read receipts, blocks, and reports.
- Event data: events you host, organizer display name, venue, city, map link, start and optional end time, event time zone, audience, activity tags, optional spoken language, guest capacity, RSVPs, applications and optional messages, application decisions and status history, host announcements, cancellations, and event reports.
- Verification and notification data: short-lived meet coordinates, attempt counters, verification pairs, push endpoints, encryption keys, user agent, and queued delivery status.
- Technical data: pseudonymized rate-limit identifiers, request and security logs, CSP violation summaries, error details, cache metadata, and consent choices stored on your device.
- Analytics data, only after you allow Analytics: randomly assigned browser and session identifiers, timestamps, fixed page templates and product-action names, the origin of an external referring site, and basic browser, device, and coarse geographic information. I do not send account IDs, profile details, messages, heyka codes, exact locations, query strings, or raw profile, event, or chat URLs to Analytics.
Profiles and who can see them
Anyone with an active code or username link can open its public page. You have a permanent code and may create one temporary code. Usernames are public, guessable aliases for the permanent code only. Pausing the permanent code disables that code and its username link; the temporary code keeps working. The temporary code has no automatic expiry: delete or regenerate it to disable its old link. To disable both personal-code entry points, pause the permanent code and delete the temporary code. Existing connections and their photo permissions remain. Cached pages or previews may remain until successful cache revalidation; new requests always check whether the code is active.
Visibility expands only in defined signed-in relationship states. Blocks remove profile, request, conversation, and message visibility in both directions.
- Anonymous visitors see only display name, derived age, verification status, and the main public photo.
- A signed-in person opening an active code or username link may see your biography, public photos, gender, what you are open to, and optional profile details you supplied. Your choices about what you are open to and your relationship goal are hidden from anonymous visitors and are not used to filter or match people. Relationship goal and height are shown only when Dating is selected.
- A pending request recipient can see the sender’s profile teaser, including what they are open to and any visible relationship goal, and all sender photos so they can decide whether to accept.
- Accepted connections can see the counterpart profile and every profile photo, including photos marked private.
- Birthdate itself is owner-only; other people receive only the calculated age.
Photos
Photos are stored in a private storage bucket. heyka creates WebP renditions from decoded pixels, which removes embedded EXIF metadata. You can keep up to six photos and choose their supported visibility.
Authenticated photo responses use a year-long immutable browser cache. Changing a photo from public to private rotates its storage path, but bytes already fetched by a viewer may remain in that viewer’s browser cache for up to a year. Public photos are also kept in the hosting provider’s shared cache, which is set to refresh them about every 4 hours, so a photo that stops being public (for example because it is replaced, its code is paused or the account is deleted) can still be served for about that long, occasionally a little longer while the cache refreshes, to anyone who already has its address.
- The main photo must be public so an active public profile has a stable image.
- Photo access is checked against ownership, public status, pending requests, accepted connections, and blocks.
- Removing a photo deletes its current storage objects through the application’s cleanup process.
- Do not upload a photo unless you have the right to use it and are comfortable with the visibility you select.
Introductions, chats, blocks, and reports
A scan does not create a connection by itself. The scanner chooses whether to send an introduction and first message, and the recipient chooses whether to accept or decline.
Participants can see their conversation messages and read status. Individual messages cannot currently be deleted separately. Blocking stops access and communication; reporting sends the selected person or event and a reason to the operator.
- First messages are visible to the recipient before acceptance.
- Conversation participants receive realtime message and read-status updates through the app's realtime infrastructure.
- Typing and meet-status signals are transient realtime events rather than chat-history records.
- Reports are not public and are used to investigate safety, abuse, and Terms violations.
Public events and location
Active events appear on the open /events listing, which can be indexed by search engines. The listing includes the event details needed to discover it, the host’s display name, and the eligible main photos of the host and up to three participants. Individual event links are shareable even when marked not to be indexed.
When you choose “near me”, the browser asks for location permission. If you allow Preferences, heyka remembers that choice; on a later visit it reads a fresh location automatically only when the browser reports that the permission is still granted, and otherwise waits for you to tap the button again. Earlier coordinates are never reused. heyka sends coordinates in a private POST request to calculate approximate straight-line distances within 30, 50 or 100 km. Visitor coordinates remain in memory for this view and are not saved in the database, URLs, shared caches, browser storage, analytics or error reports. City search remains available without location permission. Without a remembered choice, the listing may start from a city estimated from your IP address by the hosting provider. Event times use the time zone saved with each event. An estimated or entered city is matched to eligible event cities before lookup; only those public city names are used in shared city-result caches.
Only a main photo available through any active, unrevoked personal code is eligible. Pausing the permanent code alone does not remove that photo while the temporary code is active. Leaving an event removes you from its participant selection. Changing your main photo updates future renders. The main photo cannot be set to private. Previously downloaded, cached or shared images may remain with their recipients or messaging services.
When you ask to join an event that requires host approval, the host can see your full profile and public photos, but not your private photos, along with your optional message. This access lasts while the request is pending before the event starts, or while you are an approved guest before the event ends. Event-based access ends on decline, withdrawal, leaving, cancellation, blocking or event completion. A separate personal connection keeps its own access. While you are going to an event or hosting it, anyone signed in to heyka can see that, along with your display name, profile and public photos, but not your private photos. They can do so without joining the event. On Singles, Men, Women and Non-binary events, where attending can reveal your relationship status, gender or orientation, only the host and the other guests can. This ends when the event ends or is cancelled, when you leave, or if you block one another; people you have blocked, and people who have blocked you, don't see you this way. After an event ends or is cancelled, full profiles are no longer available through it, but the host and guests can still see your display name, main photo and verified status in its guest list, unless you leave or either of you blocks the other. The list shows the host and up to 12 guests, drawn at random and redrawn every hour. If you’re going, you always see yourself as one of the 12. The host of an event that requires approval sees the 12 newest guests instead. People viewing the list see your public photos only while at least one of your personal codes, permanent or temporary, is active; otherwise they see your profile details without those photos. A host reviewing your request can see your public photos even when none of your codes is active. Previously delivered photos cannot be recalled. Unless either side blocks the other, request status and your message remain as event history until the event or a related account is deleted, and either side can report the other based on that request. Blocking deletes the application and its message, so it no longer provides reporting eligibility. Reports already submitted remain subject to the reporting retention rules. Host announcements are visible to the host and confirmed guests. Optional push notifications supplement the in-app request status and announcements; they do not contain your message, profile details or announcement text. After approval, the host and the approved guest can open a shared chat; the usual chat rules apply there, including blocking and reporting.
- Hosts publish a title, description, venue, city, precise meeting point (rounded to six decimal places), start and optional end time, time zone, audience, activity tags, optional spoken language and capacity. An Everyone or Singles audience only describes the event; a Men, Women or Non-binary audience limits who can join. Choose a public meeting place. Coordinates are stored with the event and may be delivered in public detail responses and authorized Realtime event broadcasts. Hosts can add an optional cover photo. It appears on the public events listing, the event page and link previews, is stored in a public storage folder under the host’s account, and can be loaded by anyone with its address without signing in. A replaced or removed cover is deleted, normally within minutes, and covers are deleted with the host’s account. Hosts can remove a cover at any time, including after the event.
- Hosting or joining an event can place your main profile photo on its public page, its link-preview image and its card on the public events listing, revealing your participation to anyone who receives the link or browses the listing, which search engines can index. Up to six participants are selected in stable join order, and the listing card shows the first three; the total RSVP count is shown separately. Additional gallery photos are not used.
- On create/edit pages, Geoapify receives place-search text and selected meeting-point coordinates through the heyka server to suggest a location and time zone. The map loads from Google Maps directly in your browser, so Google receives your IP address, ordinary browser information, and the viewed map area under Google's privacy policy at policies.google.com/privacy. If these services are unavailable, you can enter coordinates and select a time zone manually. Directions open Google Maps only when selected and contain the event destination, without a visitor origin. Nearby discovery does not contact the map provider.
- For a Men, Women or Non-binary event, heyka’s servers check the gender saved in your profile when you join, ask to join, or are approved; a refusal tells you only that the event’s audience doesn’t match. If your main photo appears on such an event’s public page or link preview, people who see it may infer the gender your profile had when you joined.
QR camera processing
The scanner uses the browser BarcodeDetector when available or a locally loaded QR decoder. Frames are processed in browser memory, are not uploaded to heyka, and are discarded as scanning continues.
- Camera access occurs only after browser permission and while you use the scanner.
- Only the decoded code or URL is used to navigate to a profile.
Meet verification
A conversation participant can voluntarily submit their current coordinates to confirm that both participants are physically close. The second confirmation is compared with the first, and a successful pair contributes to each profile’s verification count.
Coordinates are not exposed through the application API. The system deletes a pending coordinate within 9 minutes 30 seconds, with cleanup running every 30 seconds.
- Daily attempt counters are deleted after 7 days.
- Successful verification pairs and confirmation timestamps remain for the account lifetime.
- A profile badge appears after the configured number of distinct successful pair confirmations.
- The badge does not verify legal identity, age documents, criminal history, intentions, compatibility, or personal safety.
Browser notifications
If you enable notifications, heyka stores a push endpoint, encryption keys, user agent, timestamps, and the account that owns the subscription. You can disable push in heyka and in browser or operating-system settings.
Push payloads pass through the browser vendor’s push infrastructure and may contain a sender display name and up to 140 characters of a message preview. Consider whether previews are appropriate on your lock screen.
- A subscription is removed when you disable it through heyka or when the provider reports it permanently unavailable.
- Delivery records track pending, retry, sent, or permanent-failure status for operational reliability.
- Sent and permanent-failure delivery records, plus processed-message claims, are scheduled for deletion after 30 days.
- Push permission is independent of the Preferences cookie setting.
Security and error monitoring
Rate limiting protects public profiles and sensitive actions. Before an IP-derived identifier is sent to the rate-limiting provider, heyka transforms it with a keyed HMAC; the provider's analytics features are disabled.
The error-monitoring provider receives privacy-scrubbed operational errors and bounded security summaries. Browser monitoring is errors-only, loads only when an error occurs, sends no default personal identity, and stores no monitoring cookie or identifier on your device.
- Dynamic IDs, query strings, tokens, message bodies, form data, and user identity are removed or normalized from monitoring events.
- Content Security Policy violation reports are sent to heyka and reduced before operational reporting.
- Server and provider request logs may contain ordinary network metadata needed for security, reliability, and abuse investigation.
- No security measure is perfect; contact privacy@heyka.app if you believe an account or personal data is at risk.
Cookies and device storage
Necessary storage includes the dmc_consent choice record, the session-only locale language cookie, the authentication provider's session cookies, PKCE sign-in verifier cookies that are normally removed when consumed but have a maximum 400-day cookie age, a bot-protection security cookie on the API/authentication domain, requested session state, and the existing offline shell.
Preferences can remember a height unit, your events area (a chosen city, all events, or device location, and the search radius; never coordinates), and dismissed installation, push, or promotional prompts. Use the controls below to allow or refuse them.
Analytics is off until you allow it. The analytics service then sets first-party cookies that distinguish a browser and maintain session information for up to 180 days without extending that lifetime on each visit. The analytics script is not requested before consent. Saving your choices with Analytics off stops future collection and removes those analytics cookies where the app can access them. The current tab updates immediately; another already-open tab may not reflect a change until reload.
Service providers and international transfers
I use providers for backend infrastructure and hosting, authentication, email and push delivery, maps and place search, Cloudflare Turnstile abuse prevention, error monitoring, and—only with your consent—analytics.
Some providers may process data in the United States or other countries outside the European Economic Area. Where GDPR requires transfer safeguards, I use the applicable adequacy decision or contractual safeguards, including the European Commission’s Standard Contractual Clauses. You can request information about those safeguards or a copy at privacy@heyka.app.
Why I use information
Providing accounts, profiles, introductions, chats, events, requested notifications, and account controls is necessary to perform your agreement with me. Security, abuse prevention, reliable operation, and carefully minimized error monitoring support my legitimate interests and those of the community.
Consent applies where required, including optional Preferences storage, optional analytics measurement, and browser-controlled camera, location, and notification permissions. Legal obligations may require limited processing or disclosure.
- Contract: provide the service and features you request.
- Legitimate interests: secure, debug, improve reliability, prevent abuse, and moderate the service with minimized data.
- Consent: optional Preferences and Analytics storage and device permissions where applicable; it can be withdrawn prospectively.
- Legal obligation: respond to valid legal process and meet applicable compliance duties.
- heyka does not sell personal data, serve behavioral advertising, or use automated compatibility scoring or matching.
How long information remains
Profiles, relationships, conversations, and messages generally remain while the relevant account exists. Individual-message deletion is not currently available. In-app reports and related database moderation state are deleted when either related account is deleted. Correspondence received through the privacy and abuse mailboxes is stored separately and is normally retained for 12 months after a case closes, unless a legal hold or a valid erasure decision changes that period.
Deletion from live systems does not necessarily remove provider backup copies immediately. Residual copies may remain isolated until the provider’s routine backup-expiry cycle and are not restored except for disaster recovery.
- Pending meet coordinates: no more than 9 minutes 30 seconds, with cleanup every 30 seconds.
- Meet attempt counters: 7 days.
- Successful verification pairs: account lifetime.
- Terminal push-delivery records and processed-message claims: scheduled for deletion after 30 days.
- Consent choice: 180 days from the latest choice.
- Preference storage: until you revoke Preferences, clear site data, or the relevant browser session ends for session-scoped values.
- Released usernames: retained permanently as de-identified tombstones so they cannot be re-issued or used for impersonation.
- Photos already delivered to a viewer: potentially present in that viewer’s immutable browser cache for up to one year. Public photos: about 4 hours in the hosting provider’s shared cache after they stop being public, occasionally a little longer while the cache refreshes. Event covers: until the host replaces or removes them or deletes their account, then about 4 hours in the shared cache.
- Analytics cookies: up to 180 days from when they are first set. Event-level and user-level analytics data is configured for 14-month retention; standard aggregated reports may remain longer under the analytics provider's reporting rules.
- Account-deletion evidence: retained indefinitely under legitimate interests to demonstrate completion, investigate failures, and meet accountability duties. The row contains the account UUID; final phase and status; processing-attempt, consecutive-failure, and lease-revision counts; and requested, last-updated, and completed timestamps. Completion clears lease timing, retry eligibility, and error state. It contains no email, content, message, or Storage path, but the UUID remains an account identifier and is not anonymous.
Your choices and privacy rights
Send requests to privacy@heyka.app from the account email where possible. I may ask for proportionate verification and will respond without undue delay, normally within one month under GDPR, subject to lawful extensions.
Some requests can affect other people’s rights—for example, a conversation export contains counterpart information. I will scope disclosures and deletions carefully and explain any lawful limitation or refusal.
- Access personal data and receive information about its use.
- Correct inaccurate or incomplete information.
- Request deletion where applicable.
- Receive portable data where the portability right applies.
- Restrict processing in qualifying circumstances.
- Object to processing based on legitimate interests.
- Withdraw consent prospectively and change optional Preferences or Analytics cookies at any time.
- Complain to Poland’s President of the Personal Data Protection Office (UODO) or another competent supervisory authority, and appeal applicable United States privacy-request decisions by replying to my response.
Adults only
Birthdate is required and the application and database enforce an 18+ rule. If I learn that a minor created an account, I may suspend and delete it. Contact privacy@heyka.app if you believe a minor is using heyka.
Changes to this policy
The current policy is published at this URL. Material changes will be communicated through the service or account contact information when appropriate. Continued use after an effective change is subject to applicable law and the choices described here.