Privacy Policy

1. Who is responsible

Samuel Kubinec is the controller of personal data processed for the Styvi service unless a feature clearly identifies another controller. Our public contact for privacy, support, child-safety, rights and legal requests is privacy@styvi.cc.

Styvi is currently a pre-release project operated by Samuel Kubinec as an individual. The service contact address is Bertotovce 168, Slovakia. No registered company, sole-trader details, company or tax identifier, or register entry has been supplied for Styvi. The operator's business and tax status and any legally required commercial disclosures must be completed before a commercial public launch.

Apple, Google, external retailers and other third-party services may act as separate controllers for information they collect directly under their own terms. This Policy does not replace their notices.

• Samuel Kubinec
• Status: individual pre-release developer; no company or sole-trader registration has been supplied for Styvi
• Country used for this notice: Slovakia
• Business or service address: Bertotovce 168
• Company or registration ID: none supplied
• Tax or VAT ID: none supplied; Styvi is not represented as VAT-registered
• Register and registration number: none supplied
• Email: privacy@styvi.cc
• Phone: +421951818608
• Consumer and e-commerce supervision: Slovak Trade Inspection, Central Inspectorate, Bajkalská 21/A, P. O. BOX 29, 827 99 Bratislava, Slovakia
• Data-protection supervision: Office for Personal Data Protection of the Slovak Republic, Galvaniho 7/B, 821 04 Bratislava, Slovakia

2. Information we process

3. Device permissions and on-device work

Depending on the feature you choose, Styvi may ask for camera, microphone, photo or media library, notifications, location, speech, biometric or device authentication, Siri or shortcuts, and related platform permissions. A permission is requested for the feature shown at that moment. You can refuse or change it in system settings, but that feature may stop working.

Some visual analysis, safety checks, subject segmentation, translation and other processing may happen on the device through Apple frameworks. Information that stays only on your device is not collected by Styvi. If a result or selected file is sent to our backend, that transmitted information is covered by this Policy.

The audited app does not currently upload your address-book contacts. Discovery settings referring to contacts do not by themselves grant Contacts access. We will update the product notice and this Policy before any contact upload is introduced.

4. Why we process data and our legal bases

We do not treat a device permission or acceptance of the Terms as blanket consent for unrelated processing. Google Gemini processing has its own choice where the feature requires it. Where we rely on consent, you may withdraw it prospectively without affecting earlier lawful processing. Where we rely on legitimate interests, you may object and we will assess your circumstances and our compelling grounds.

Optional AI Editor processing and optional writing-style memory each require a separate affirmative choice. We use consent for these optional purposes; providing the main account service, maintaining purchase records, or carrying out necessary safety and legal processing does not depend on accepting them. Withdrawing one choice does not enable or disable unrelated analytics, diagnostics or location choices.

5. Who can see what you share

• Public profiles and public posts can be seen by other users and, where public sharing is enabled, by people outside Styvi.
• Audience-limited posts and Snips are delivered according to the audience selected when you share them.
• Notes, Moments, music presence and social interactions can be visible to friends, Besties or selected recipients according to the available feature controls. A reply, repost or share can change who sees a copy; check its audience before publishing.
• Messages and live-location information are intended for conversation participants. Recipients can still screenshot, record, copy or redistribute what they receive.
• Drafts and private account information are not presented as public content, but authorized systems and staff may process them when needed to provide the feature, investigate a report, secure Styvi or comply with law.
• Removing content from public view does not necessarily erase copies already saved or lawfully retained by another person.
• For supported encrypted message formats, the sending device encrypts the protected content and the receiving devices open it using account keys. The server still processes routing and security metadata such as participants, times, delivery state and envelope or attachment sizes. Older messages, unsupported formats, independently fetched shared-resource previews and content a participant submits to support can be processed differently. Keys may use Apple's synchronizable Keychain according to device and Apple account settings. This is not a claim that all messages, all devices or backups have one independently audited encryption guarantee.

