Spark Privacy Policy

1. Who we are (data controller)

Spark is operated in Romania by Birloi Eduard Stefan and Patrinoiu Calin Petre under the NevetsInc brand. NevetsInc is not a registered company. These individual operators are responsible as data controllers for the processing described here: they determine why and how Spark uses personal information. In this policy, “we,” “us,” and “our” refer to those operators.

• Service: Spark.
• Operators: Birloi Eduard Stefan and Patrinoiu Calin Petre, using the NevetsInc brand.
• Privacy contact: NevetsInc support. Identify your request as “Spark privacy request.”
• Additional information: Contact and Support.
• Other products: NevetsInc products. Their own notices may apply.

2. Scope and information sources

This policy covers accounts, profiles, approval, discovery, friend requests, direct and group messages, uploads, statuses, calls, activities, optional connections, advertising, notifications, and moderation.

It also covers Spark+ billing and appearance, administrator-issued membership, profile prompts and voice introductions, availability invitations, introductions between friends, friendship spaces, games, shared themes, and sealed capsules. The sections below describe each feature's audience and limits; enabling one feature does not authorize unrelated processing.

Information comes from you, from your use of Spark, from people who interact with or report your account, and from providers you choose to connect. Someone may send a message mentioning you, a reporter may describe an interaction, and Spotify may return listening metadata after authorization.

External websites, operating systems, music providers, GIF services, and advertisers may also process information under their own policies. Following an external link or using an optional feature can create a separate relationship with that provider.

3. Account and authentication information

We process account identifiers, email addresses, authentication records, sign-in status, account timestamps, and security information needed to register, sign in, recover access, and protect accounts. Guest access creates an account/session identifier even without an email.

Supabase provides authentication. Passwords are handled by its authentication system; Spark does not display your plaintext password to members. If you enable an authenticator, security checks process information needed to verify a code and the session's authentication level.

Sign-up human checks process challenge identifiers, answers, and request information to reduce automated abuse. Never send a password, recovery link, authenticator secret, or sign-in code to support or another member.

4. Profile information and private fields

Profiles can include a display name, photo, biography, gender, interests, preferences, friend code, approval status, staff designation, and social connection information. Visibility depends on eligibility, blocking, and available privacy settings. Information in a profile field can be seen by that field's audience.

Email, birth date, and stored location are private profile fields. Their records are separated from ordinary profile rows and restricted to the owner and authorized moderators. Raw profile updates do not publish these fields through ordinary profile realtime events.

This does not protect information you write in a biography, include in a photo, send in a message, or reveal in a call. Derived information, such as an age or approximate distance where displayed, may still convey something about you.

Optional personality features include up to three profile prompt answers and a voice introduction of up to ten seconds. These are profile content, not private verification documents. The recording can reveal your voice and anything audible in the background; it is not used by this feature to perform biometric identity verification. Voice-introduction uploads can have public URLs.

Saved appearance includes themes, accent colors, fonts, avatar frames, profile effects, name styles, and banners. Where enabled, these can appear on profiles and other member-facing displays. Uploaded banners can have public URLs. A Spark+ badge or effect indicates membership or a grant, not identity verification, trustworthiness, or a safety assessment.

5. Application review and legacy documents

The current application flow submits your completed profile and gender selection for approval. Approval is a review decision, not a criminal background check, university-enrollment certification, or guarantee of safety or accurate age.

Earlier versions accepted verification information such as phone numbers, student-document images, or selfies. Legacy verification database records are restricted to authorized moderators, rather than ordinary members. Approval does not itself erase those records.

Contact support to ask about or request deletion of legacy documents. Do not upload identity documents to ordinary chat or profile storage. A moderator-only database record does not establish that every historical file URL has always had private storage protection.

6. Connections, discovery, and recommendations

We use interests, preferences, friend requests, swipes, matched connections, blocks, and permitted interaction history to provide discovery and order recommendations. For you, Nearby, Personality, and Explore modes can change profile order.

Adaptive discovery uses recent choices for bounded changes to ordering. History signals decay over time; compatibility scores remain estimates rather than identity checks or promises of a successful relationship. The interest model uses a limited set of accessible historical profiles, falling back to ordinary matching when history cannot be read.

