Privacy policy
Responsible provider
Ivashchenko Business Solutions Owner: Kateryna Ivashchenko St. Gallerstrasse 160 9320 Arbon, Switzerland Sole proprietorship Commercial register: Thurgau UID: CHE-188.961.979 support@svoia.ch
Spam protection
Messages, reports, profile and goal changes, and blocking use account-and-action counters with limited time windows. They contain no message content or IP addresses. Expired windows reset on the next action; counter rows remain until the Svoia account is deleted. Reaching a limit temporarily restricts that action and does not automatically ban the account.
Data and purposes
Svoia processes your sign-in identifier, profile, goals, messages, blocks, reports and timestamps to provide access, discovery, collaboration and security. Profile details are entered by you, including name, profession, location, skills, languages and portfolio link. Email is not stored in the product profile or shown to members; trusted sign-in information is used to verify owner access.
Visibility and messages
Visible profiles and published active goals are discoverable by authorised members who are not blocked. Drafts are available to their author. Hiding a profile also removes its goals from shared discovery. Messages are available to correspondents in the app. They are not end-to-end encrypted; the operator can technically access the database.
Providers and AI
Sites and Cloudflare run the app and database; ChatGPT provides sign-in. Explicitly starting the AI assistant sends the entered goal and output language to OpenAI; that generation call uses store:false. In addition, text in visible profiles, active goals and chat polls are checked through the OpenAI Moderation API before storage or publication. Only the submitted text is sent, not the full conversation or email address. Hidden profiles and drafts are not sent for this content check. The existing API key remains encrypted server-side. Provider retention, processing countries and transfer arrangements remain to be confirmed separately.
Retention and rights
You can edit or hide your profile and download or explicitly delete product data under “Your data”. Deletion also removes your conversations and saved Svoia key from the product database, but does not delete your ChatGPT account. Automatic time-based deletion is not configured. Infrastructure-log and backup retention, overseas processing countries and transfer safeguards remain to be confirmed. The contact for access, correction and other privacy requests is listed in the imprint. The main legal framework is the Swiss FADP; additional applicable requirements must be assessed before opening.
Review history and deletion
Report text, the reported record, decisions, explanations, timestamps, deadlines and appeals are stored for manual review. The review panel shows the owner only the reported record, not other conversations or unrelated drafts. Participants receive the explanation, not the reporter’s identity or original report text. Explanations must therefore not include reporter details. Account deletion removes the account’s own decision history. For submitted reports, the text and connection to the reporting account are removed; links to decisions about other participants may remain for their history without report text or reporter identity. Automatic time-based cleanup is not configured; final retention periods remain to be decided.
Access from age 13
Only the account ID, policy version and confirmation time are stored for the age rule. The date of birth entered is used for the age calculation and is not stored. The confirmation is included in the account’s own export and removed on account deletion. Introducing the rule does not delete existing records. Age eligibility is not inferred from possession of a ChatGPT account.
Manual backups
The owner can create an encrypted file of the entire network’s product data and store it outside the app. It includes profiles, goals, messages, blocks, reports, decisions, appeals, counters and age confirmations. The stored AI key and server settings are excluded. Decryption depends on the protected server key; losing it may prevent recovery. Automatic backups and final retention periods are not configured. Restoration is allowed only into an empty product database of this project after file inspection and explicit confirmation. Deleting an account in the app does not automatically remove files already downloaded. Later deletions and privacy changes must be reconciled before reopening access after recovery. Short-lived restore confirmations last ten minutes and are cleaned up at the next inspection or account deletion. Successful restores are recorded without file contents.
Automatic text checks
Profanity, harassment, hate and threats are prohibited. A local word filter and server-side content check can stop sending or publication. If the external check is unavailable, content requiring that check is not released; hidden profiles, drafts, export and deletion remain available. Rejected attempts can consume action limits. Svoia does not save rejected new text or results as messages or a review archive and does not automatically ban an account because of a filter result. Checks can make mistakes or miss violations. Edit the text or report a mistake to the owner. Existing content is not automatically scanned retroactively.
Message requests and individual message reports
The first message to a new contact is a request. Only the recipient can accept or decline it; further messages are blocked until acceptance. Declined requests cannot be resent. Existing conversations remain accessible. Correspondents can report a specific message, including after blocking. The owner sees only the selected message and the report reason, without the rest of the conversation. Reports do not create a separate message copy. Account deletion removes messages and related requests from the current database. Decision history and older external backups follow the rules above; external files are not erased automatically. Request statuses are included in personal exports and protected owner backups. Local rules block recognizable suspicious links and explicit requests for passwords, access codes or money transfers in new messages and published text. Checks do not visit links or verify identity, reputation or transaction safety. They may miss risks or make mistakes. Allowed text is not proof of trustworthiness. Check addresses and payment recipients yourself; never share passwords or codes. Report mistaken decisions to the owner. Your @username stays visible in accepted chats.
Profile and cover photos
You may add your own profile and cover photos. Files are first cropped and compressed in your browser without carrying over original metadata. Only after separate consent and saving is the prepared image sent to OpenAI Moderation for checking and then stored privately in Cloudflare R2 through Sites. Rejection or unavailable checks leave the saved photo unchanged. Access follows the profile’s visibility, age, blocking and restriction rules. The owner may inspect current photos of an explicitly reported profile. No facial identity recognition is performed. Photos can be replaced or removed separately from profile text and are included in personal exports and new encrypted backups. Removal deletes active references and requests file deletion; technical cleanup failures can leave files inaccessible through the app until maintenance. Older external backups are not erased automatically. Final infrastructure retention periods and cleanup procedures remain to be confirmed.
Notifications
Your message and request notification preferences are saved to your account, included in export and encrypted backups and removed with account data deletion. Account decisions remain visible. Push is available after explicit device permission; email is not connected yet.
Push
Opt-in push stores a technical device endpoint and activation time under your account (up to three devices). Message and conversation-request alerts use your browser push service (Apple, Google or Mozilla) with no message text. Disable this device in notification settings; signing out also attempts to unsubscribe it. Invalid endpoints are removed on failed delivery. Device records are included in your own export and account-data deletion, but excluded from backups; subscribe again after recovery.
Comments and post actions
Comments store text, author, parent post and timestamps and are checked through OpenAI before sending. Post access, profile visibility, blocks and moderation restrictions apply. You can delete your own comments and report others. Likes show a count; saved and hidden post markers remain private. Shared links do not grant access. Own account records are included in export and encrypted backups and removed on confirmed account deletion; deleting a post removes its related comments and markers.
Photo effects and music
Posts store the selected photo effect, brightness and optional Svoia melody identifier. The original photo remains unchanged; the presentation is applied when displayed. Short melodies are supplied as the app’s own files and start only after a click. These melodies do not load an external service. Explicit music search sends the query to Apple’s Swiss catalog, first through the server and, if unavailable, directly from the browser without Svoia sign-in cookies or a referrer. New selections are verified through the catalog or structured metadata on Apple’s public song page before saving. Queries are not stored in the product database. Selected catalog music is stored with song and album identifiers, title and artist. The official Apple Music player connects only after Load player is pressed. Apple may receive IP, browser and usage data and use cookies; full playback may require a subscription. Music is not copied or combined with photos into an audio file. Settings are included in your export and protected product backups and are deleted with the post.
Current vacancy search
Explicit vacancy search sends only entered conditions and the selected language to OpenAI. Web search may derive queries for search providers. Profile, messages and sign-in email are not sent automatically. Do not enter names, contact details or documents. The request uses store:false, without ruling out technical provider retention. Conditions and results are not stored in the product database; existing AI usage counters and timestamps remain. Results and AI assessments may be outdated or wrong; check the original advertisement before applying. The pilot is owner-only and does not send applications.
Videos in posts
Each post may include an MP4/MOV up to 30 seconds and 8 MB. Own videos are stored privately in R2 only when saved after consent. Common container metadata is removed without transcoding. Video and audio are not fully checked automatically or sent to OpenAI. Videos can be reported; the owner may inspect the exact reported post. Post access, visibility, age, blocks and restrictions apply. Replacement, removal and confirmed account deletion remove active references and request file deletion. Protected backups include video within the total size limit; older copies remain. Personal exports include metadata and an access-protected link to download the file separately. Saving a YouTube link sends its video ID to YouTube for a server-side availability check. ID, title and channel name are stored; this does not verify official channel status. Your browser connects to YouTube only after Watch video. YouTube may receive IP, browser and usage data, use cookies and show ads. Svoia does not remove or bypass these ads. Publish only video and audio you may use.
Featured, following and meetups
Featured stores up to three references to your own posts or goals, or HTTPS links and titles you enter. Existing access, visibility, blocking and moderation rules apply. New link titles and URLs are checked like published text. Following stores a private association with a selected profile; your follow list is not shown to profile visitors and does not grant messaging access. Meetups store the organiser, title, description, time, town, venue, language and status, visible within the authorised network when the organiser profile is visible. New and edited meetup text is checked. RSVPs store the participant reference, meetup and time. Other participants see an eligible attendance count, not the attendee list. There are no automatic invitation emails or meetup reminders. Refresh to see edits and cancellations. Your records are included in export and encrypted backups; confirmed account deletion removes your data and related active references. Previously created external backups must be considered separately.
Community rules
We store your age declaration, rule version and consent time. This is not proof of age.
Email sign-in
In addition to ChatGPT, enabled email sign-in can use a one-time code. Resend receives the requested email address and code for delivery. SVOIA stores the verified address separately from the public profile, its internal account mapping, and hashes of codes, browser proofs and session tokens. Other members cannot see the address. Existing profiles are connected only through explicit linking from a signed-in account, never merely by matching addresses. Abuse counters use protected derivatives of the address and IP rather than a clear-text IP. Codes last up to 15 minutes and linking intents 15 minutes; expired technical records are cleaned up at the next code request. Sessions last up to 7 days and expire after 24 hours of inactivity. Sign-out revokes the session; account deletion removes its authentication records. Encrypted backups include account links but no active codes, session tokens or owner privileges. An email code does not verify age.
Manage verified email
My data shows your verified sign-in email. Change email replaces the previous address only after explicit agreement and verification of the new code. Previous email links and their active sessions are revoked; your internal account ID, profile and permissions stay the same.
Profile phone number
You can optionally save a phone number. By default, only you can see it. If you share it, accepted contacts can see it on your visible profile. It is not used for contact search or sign-in. You can remove it or change its visibility at any time.
Location in chat
Sharing a location is optional and one-time. Your device location is requested only when you choose to use it. For place lookup, SVOIA sends search text or coordinates to Komoot’s Photon service. The preview loads an OpenStreetMap map, sharing the selected point and technical connection data. The sent message contains the place name, available address and map link. There is no continuous location tracking.
Dictation and voice messages
Dictation converts your voice into editable text after you start the microphone. In a browser this may use the browser provider’s speech recognition service. In the iPhone app recognition may run on the device or use Apple’s service, depending on availability. Local punctuation formatting makes no additional AI request. The draft is sent to the other person only with “Send”. A voice message is initially recorded on your device and is stored in SVOIA and made available to the other person only with “Send voice message”. Playback alone does not send the recording to OpenAI. Only “Create transcript” sends the selected recording to OpenAI for recognition and uses one AI request. The text appears below the recording and is not sent as an extra message. Recognition can contain errors. The spoken language and last input mode are stored as local preferences, without storing recordings in these preferences.
Chat photos, videos and captions
The preview and any caption remain on your device until you send. “Send” stores the file and caption in SVOIA for the two chat participants. With your permission OpenAI checks the photo; a caption is checked like other message text. The rest of the conversation is not sent for this check. Uploads may take a moment. After a failed upload the file and caption remain available for retry during the open session; reloading or closing may remove this local draft.
AI & privacy
Only selected text, voice messages or attachments are sent to OpenAI for translations, writing suggestions and explanations. Photos, drawings and document pages are sent for content checks before sharing. Your choice applies to this account across devices and can be changed here at any time.
Age check
SVOIA is available from age 13.
SVOIA checks the minimum age using the date you enter and stores the result and the time of the check. Your date of birth is not stored. The information is self-reported.
Posts
Posts contain text, an optional compressed photo, visibility and timestamps. Posts are currently visible only to their authors. Earlier network posts are retained and hidden from other members. Every new photo is checked through OpenAI after your explicit consent, even for private posts, and stored in private R2 storage. A separate server value stores your notification read-through date. Your posts and photos are included in your export, confirmed account-data deletion and encrypted backups. Previously downloaded backups may retain content deleted later. The owner can review the exact reported post.
Saved
Favourites store references to profiles or goals. Saved searches contain your search terms and filters. Both are account-bound, visible only to you and included in your export and encrypted product backup. Saving an item does not expand access rights. After you dismiss the introduction, this browser remembers that choice for your account; the guide remains available in the menu. Email notifications are not connected, and no recipient address is stored for them.
Directory
The directory contains separately labelled organisation and provider facts, a source and the date of manual review. A listing is not a member account and cannot receive internal messages. Website links lead to external services.
Administration also stores private notes about sources and reuse grounds, excluded from search results. Directory records and review notes are included in the encrypted operator backup; personal bookmarks are included in the account export. Manual approval is not quality certification.
Corrections and removal
Correction, removal and representation requests store the sign-in identifier, listing reference, message, status, times and reply. Only the requester and administration see a request; private review notes are administration-only. Own requests are exported and removed by confirmed account deletion. Independent organisation listings remain.
Explicit website verification fetches only a randomly named text file on the stored official website over HTTPS, without cookies or redirects. The file contains no name or email; proof can be checked for seven days after submission. Website control is not identity or quality certification and grants no editing rights. Representation also requires manual review.
Approved removal hides the listing. Replies appear in the app; email is not connected. Requests and private evidence are in the encrypted operator backup. Automatic retention is not yet configured. As access is closed, this pilot does not replace a publicly accessible rights channel; operator contact and procedures must be completed before opening.
Organisation suggestions
Organisation suggestions store the account identifier, name, official website, canton, city, note, status and times. Only the proposer and administration can see them. Submission does not publish a listing or grant representation rights. The name and note undergo the same safety check as other publishable text.
Own suggestions can be deleted, are included in the account export and are removed by confirmed account deletion. Encrypted operator backups contain these data too; external copies need to be considered when handling deletions. Automatic retention is not configured yet.