6. Service providers and other recipients

We disclose only the information reasonably needed for the relevant service. The exact data a provider receives depends on the feature you use.

7. International transfers

Some providers and their subprocessors process information outside Slovakia or the European Economic Area. Where required, transfers rely on an adequacy decision, the European Commission's Standard Contractual Clauses and supplementary measures, or another lawful mechanism. A provider's infrastructure, support and security processing may still be global even when primary storage is in the EEA.

You may contact us for information about the safeguards relevant to a transfer. We do not describe Styvi as EU-only because that would not accurately reflect all edge, platform, AI, search and support services.

8. AI processing

When you intentionally use an online AI feature, Styvi may send a prompt, selected image, music description or lyrics, or another requested input, limited entitlement context and safety metadata through our backend to Google Gemini. The response and request record may be stored to deliver and display the result, account for credits or allowances, investigate abuse or show the applicable history. Revoking optional Gemini permission blocks new requests but does not automatically erase results already created.

Image and text features use Gemini generation requests. Music Studio uses Google's Interactions API to create audio clips or songs and cover art. Video safety review can send an uploaded video to Google Cloud Video Intelligence and temporary Cloud Storage; selected flagged context may additionally use Gemini Files for review. The backend attempts to remove temporary review copies and provider files after processing, but a failed cleanup may require follow-up. Styvi does not claim that every AI request stays on the device or that Google keeps no records.

With separate AI Editor permission, Styvi sends the unsent draft you explicitly select, operation, style, target language and optional writing instructions through the backend to Google Gemini. Conversation history, recipients and contacts are not automatically included. The suggestion is returned for your review and is not sent as a message automatically. This chosen online draft processing is separate from transport or encryption of a message you later send.

Optional writing-style memory stores aggregate preferences such as typical length, capitalization, emoji use and punctuation, rather than an extra archive of message bodies. The current server-side learning path can update these statistics only from qualifying readable sends after opt-in; encrypted message bodies are not decrypted by that path, and older history is not scanned. Enabled preferences can accompany a selected AI Editor draft. Turning memory off deletes its active profile and clears associated retry results. This feature is not permission to train a general model on your conversations.

The production Gemini project is configured as a Paid Service. This configuration must remain associated with an active Cloud Billing account for users in the EEA, Switzerland or the United Kingdom.

Under Google's Paid Services terms, prompts and responses are not used to improve Google's products, but Google logs them for a limited period to detect prohibited use and can process technical usage data separately. Styvi has not verified approved zero-data-retention status and does not promise zero retention.

Do not submit confidential information, special-category data or another person's content unless you have a lawful reason and permission. AI output can be inaccurate, biased, incomplete or unexpected and is not professional advice.

9. Ranking, personalization and moderation

Styvi uses signals such as follows, interactions, freshness, watch or dwell activity, saves, feedback, safety status and account settings to rank or recommend content. Automated image and text systems may label, block, reduce visibility of or route content for review. Human review may be used for reports, appeals and significant enforcement where operationally available or legally required.

These systems can be wrong. You can use available feedback, report and appeal controls or contact us. Styvi does not use automated decisions to determine eligibility for employment, credit, housing, insurance or another comparable high-impact service.

10. Optional app analytics and diagnostics

The iOS app offers two independent choices: Share usage analytics (PostHog) and Share crash diagnostics (Sentry). Both are off until you save an affirmative choice. You can continue without sharing and change either choice at any time in Settings → Data & privacy → Analytics & diagnostics. The choices apply to this installation; signing into another account on the same installation does not create a new consent choice.

PostHog receives only named screens and onboarding steps, feature success or failure categories, purchase and restore steps, the App Store product, price and currency where available, elapsed time, app/build and iOS versions, consent notice version and time, and random installation, session and purchase-attempt references. We do not send the Styvi account ID or identify a person profile. A random reference can still distinguish activity over time, so we treat these records as personal data rather than claiming they are anonymous. Analytics covers people who opt in and does not represent every user or independently verify revenue.