Best Friends can use conversation and call interaction metadata to order eligible connections. Relationship rankings stay private; displayed friends and mutual counts come from actual connections. Contact support to question how recommendations use your information.

Availability and friend introductions

“Free now” availability shares a chosen title, activity/call type, expiry, and associated call reference with eligible matched friends. Availability lasts for the selected 15–120 minutes, unless closed earlier. Expiry stops the active listing; it does not promise deletion of its database record or automatically end a separate call.

An introduction records the sender, two selected recipients, an optional note, their response states, and timestamps. Recipients see the proposed introduction and relevant profile information. Both recipients must accept before Spark creates a private three-person group; this does not automatically make them matched friends. Declining or cancelling closes the proposal without promising immediate erasure of its record.

7. Location and approximate distance

Location features depend on information you choose to provide and, where requested, browser/device permission. Nearby discovery uses a coarse location grid for distance calculations, checking the requesting account, visibility, and blocks. It does not intentionally return stored precise coordinates through ordinary member profile responses.

Control distance sharing in Settings → Privacy & Presence and revoke browser location permission. A location attached to a message is shared with the conversation audience and may be more precise than discovery distance.

Approximate distances can still reveal a general area. Do not publish your home address, school timetable, or live whereabouts to people you do not trust.

8. Messages, attachments, and voice notes

We store message content, participant/group identifiers, timestamps, replies, edit/deletion state, receipts, and attachment references for delivery and conversation history. Voice notes and uploaded files are stored for playback or retrieval.

Messages are not end-to-end encrypted. Transport encryption and database access rules protect delivery and access; they differ from a system where only conversation participants hold decryption keys. Authorized operational/moderation access may be necessary for reports, support, or legal duties.

Your own messages can be edited or deleted within the available one-hour window. Deletion displays a placeholder and marks the message as deleted. It does not guarantee erasure of original database content, attachments, backups, notification previews, or recipient copies.

Friendship spaces

A friendship space can contain shared notes, jokes, checklist plans, photos, song links, game state, and theme proposals. Spark stores the connection and author identifiers, content or media references, completion/approval state, and timestamps. Access is checked against the current matched connection, profile eligibility, and blocks; these spaces are intended for the two eligible friends.

Shared items are visible to both friends. Authors can remove their entries; removal clears the shared item's content and media reference while retaining a minimal removal record for synchronization. Games also store board positions, moves, whose turn it is, and results. These features are not end-to-end encrypted. Losing access cannot retrieve copies someone already made.

9. Upload URLs and view-once photos

Some uploads use public storage URLs. Anyone who obtains a working URL may retrieve a file without being its intended recipient. A URL can be forwarded or retained outside Spark; knowing it is not the same as having private access-controlled storage.

View-once photos track opening and expiry, with per-member opening state in groups. They have a 24-hour expiry, and sender-side upload cleanup is best-effort.

Private friendship media and group covers

Friendship photos, capsule media, and uploaded group covers use a separate private storage area. Authorized retrieval produces a signed URL valid for 60 seconds, rather than a permanent public URL. Group-cover access is limited to eligible current group members. Access checks govern new retrievals; a URL already issued may still work until it expires, including if forwarded. Downloaded files and screenshots remain outside those controls.

Sealed capsules

Capsules store a title, creator/connection identifiers, media type, release date, expiry, and creation/removal state separately from their text, photo, or voice payload. The metadata is visible before release; the payload cannot be retrieved by members, including the creator, before the server checks that release is due. The creator may still possess their original text or file outside Spark.

Capsules can be scheduled up to two years ahead. Access to released content lasts until one year after the release date, subject to continued eligibility and earlier removal. A lock is a server access restriction, not end-to-end encryption or protection from authorized infrastructure access. Expiry restricts access; it does not itself guarantee physical deletion. Creator removal deletes the stored capsule payload and requests media cleanup; a minimal removal record, recipient copies, and backups may remain.

10. Groups, statuses, polls, and plans

Groups process membership, roles, descriptions, photos, invitation codes, messages, polls, responses, RSVP choices, and shared activities. Discoverable groups can appear in group discovery. Invitations can be forwarded; resetting a code does not automatically remove existing members.

Statuses have a 24-hour display lifetime. Friends-only statuses are available to matched friends under access rules. Public statuses can be seen by signed-in non-guest members, including non-friends. Replies remain friend-gated.

Expiry restricts display, not every remaining file or copy. Exporting a plan to a calendar creates a separate copy managed by that application.

Shared friendship themes record the proposer, selected wallpaper/bubble style, recipient approval, and timestamps; a proposal becomes mutual after the other friend accepts. In-call party activities exchange relevant actions, answers, drawings, scores, and synchronization state through call signals, including host-controlled synchronization. Information revealed during an activity is available to its participants.

11. Calls and screen sharing

Calls process participants, call type/status, timestamps, invitations, signaling, and shared activity state. Microphone, camera, and screen access depend on browser/device permissions.

Audio/video use WebRTC, with direct connections where possible and relays where configured or necessary. Connectivity services, including STUN/TURN providers, may receive network information such as IP addresses. A direct connection may expose network information to the other peer.

Spark does not provide a built-in call recording service. Other participants may capture a call themselves. Share only the screen/window you intend; notifications, tabs, and documents may be exposed.

The microphone test analyzes input locally, does not record or upload test audio, and stops after 15 seconds, cancellation, or leaving/hiding the page.

12. Presence, activity, and notifications

Depending on settings and feature behavior, other members may see online/last-active status, typing, read receipts, and optional call or game activity. Invisible presence and “Share My Activity” are separate controls.

Notifications process permission state and, where used, push subscriptions/device endpoints. Desktop notifications can display sender names, profile images, and message previews, including on a lock screen depending on device settings.

Change presence/activity in Settings and notification permissions in your browser or operating system. Disabling notifications does not delete messages. Settings and permissions may differ across devices.

13. Optional Spotify and external media

Authorizing Spotify in Settings → Connections lets Spark receive your Spotify account name, current playback metadata, and recently played tracks. Access/refresh tokens are encrypted and stored server-side, rather than included in member profile responses or browser storage.

Listening activity is visible to matched friends by default for new connections. Existing connections retain their saved preference. Change “Show listening activity on my profile” in Privacy & Presence or disconnect Spotify. Private sessions are not displayed; access also respects relevant blocks, moderation, and private-profile rules.

Previews stream from Spotify or, where an exact matching preview is available, Apple's iTunes catalog. Song title/artist may be sent to Apple's catalog for lookup. Results may be cached; Spark does not save preview audio for offline listening. Playing a preview sends normal browser requests to the media provider.

GIF search can send search terms and browser requests to GIPHY. External images may contact their hosting provider. Disconnecting Spotify removes connection credentials and cached music metadata; it cannot erase copies already held by another person or provider.

14. Browser storage, preferences, and advertising

Spark uses browser storage for sessions, drafts, appearance, sound/device preferences, dismissed prompts, and related settings. Some device/ringtone preferences also synchronize to profiles. Browser caches can contain previously displayed resources.

Clear site data after signing out on a shared device. Doing so can remove unsent drafts and remembered choices, but does not automatically delete server records.

Vercel Speed Insights receives website performance measurements, including page route/URL, load and interaction timings, browser/device/operating-system information, network characteristics, and country information. Spark mounts this measurement service when the app loads. A URL can contain a resource identifier; performance measurement is separate from message storage and ordinary hosting/security logs. See Vercel's Speed Insights privacy information.

The optional Ads page loads Google advertising services, which may process device, browser, IP/request information, and cookies or similar identifiers. Opening it can contact Google; the page is not a promise of tracking-free advertising. See Google advertising information.

A privacy notice does not substitute for consent where required. You can avoid the Ads page and manage browser/cookie controls; those controls do not undo network requests already made.

15. Why we process information

We use information for specific service, safety, and legal purposes. Where GDPR or equivalent rules apply, the lawful basis depends on the activity and circumstances.