Sentry receives minimized crash stacks, fixed operation/error categories and Apple MetricKit system diagnostics, with selected technical app, device and operating-system context. Crash messages and stack-variable values are removed before sending. No Styvi user identity is attached. System reports can be delayed and may describe an earlier incident.

These integrations are configured to exclude messages, photos, audio, prompts, form values, email addresses, passwords, precise location, signed receipts and transaction identifiers. They do not record screens or sessions and do not use advertising identifiers or cross-app advertising tracking. Providers necessarily receive a network connection's IP address during transport; storage of IP addresses and IP-based location enrichment is disabled. Primary project storage is in the EU. Contracted support, infrastructure or subprocessors can still involve international access subject to the safeguards described above; EU storage is not a promise that every processing step stays in the EU.

Turning an option off stops new optional collection and removes reports still queued for that purpose on this device. A request already in transit can finish. Withdrawal does not automatically erase records previously delivered to a provider or affect earlier lawful processing. A new random analytics reference is created if analytics is later re-enabled. Essential account security, moderation, purchase verification and entitlement delivery continue independently.

For access or deletion of optional analytics, contact privacy@styvi.cc and include the analytics reference displayed in Analytics & diagnostics. Keep an earlier reference before re-enabling analytics if your request concerns that earlier period. We do not maintain a direct link from that reference to your account. Sentry reports have no account identifier; a report/event ID, approximate incident time and app version can help us locate a specific report without collecting unnecessary identity data.

11. Cookies and browser storage

Styvi uses strictly necessary first-party cookies and browser storage to provide the website, authenticate accounts and protect sign-in. Under section 109(8) of Slovak Act No. 452/2021 Coll., consent is not requested for storage whose sole purpose is communication transmission or that is strictly necessary to provide an information-society service you expressly request.

Optional preference storage is off until you choose “Allow optional cookies”. Choosing “Use necessary only” does not limit sign-in, MFA, passkeys, magic links, Device Approval or other account-security controls. Styvi currently uses no advertising cookies, cross-site tracking cookies or browser analytics cookies.

The older cookie names styvi_web_access, styvi_web_refresh, styvi_web_pending_access, styvi_web_pending_refresh, styvi_web_mfa_factor and styvi_web_mfa_challenge are not active storage. The server only sends deletion instructions for them during authentication cleanup.

Cloudflare operational observability and security request processing occur on the server and are not browser analytics cookies. WebAuthn passkey credentials are managed by your browser or operating system rather than stored by Styvi as cookies.

Use the persistent “Cookie settings” control at the bottom of the website to change or withdraw your choice at any time. Withdrawal is prospective and immediately deletes Styvi's optional local and session-storage keys where browser access permits. If Styvi introduces optional analytics, advertising or another storage purpose, this notice and the consent choices must be updated before that purpose is activated.

12. How long we keep information

We keep personal data only for the period needed for the purpose described above, then delete, de-identify or securely isolate it unless law or a legal hold requires longer retention. Because several records are linked, deletion can occur in stages across active databases, storage, queues and protected backups.