Permission is feature-specific. A browser prompt, account agreement, and legal consent serve different purposes. Withdrawing consent stops consent-based future processing; it does not undo earlier lawful processing.

Some information is needed for a feature: an account identifier for delivery, conversation content to send a message, or billing references for a subscription. Without it, we may be unable to provide that feature. Optional profile prompts, voice introductions, external connections, uploads, and appearance choices are not required to use every other feature.

Messages, biographies, photos, and recordings can reveal health, religion, sexuality, or other sensitive information about you or someone else. Avoid including information that is unnecessary or that you have no right to share. Posting it does not give Spark unrestricted permission to use sensitive data, and does not remove any additional legal conditions that apply to its processing.

16. Who receives information

Information is shared as needed with:

• Other members: information available through the profile, conversation, group, status, or activity audience.
• Supabase: authentication, database, realtime delivery, and storage infrastructure.
• Vercel: website/API hosting, performance measurements, and related request, security, and delivery processing.
• Stripe: requested Spark+ checkout, recurring payments, invoices, and customer billing controls, as described below.
• Feature providers: Spotify, Apple catalog/media services, GIPHY, Google advertising/connectivity services, and configured call relays when used.
• Authorized personnel: people needing access for support, operations, safety review, or legal compliance.
• Authorities/professional advisers: where legally required or lawful and necessary for serious safety issues or legal claims.

Administrator-issued Spark+ grants store the recipient, granting/revoking administrator, reason, duration and change timestamps in private membership and moderation records. The public profile can show active expiry or lifetime membership, badge and appearance. A private acknowledgement records whether the current membership welcome screen has been seen.

Spark+ payments and Stripe

Spark sends Stripe an internal account reference and plan metadata, and links the account to customer, checkout, and subscription identifiers. Spark's private billing records include subscription status, billing-period/access dates, cancellation state, event identifiers and processing timestamps, and temporary checkout-attempt/session records used to prevent duplicate or excessive requests. Webhook information is processed to verify payment events and update access.

Payment information is entered on Stripe-hosted pages. Stripe may receive billing/contact details, payment-method details, transaction information, and device/network information for payment processing, fraud prevention, and legal requirements. Spark does not receive or store full card numbers or card security codes. Authorized billing operators may access relevant customer/transaction information through Stripe's tools.

Stripe processes some data on the business's instructions and some for its own purposes, including security, fraud prevention, and legal duties. Banks and payment networks also participate in processing. See Stripe's Privacy Policy for Stripe's processing, retention, contacts, and rights information. Spark remains responsible for its own billing records and decisions.

Cancelling a subscription stops or schedules the end of renewal according to the billing controls; it does not erase the account, payment history, or appearance preferences. Membership expiry hides paid benefits without automatically deleting saved styles or uploads. An administrator grant and its reason are private records, while an active badge, appearance, or displayed membership duration can be visible to other members.

Spark does not sell member profiles, private messages, or connection data to data brokers. Advertising providers can still collect data through their own requests. Third-party advertising may have implications under a jurisdiction's definition of “sale” or “sharing”; we do not make a blanket exemption claim.

If a business transfer affects information, applicable notice/privacy obligations continue. This policy does not authorize unrestricted sale of private conversations.

17. International processing

Providers can process data outside your country, including the United States. Locations depend on the configured project, hosting service, provider, and feature.

As checked on 10 October 2026, Spark's primary Supabase database project is configured in Frankfurt, Germany (eu-central-1). This identifies the primary project region, not a promise that all hosting, support, backups, media delivery, payment processing, or provider operations stay in Germany. See Supabase's region information.

Where EEA/UK restrictions apply, a lawful transfer mechanism is required, such as an adequacy decision or appropriate contractual safeguards. We do not claim every transfer is covered by the same mechanism.

Ask support about providers, processing regions, and applicable safeguards relevant to your data. A provider's public compliance statement alone does not confirm every aspect of Spark's configuration.

18. Retention and erasure limits

Retention depends on record purpose, account state, feature lifetimes, security needs, and legal duties. Records should not be retained merely because storage is available.

There is no universal promised purge date for every category or backup. Ask support for details relevant to your request. An erasure exception needs a valid purpose and applicable legal basis, not unlimited permission to retain everything.

19. Account deletion and data requests

Account deletion first closes the linked Stripe customer to stop recurring Spark+ billing. If payment processing or provider failure prevents this, the account remains intact and the app shows an error for retry or support. Payment providers may retain records under their own legal and operational obligations.

Use Settings → Security & Privacy → Export my account data for the available account export, or Settings → Delete Account to start deletion. Keep downloaded exports private. Confirmation and recent authentication are required for deletion; an authenticator check may be needed. If it fails, sign in again or verify your authenticator, retry within the indicated window, or contact support.

The Settings export includes available account/profile, conversation, and selected friendship records, including capsule metadata. It is not a complete response to every possible access request: capsule payloads, including released content, and private provider/billing records are not included in this export. Contact support for additional eligible personal information or provider questions. An access request is assessed under applicable law; it does not automatically change a capsule's release date or another member's access.

Deletion differs from signing out, clearing site data, leaving a group, or deleting a message. Recipient copies, exported material, some shared history, lawful safety/legal records, and backups may remain where applicable.

Request access, correction, erasure, restriction, portability, objection, or processing information through support. Include your account reference and request scope. We may ask for proportionate identity verification; we do not need your password.

20. Your privacy rights and response timing

Depending on law, you can ask to understand/access information, correct it, request erasure, restrict processing, receive eligible portable data, object to certain uses, and withdraw consent. Rights have legal conditions and exceptions.

Under GDPR, we must respond without undue delay and normally within one month of receiving a request. Up to two additional months are permitted for complex/numerous requests, with notice and reasons within the first month. This is a response deadline, not a promise to erase every backup or recipient copy in 30 days.

If we decline a request or apply an exception, we must explain the relevant reason and remedies as required by law. Requests are generally free; lawful fees/refusals for manifestly unfounded or excessive requests must meet the law's conditions.

You may complain to a local supervisory authority. In Romania, see ANSPDCP. Contacting us first is not a condition of exercising a legal complaint or court right.

21. Children, teens, and guardians

You must be at least 13 years old to use Spark. Under-16 users need the consent of a parent or legal guardian under Spark's eligibility rule. Additional local requirements may apply, including valid consent and a minor's ability to enter a contract.

A birthday, checkbox, approved profile, or badge does not prove parental consent was independently verified. Sexual content is prohibited for everyone. Report grooming, exploitation, or suspected underage accounts through support.

We do not knowingly permit accounts belonging to children under 13. Report suspected accounts or missing required consent using the account reference, without publishing sensitive material.

Guardians can request assistance with a child's information. Verification of the account and guardian's authority may be necessary, while respecting the child's rights and law. For immediate danger, contact local emergency services.

22. Security and reporting an incident

Spark uses HTTPS, authenticated access, database access rules, restricted private fields, and security controls intended to reduce unauthorized access. They cannot guarantee a system, device, or recipient will never be compromised.

Keep devices updated, protect credentials, review permissions, and sign out on shared devices. A profile badge does not make malicious files or another member's conduct safe.

For suspected data exposure or unauthorized access, contact support, labeling it “Spark security incident.” Describe the feature/time without posting private data publicly. Applicable breach-notification duties continue to apply.

23. Public pages and AI-readable information

Public pages, Markdown variants, a sitemap, llms.txt, OpenAPI documentation, and an MCP endpoint help search tools and assistants understand Spark.

These resources describe the product/operator; the public API does not provide member profiles, private messages, or social connections. Indexing public pages is separate from signed-in feature access.

Discovery ranking is described above. AI-readable documentation does not authorize collecting private member data or bypassing authentication.

24. Policy updates and contact

We update the date when this policy changes. Where law requires additional notice or fresh consent, those requirements apply. A revised notice does not make earlier unlawful processing lawful.

For questions about providers, retention, a child's account, or data rights, use NevetsInc support. See Contact, Help, and Terms.

General guidance is available from the European Commission. Nothing here waives a privacy right or remedy under applicable law.