• Optional PostHog analytics: the device queues at most 200 unsent events while analytics remains enabled. Only events from the preceding seven days are eligible for delivery; older events are discarded when the app next processes its outbox. An app that is not running cannot perform that cleanup until it runs again. Withdrawal removes the queued file when the choice is processed. The free EU project makes up to one year of events available for analysis. The provider's query window does not itself guarantee physical erasure; we review continued retention and use the provider's deletion process for records no longer needed and valid deletion requests. We do not promise automatic erasure at the end of the query window.
• Optional Sentry diagnostics: event retention is currently 30 days on the free Developer plan and up to 90 days during the initial trial. Issue summaries, aggregate counts, service-account audit records and protected provider backups can have different lifecycles. Withdrawing diagnostics removes the device's optional diagnostics cache; it does not remotely erase an earlier report.
• Account, profile and user content: generally while the account or content remains active, then through the deletion process. Some purchase, safety, audit or AI-usage records can remain where required or can be retained after the account identifier is removed.
• Snips and other time-limited media: expiry removes the item from ordinary viewing, but does not currently guarantee immediate deletion of the database record or stored media. Safety, report, legal and backup needs can extend retention.
• Notes and Moments: an audience, expiry, archive or view-once label controls normal product access, while interaction records, reports, protected media and backups can have separate lifecycles.
• Messages and location: message records, encrypted envelopes, applicable media and delivery metadata follow the conversation and account lifecycle; legacy or unsupported content can remain readable by the service. Deleting a record cannot recall a recipient's saved copy. Opt-in live friend-location payloads are encrypted for intended participants and delivered through a private realtime channel rather than intentionally written to the main location database.
• AI Editor: the current backend makes a completed suggestion available for retries for 10 minutes and schedules cleanup every five minutes, so active stored text can remain for about 15 minutes under normal operation. A cleanup failure can delay erasure. Usage and request records are scheduled for removal after 90 days and can contain request identifiers or digests, without retaining the original draft as usage text. Writing-style aggregates remain until you disable memory, delete the account or an applicable deletion requirement takes effect; revocation removes the active profile. Provider-side processing follows the Google terms explained above.
• Connected music: Spotify credentials and listening records remain while the connection or a lawful operational need exists; disconnecting or changing sharing stops future authorized synchronization, but prior friend-visible observations and provider-side records can follow separate deletion cycles. Music Studio files are private account storage until removed or deleted under the account lifecycle; deleted track metadata can be retained as a usage or billing tombstone.
• Search, recommendation and feature activity: for as long as needed to personalize, secure and improve the service, with reset or deletion controls where available.
• Purchase, entitlement, refund and receipt records: for the account lifecycle and longer where accounting, tax, fraud, platform or consumer law requires.
• Merchandise and creator payouts: delivery details, order and tracking history, earnings and payout records may remain for fulfillment, accounting, tax, fraud, chargeback and legal-claim periods. A cancelled request does not necessarily erase its transaction history immediately.
• Reports, enforcement, security and audit records: for the time reasonably needed to investigate, prevent repeat abuse, defend decisions and meet legal duties.
• Video moderation: review decisions, reason notices, strikes, appeal records and selected evidence can remain for safety and redress. Temporary Google review copies are removed by the processing workflow where it succeeds; a cleanup failure can delay removal.
• Legal-version records: acceptance time, current document versions and up to two seven-day review deferrals are retained with the account and as needed to resolve compliance or contract disputes.
• Support and legal requests: through resolution and an appropriate limitation or record-keeping period.
• Data exports: the signed download link expires after seven days. Expiry of that link is not the same as immediate deletion of the protected export object, which follows the backend storage lifecycle.
• Website Studio: publication history and soft-deleted website media are currently retained without a fixed deletion deadline. Removing an asset from the current page does not by itself erase historical copies.

The current service does not have one universal fixed period for every record. Where a period is not stated, we use criteria including account status, feature lifecycle, sensitivity, user expectations, legal limitation periods, fraud and safety risk, storage integrity and whether information can be de-identified. Contact us for the current period applicable to a specific record.

13. Your choices and rights

Send a request to privacy@styvi.cc. We may need proportionate information to verify your identity and protect the account. Under the GDPR we normally respond within one month, subject to permitted extensions for complex or numerous requests.

Submitting an in-app account-deletion request requires proportionate identity and account-security verification. Gems, AI-credit balances, refund adjustments and active subscriptions do not prevent the request. The current workflow signs out sessions and schedules permanent deletion after a seven-day recovery window. A failed or unavailable request can be raised with our privacy contact for individual assessment, including any need to restrict processing or erase particular data sooner. Certain records may instead be retained or de-identified where necessary for purchases, fraud prevention, moderation, security, legal claims or another lawful reason, and independently copied or re-shared content may require a separate rights request. Removing the app does not delete the account, and deleting a Styvi account does not automatically cancel an App Store subscription.

Depending on applicable local law, you may also have rights to appeal a privacy-request decision, obtain information about international transfers, or request review of a materially significant automated decision. Send the request or appeal to privacy@styvi.cc; we will explain the outcome and applicable complaint route. These rights do not depend on accepting optional analytics or AI processing, and mandatory local rights are not reduced by the choice of Slovak law in the Terms.

• Access personal data and obtain information about its processing.
• Correct inaccurate or incomplete information.
• Request deletion, subject to lawful exceptions.
• Restrict processing or object to processing based on legitimate interests.
• Receive portable data where the GDPR conditions apply.
• Withdraw consent prospectively where consent is the legal basis.
• Use profile, privacy, notification, personalization, block, mute, restrict, export and deletion controls that are available in Styvi.
• Complain to the Úrad na ochranu osobných údajov Slovenskej republiky or another competent supervisory authority.

14. Children and teenagers

You must be at least 18 to create or use a Styvi account. A higher age may apply in a country or to a particular feature. Styvi is not an Apple Kids Category app and is not designed for children below the applicable minimum age.

Slovak law requires parental authorization where consent is used for an information-society service offered to a child under 16. Styvi does not treat a written age statement or restricted-mode label as a substitute for legally valid authorization.

Google's current Gemini API terms prohibit an API client that is directed to or likely accessed by people under 18. While Styvi includes Gemini, the service therefore requires users to be 18 or older. If Styvi later serves minors, Gemini must first be removed or replaced and the age design and this Policy must be updated.

A parent or guardian who believes a child is using Styvi contrary to these rules should contact privacy@styvi.cc. We may restrict the account, request proportionate age information, or delete data where required.

15. Security and incidents

Styvi uses measures such as encrypted transport, authentication and MFA controls, scoped storage, platform attestation or integrity checks where configured, server-side purchase verification, rate limits, access controls and audit records. Live friend-location payloads and supported encrypted message formats are designed to protect their content for intended participants. Coverage varies by format and client version as explained above; the service as a whole is not described as end-to-end encrypted.

No service is perfectly secure. Protect your credentials, use device security, and report suspected compromise. We will assess personal-data incidents and notify affected people or authorities where law requires it.

16. Changes and contact

We may update this Policy when the service, vendors or law changes. We change its version and effective date and provide additional notice for material changes where required. In the iOS app, a signed-in person can accept an updated Terms or Privacy version or choose to review it seven days later, at most twice for that version. After the second seven-day deferral, the app presents acceptance or the account-deletion path. Earlier versions and choice records should be retained for accountability. Acknowledging this Policy does not substitute for a separate consent required for optional processing.

Questions, requests and complaints can be sent to privacy@styvi.cc. Use a clear subject such as “Privacy request”, “Child safety”, “Account deletion” or “Security”.

• Samuel Kubinec
• Status: individual pre-release developer; no company or sole-trader registration has been supplied for Styvi
• Country used for this notice: Slovakia
• Business or service address: Bertotovce 168
• Company or registration ID: none supplied
• Tax or VAT ID: none supplied; Styvi is not represented as VAT-registered
• Register and registration number: none supplied
• Email: privacy@styvi.cc
• Phone: +421951818608
• Consumer and e-commerce supervision: Slovak Trade Inspection, Central Inspectorate, Bajkalská 21/A, P. O. BOX 29, 827 99 Bratislava, Slovakia
• Data-protection supervision: Office for Personal Data Protection of the Slovak Republic, Galvaniho 7/B, 821 04 Bratislava, Slovakia