Skip to main content

Privacy Policy

Last Updated: November 10, 2026

Visxy

1. Introduction

This Privacy Policy explains how Visxy ("we", "us", "our") collects, uses, and protects your information when you use the Service.

Our Terms of Service and Refund Policy explain your contract and purchase rights. This Policy is a notice about personal data, not a request for blanket consent. Where consent is needed, we ask separately; reading this Policy or using the Service does not replace that consent.

The Service is currently available through our website at visxy.com. App Store and Google Play purchases are not currently available; references to those purchase channels apply only if they are offered.

1.1 Who is responsible for your data

Murat Dinç, operating under the name Visxy, is the data controller for the personal data described in this Policy. Visxy is the service name, not a separate legal entity. The Service is offered internationally in English and is operated from Türkiye.

Correspondence address: Hamidiye Mah., Sanayi Sit., 15029 D:24-A, 10300 Edremit, Balıkesir, Türkiye.

For any question about this Policy or about your data, contact support@visxy.com.

2. Information We Collect

2.1 Account Information

When you create an account, we collect your email address and/or username and authentication data via our authentication provider (Supabase Auth), including information from Google or Apple if you sign in using those services.

Acceptance and age records. We record which published version of the Terms of Service and of this Privacy Policy you accepted, when, and whether at sign-up or later; and your confirmation that you are 18 or older, with when and where you gave it. We do not collect your date of birth or any identity document for this.

2.2 Usage Data

We collect data about how you interact with the Service, such as prompts viewed, copied, and favorited. Page and session counts, and how long public pages take to become usable on your device, are measured by Vercel Web Analytics and Vercel Speed Insights (cookieless measurement — see Sections 3.1, 4, and 5). If you accept analytics cookies, Google Analytics also records pages visited and similar usage events.

2.3 Subscription & Payment Information

Purchases are not currently available. Before purchases are offered, we will identify the seller, payment provider and their roles here and at checkout. To deliver a purchase and handle refunds, we receive limited transaction and subscription information; we do not store full payment card details.

If App Store or Google Play purchases are offered, the relevant store handles billing and provides us with purchase or subscription status.

Refund and dispute records. If you ask for a refund, we keep a record of the request, what it concerned, and what we decided — together with the correspondence it took. Where a refund is made, the purchase record is marked as refunded rather than deleted, because the record of a period is what makes its licence code verifiable (Section 2.4). The same applies to a payment dispute or chargeback raised through your bank or an app store. Our Refund Policy explains when a refund is due and how to ask for one.

2.4 License & Copy Records

If you hold or have held a Premium subscription, we generate and store license and usage records associated with your account:

  • License codes: for each active Premium period, we generate a unique license code (VISXY-XXXX-XXXX-XXXX) and store it, along with the plan, start and end dates, and status, as part of your subscription history. These records remain in your subscription history after a period ends, until account deletion, subject to the retention exceptions in Sections 6 and 7.
  • Copy records: prompts you copy while a Premium period is active are recorded under that period's license code, so you can review the prompts you used during that period. Copies made outside an active Premium period are recorded without a license association.

License codes may be verified through our public verification page (visxy.com/license), which exposes only the plan, period, and status of a code — never the identity of the account holder or any personal information. See our Terms of Service, Section 6.3, for how these records relate to your usage rights.

2.5 AI Generator Data

If you use the AI Generator, we collect and store:

  • The prompts you write, and the settings you chose (model, size, duration, and so on);
  • How you organise your own work — the models you pin; setups you save (a name, a model, its settings, a prompt and the kinds of input it expects); collections (a name and which reference files, results, characters and saved Visxy items belong to it, in order); characters (a name, a kind, an optional description, optional age, gender and country describing the character, and which reference files are its pictures); brand kits (a brand's name, an optional description, its colours, font names and guidelines, and which files, characters and saved Visxy items belong to it); and albums (a name and which results belong to it). These records link to the files without making a copy. Items in your personal Generator library are private to your account. Files, characters, brand kits and collections in a Business workspace are shared with its members;
  • Visxy items you save or report — which of Visxy's ready characters and elements you saved, and when. Using one in a generation is recorded with that generation's inputs and adds to a use count kept for the item, which holds nothing about you. A report on an item stores your account, the item, your reason, your optional note and how it was handled. Browsing the catalog without an account reads only published items and does not record individual item views. An item you try in the composer stays in your browser until you sign in or leave. Site-wide measurement is described in Sections 2.2 and 4;
  • Reference files you upload, until you delete them or their retention period ends (Section 6);
  • The media you generate, stored privately against your account;
  • Results and original inputs we add for you, with your consent or documented authority, together with their recorded prompt, model and settings. These also appear in your personal result and reference libraries and follow the normal file retention rules in Section 6. Adding them does not create a credit charge;
  • Generation records — which model ran, whether it succeeded, any error the model returned, and the credits held and charged;
  • Credit ledger entries — every grant, hold, charge, refund and expiry, kept as the audit trail behind your balance;
  • Credit pack purchases — which pack, when, where it was bought (web, iOS or Android), the payment's transaction identifier, the credits it granted, what is left of them and when they end;
  • Credits we grant you, with a short internal note of why and which member of staff added them. The note is not shown in your account, but it is part of the data you can ask us for (Section 8);
  • Model refusal records, where a model provider declined a request or its safety checker withheld a result after it was made: when, for which generation, which model and provider, and the code or message the provider returned. A withheld result is never delivered, stored or charged. A refusal is not treated as a breach of our rules and never limits your account or your Generator access (Terms of Service, Section 7A). These records let a person look into a pattern of refusals and review a decision about your Generator access;
  • Generator access records, if a person at Visxy stops your access to the Generator: when it was stopped and restored, and which member of staff did each;
  • Trust & Safety case records, when reports or safety signals concern your account or something you made: what the case is about, which reports and signals joined it — each report's reason, how it was handled and the account that sent it — the case's history and, for a generation, that generation's record (its model, provider, outcome, credits and cost; never your prompt or your files). A case is how reports about one thing on one ground are handled together, and how a later report on a ground already decided is recognised rather than starting over;
  • Content-rule records, if Visxy's own content rules stopped a request before it was sent (Terms of Service, Section 7A): when, which model, which rule matched and the listed words that matched it. For the most serious category only — sexual content involving minors — the text of the request is also kept, inside a restricted case that only administrators can open, each opening recorded with a reason;
  • Decisions, restricted files and appeals, when a person decides about a report or a safety concern: the decision, the message written for you and an internal note, any action taken on your content; a file restricted while it is reviewed, with the note shown to you and its release; and, if you ask for another look, your request, the outcome and any credits added to make up for a wrong decision;
  • Report protection records: to keep reporting from being misused, we use how many reports an account sent in the last day and how its earlier reports were settled, and we note on a case when many reports arrive at once from new accounts. Staff see counts, not who sent them;
  • Staff review records, if a member of staff looks at your private content (Section 3.3): who reviewed it and in which role, when, why — and the case, if any — which of your prompts they opened and which of your files they were sent. The record never contains your prompt or your files;
  • Publications, if you make any — what you published, which inputs you marked reusable, your separate output reuse permission and changes to it, whether your username is shown, which version of the publishing terms you accepted and when, and a record of each publish, withdrawal and removal (Terms of Service, Section 6A.7).

What leaves Visxy. Your prompt text and any reference files you attach are transmitted to the provider serving your selected model (fal.ai, Replicate, kie.ai or Higgsfield). They are processed under that provider's applicable privacy policy, content policy and service terms. We do not transmit your account identity, email address, or payment details to them, but your submitted content may itself contain personal data. kie.ai is a reseller of other model vendors; a generation it runs may also be processed by the upstream vendor it uses to fulfil the request, under that vendor's own terms.

Higgsfield model-training permission is not granted. We do not authorise Higgsfield to use your Generator inputs or outputs to train, develop or improve its general-purpose AI models. Its API terms permit training by default unless the API customer opts out or has a written no-training commitment. Visxy requires that exclusion to be effective and cover the selected model before sending your content. The exclusion is for API content; it does not govern content you submit directly to Higgsfield's website or other products, and does not undo training use before it took effect. An exclusion from model training does not prevent processing needed to fulfil your generation, security checks, support or lawful retention. See Section 6 and Higgsfield's API terms.

Generated media is private by default. It is not listed in a public gallery unless you publish it, and it is not used by us to train models. If you share a generation or a collection, anyone with its link can view the shared content until the link expires or you revoke sharing, as applicable. A shared collection also shows its title and your public name — the same name your public profile shows, described below.

Publishing makes data public that you chose to publish. A publication shows its result, your submitted prompt and any rewritten prompt the model returned, the model name and the original inputs to anyone, including people without an account. Visxy catalog files are excluded (Terms of Service, Section 6A.8). Anyone who can see a publication can save what is shown. A publication approved for Community can also be shown, with its prompt, as an example on its public model page, which search engines may index. Inputs you mark reusable may be used by others when they recreate your publication. Your output may be used as a new input only if you separately allow it. Turning that permission off stops new uses without erasing already generated results or recalling saved copies. If we add a publication to your profile on your behalf, we keep a private record of your consent or the authority we relied on.

Your public profile is a page every member has, whether or not anything is published on it. When your username is visible, the address uses your current username. Anonymous profiles and members without a username use a permanent identifier. The identifier link continues to work if you change your username; previous usernames do not remain aliases for your profile. The page shows your public name, your live published creations and the month you first published. With your username visible, it can also show your profile photo and the optional bio, expertise areas and profile links you save in Settings. You can feature selected published creations and choose already-shared collections for a profile showcase. Adding a shared collection to the showcase makes its existing link discoverable on your profile; private collections stay private.

The name follows one setting for your whole profile, and the same setting names you on the favorite collections you share by link: your username, or "Anonymous" if you choose that. Until you choose a username, a neutral name ("Visxy creator") stands in for it — never your first or last name or your email address. You make the choice in the publish window, in Settings or in your list of publications in the AI Generator. In Settings, the choice applies when you press Save. It covers every publication and shared collection you have, and every one you publish or share later. If you published before this setting existed and had not chosen to show your username, you stay Anonymous until you choose otherwise.

A new profile photo you upload is shown publicly once a Visxy safety check has cleared it; until then everyone keeps seeing your previous photo, and removing a photo takes effect at once. The photo of the account you sign in with (Google or Apple) waits for the same check before it is shown.

Anonymous hides your username, profile photo, profile links, bio, expertise and collection showcase. Your profile and published or featured creations remain public, and shared collection links continue to work. Anonymous does not change what your media or a collection's title shows, and it cannot recall information someone has already seen or saved. Your email address, private first and last names, plan and unpublished generations are not shown. The profile asks search engines not to index it.

Following and blocking. We store your follow and block choices and in-app notification preferences. Your connection lists and block list are private. A creator can receive an alert when you follow them, using your current public name; Anonymous keeps that name hidden. You can control follower and followed-creator activity alerts in Settings. Blocking removes both follow connections and hides each person's published work from the other while signed in. Public content remains accessible without signing in.

Profile and creation reports. If you submit a report, we store the reporting and reported accounts, the reported profile or creation, your reason and optional details, and the review outcome. These records are private and available to authorized reviewers for handling abuse and complaints. Reports about the same profile or creation on the same ground are handled together as one Trust & Safety case, described above; the case keeps your report's reason and outcome, not its details. Submitting a report does not automatically remove content or alert the reported account. Avoid including unnecessary personal information in report details.

2.6 Social account data

We use the Meta Graph API to manage comments and public replies on our own Instagram account. We process comment text, comment and post identifiers, commenter identifiers, timestamps and reply status to display and classify comments, match keywords and avoid duplicate replies. We do not link these records to Visxy accounts or use them for advertising profiling. They are handled through our service infrastructure and Meta, whose own privacy terms also apply.

We do not currently process automated Instagram direct messages or Facebook automation data.

2.7 Device & Technical Data

We may automatically collect device information, IP address, browser type, and operating system for security and analytics purposes. Additionally:

  • Cloudflare processes network traffic (including IP addresses and HTTP request metadata) as part of our CDN, DDoS protection, and security infrastructure. This processing occurs at the network level before requests reach our servers.
  • Vercel receives page, device and performance information for public-site measurement. Web Analytics uses a temporary identifier derived from request data to distinguish visitors within a day; it is discarded after 24 hours. These tools do not set analytics cookies. See Section 5.
  • Google reCAPTCHA may collect behavioral signals, IP address, and browser/device information to distinguish human users from bots. This data is processed by Google under Google's Privacy Policy and Terms of Service.
  • Higgsfield hosts the example pictures of the styles some Generator models offer. When you open a model's style library, or a style you chose is shown with its picture, your browser loads those pictures directly from Higgsfield's servers. Like any web request, this gives Higgsfield your IP address, browser and device information, and which picture was requested. We do not send the address of the Visxy page, your account details or your prompt with these requests. Higgsfield's Privacy Policy applies to them.

2.8 Account Enforcement Records

If we suspend your account (Terms of Service, Section 11.2), we record:

  • when the suspension started, and when it ends if it is time-limited;
  • the reason shown to you — the same text you see in the Service and receive by email;
  • an internal note explaining the decision, written for our operators;
  • which administrator applied it, and which lifted it;
  • when it was lifted, and any note on that.

These records are the account's enforcement history. They are what lets us review a decision we are asked to reconsider, answer a complaint about it, and defend it if it is challenged. The internal note is not displayed to you inside the Service, but it is personal data about you: you may request a copy of it as described in Section 8.

If you ask us to delete your account, we record the date of the request and the date deletion is scheduled to run, so that the recovery window works and so we can show when a request was made.

2.9 AI Tools Data

Browser tools. Content handled entirely in your browser is not uploaded to us. We receive aggregate tool-use counts, with a tool name, date and count but no content or user identifier. Local preferences and recent-result references stay on your device until cleared.

Server text tools. Your submitted text and, where supported, attached images or extracted video frames are sent through our server to fal.ai for processing. This applies to free server requests as well as paid ones. The returned text is not saved in your Generator library. Paid requests leave job and credit-ledger records; a free daily allowance uses a usage counter. Files uploaded into your reference library are stored under the reference-file rules in Sections 2.5 and 6, even when the returned text is not saved.

Image and video tools. Paths that use the AI Generator send inputs to the provider serving the selected model and store generated media privately, as described in Section 2.5.

Free-allowance counters. Signed-in requests are counted against your account; guest requests use a random browser identifier. This identifier is pseudonymous, not a guarantee of anonymity. Clearing browser storage removes the local identifier, not necessarily an existing server record. Counters do not contain submitted content.

If you accept analytics cookies, Google Analytics also receives the tool name and whether the path was free or paid, without the content you submitted.

2.10 Creator Partnership data

If you apply to, or take part in, the Creator Partnership Program (Terms of Service, Section 6D):

  • Your application — the display name you publish under, the links to your channels, the channel type, your audience size band, how you intend to promote Visxy, your country, any note you add, your confirmation that you are 18 or over, and when you accepted the Creator Partnership Agreement and which version of it. We also record our decision and, for a rejection, the reason we show you. Our staff may add an internal note that is not shown to you; you may request it under Section 8.
  • Your partnership — your referral code and any shorter link name we assign, its status, any commission rate set for your partnership, and each change to it — approval, suspension, ending, a rate or link-name change or a balance correction — with when, the reason and which member of staff made it.
  • Visits to your own referral link — we retain a pseudonymous device identifier for 180 days to review possible self-referrals.
  • Your balance — every commission, reversal, spend, adjustment and forfeiture, with the date, the amount in US dollars and, for a commission, the type of product that earned it. For a commission we also keep the payment processor's transaction reference, so that a refund of that payment can reverse it.
  • Traffic statistics — daily counts of how many times your link was opened, by how many distinct devices, how many sign-ups and first purchases followed, and how many referrals expired unused.

We do not collect bank details, tax identification numbers, identity documents, subscriber lists or passwords for the Program.

If you opened a partner's link. We record the visit, the page you opened and a pseudonymous device identifier for the 30-day referral window. We do not store your IP address or a hash of it for referral attribution. On the website, a referral marker is saved across visits only if you accepted cookies; a sign-up during the same visit may still be attributed without that marker. If you sign up or sign in while a referral is valid, we associate it with your account. Partners see visit and sign-up counts and, if a qualifying purchase occurs, its day, product type, purchase channel and commission. We never give the partner your name, email address, account or payment details. We may review referrals for abuse or self-referral; this does not change your price or account access, and a person reviews disputed decisions. When an unconverted referral window ends, the device record is deleted and only an anonymous daily count remains.

2.11 Email subscription data

If you consent to marketing email, we record your email address, whether you are subscribed, when and where you consented (for example: from account settings, from the app, or from the form on our website), the frequency you chose, and when you unsubscribed if you did. We keep the record of a withdrawn consent alongside the consent it withdrew, because the pair is what evidences that we were permitted to write to you at the time and stopped when you asked.

You can subscribe without an account. If you do, we hold your email address, whether you are subscribed and at what frequency, when and where you confirmed (and when you unsubscribed, if you do), and the delivery record of each message we send you (Section 5) — and nothing else: no profile, no account, no browsing history tied to it. We send one message asking you to confirm, and an address that is never confirmed is not subscribed and receives nothing further. Subscribing this way does not create an account. If you later create an account with the same address, we link the two once that address is confirmed, so you do not appear on the list twice; if the two records disagree about whether you want marketing email, the unsubscribe wins — and the same holds when you move an account onto an address that subscribed without one. An unsubscribe stops every subscription that mails your inbox. If you change your account's email address, your subscription moves with it.

Every marketing message carries a link that unsubscribes you and an Email preferences link that changes how often you hear from us, both without signing in. Section 3.1 gives the legal basis, Section 5 names the provider that delivers it, and Section 6 says how long we keep it.

2.12 Contact messages and support requests

Without an account, the contact form collects the name and email address you provide, the topic and message, when it was sent and whether our support staff have read it. We use those details to handle your enquiry and reply to the address you gave. Creating an account later with the same address does not turn that message into a support request in the account.

Signed in, a support request is linked to your account. We store its topic, your messages and our replies, who wrote each message and when, whether the request is waiting for a reply or resolved, and its status history. We also keep read positions to show you new replies and avoid repeated email notices while earlier replies remain unread, and records of whether a notice was sent or could not be confirmed. Read positions are not displayed as mutual read receipts.

Only you and authorised Visxy support administrators can read your request through the support system. Those administrators can also see your username and account email to handle it. Your request is not public, and another member cannot read it merely because they know its address. Avoid sending passwords, API keys, payment-card details or personal information that is not needed to explain the problem.

Support reply notifications contain a general notice and a link to the conversation, not its topic or message text. The link requires you to sign in to the account that owns the request; it does not itself grant access. Messages you send directly by email, and replies to a guest enquiry by email, may contain the correspondence itself. Sending a support request or a contact message does not subscribe you to marketing. Sections 3, 5 and 6 explain the purposes, delivery providers and retention.

2.13 Notifications

We build your notification bell from records the Service already holds — your follows, published creations and the decisions about them, safety records, your generations and your support requests — and keep no separate copy of each notification for you. For the bell we store:

  • What you have read or dismissed. For an announcement from Visxy: whether you marked it read, followed its link inside Visxy or dismissed it, and when. For the other notifications: the ones you marked read or dismissed, and up to when you used Mark all as read.
  • Your notification choices, including the optional kinds you switched off (Terms of Service, Section 6B.4).

We use these records to show your notifications as read or unread, and to count how many members read an announcement, followed its link or dismissed it. Authorised Visxy administrators can see which announcements you read when looking after your account, and the totals for each announcement. Section 6 says how long we keep them.

3. How We Use Your Information

We use the information we collect to:

  • Provide and maintain the Service (account management, favorites, history);
  • Process subscription payments and manage premium access;
  • Generate license codes, maintain license and copy records for your Premium periods, and enable public verification of license codes (see Section 2.4);
  • Display sponsored placements to Guest and Free Account users, and count impressions and clicks in aggregate so sponsors can be reported to (Premium subscribers do not see them);
  • Analyze usage trends to improve the Service (Vercel Web Analytics and Speed Insights on every public visit; Google Analytics only if you accept analytics cookies);
  • Communicate with you (e.g., account verification, security notices, support);
  • Detect and prevent fraud or abuse;
  • Enforce our Terms of Service — including suspending an account, recording why, and reviewing that decision if you contest it (see Section 2.8);
  • Manage comments and replies on our Instagram account, including keyword matching and deduplication (see Section 2.6);
  • Operate the Creator Partnership Program — reviewing applications, attributing referrals, calculating and reversing commissions, keeping each partner's balance, and detecting self-referral and fraudulent traffic (see Section 2.10).

The table below describes the purposes and bases for processing under the GDPR or UK GDPR where applicable. Reliance on legitimate interests requires necessity and a balance against your rights; you may object as described in Section 8. It is not a substitute for consent where the law requires consent.

Under Türkiye's KVKK, processing must separately meet an applicable condition under Article 5, such as necessity for a contract, a legal obligation, establishment or protection of a right, or legitimate interests that do not harm fundamental rights; otherwise explicit consent is required. Special-category data and international transfers have additional requirements. Similar labels in different laws do not make their conditions interchangeable.

What we processWhyLegal basis
Account and authentication dataTo create and run your accountPerformance of a contract
Contact messages and member support conversations, their status/read records and reply noticesTo answer an enquiry, provide account support, follow up on a complaint and keep the conversation available to youPerformance of a contract or steps you ask us to take before one, where necessary for that purpose; legitimate interests in handling other enquiries and complaints
Subscription and billing statusTo give you the access you paid forPerformance of a contract
Transaction and invoice recordsTax, accounting and audit obligationsLegal obligation
Generator and server-tool inputs, generated media and text responsesTo perform the request and, for saved media, keep the result availablePerformance of a contract
Publications, your public profile, and the record of what you agreed toTo show what you chose to publish, let others reuse the inputs you marked, and honour a withdrawal or a removalPerformance of a contract (the publishing feature you chose to use); legitimate interests (evidencing consent and handling complaints)
Consent or authority records for a publication we add on your behalfTo evidence that we were allowed to add itLegitimate interests; establishment, exercise or defence of legal claims
Credit ledger and generation recordsTo operate your balance, and to show you and us an accurate record of what was chargedPerformance of a contract; legitimate interests (accurate billing records)
License and copy recordsTo evidence the commercial rights attached to a Premium periodPerformance of a contract
Usage analytics (Google Analytics)To understand how the Service is used and improve itConsent, given through the cookie banner
Cookieless site measurement (Vercel Web Analytics and Speed Insights)To count public visits and to see how fast the Service is for real visitorsLegitimate interests (running and improving the Service)
The request your browser sends to Higgsfield for a style's example picture (Section 2.7)To show the styles a model offers when you open its style libraryLegitimate interests (showing the options you open, from the provider that publishes them)
Sponsored placement impression and click countsTo report performance to a sponsor, in aggregateLegitimate interests (running a funded free tier)
Security, fraud prevention, rate limiting, bot protectionTo keep the Service and its users safeLegitimate interests; legal obligation where applicable
Model refusal records and Generator access recordsTo let a person look into a pattern of refusals, to stop or restore Generator access when a person decides to, and to review that decisionLegitimate interests (keeping the Generator safe and fair); legal obligation where content law requires it
Trust & Safety case recordsTo handle the reports and safety signals about one thing together, to review a decision and to recognise a report on a ground already decidedLegitimate interests (keeping the Service and its users safe); establishment, exercise or defence of legal claims; legal obligation where content law requires it
Staff review recordsTo keep every look at private content accountable, and to answer a question or complaint about oneLegitimate interests (accountable moderation); establishment, exercise or defence of legal claims
Legal hold records and the files they keepTo preserve evidence a court order, an authority's request, a legal claim, an investigation or a legal duty requiresLegal obligation; establishment, exercise or defence of legal claims
Account enforcement records (suspensions)To enforce the Terms, to review a suspension we are asked to reconsider, and to defend the decision if it is challengedLegitimate interests; establishment, exercise or defence of legal claims
Deletion request and scheduleTo operate the recovery window and evidence when a request was madePerformance of a contract; legal obligation (responding to an erasure request)
Error monitoring (Sentry)To find and fix faultsLegitimate interests
Transactional emailTo send account, security and billing messages, and notify you of a support replyPerformance of a contract
Marketing email, and the record of your consent to itTo send product news, new prompts and models, and offers — and to evidence that you asked for themConsent, given separately from creating an account and withdrawable at any time
Email delivery and suppression eventsTo deliver messages and honour objectionsLegitimate interests; legal obligation where applicable
Email open and click measurementTo understand engagementConsent where required for tracking; otherwise legitimate interests subject to applicable law. Marketing consent alone does not necessarily cover tracking
Suppression list (addresses that hard-bounced or reported us as spam)To make sure we send that address no further marketing or broadcast emailLegitimate interests; legal obligation (honouring an objection)
Meta comment automationTo operate our own social accountsLegitimate interests
Creator Partnership application and partnership recordsTo decide an application and run the partnership you asked to joinPerformance of a contract (the Creator Partnership Agreement)
Partnership balance, commissions and their payment referencesTo credit, reverse and spend a balance accurately, and to evidence itPerformance of a contract; legitimate interests (accurate records); legal obligation where tax or accounting law applies
Referral marker, per-device referral record and daily traffic countsTo attribute a referral to the partner whose link you opened, and to detect fraudulent clicksLegitimate interests (running a referral program fairly), balanced by keeping the record for the referral window only and never telling the partner who you are
Reporting suspected child sexual abuse materialTo meet applicable reporting and preservation dutiesThe specific legal obligation that applies; any special-category or criminal-offence data requires the additional conditions prescribed by law

Where we rely on consent, you may withdraw it at any time; withdrawal does not affect processing already carried out.

3.2 Automated decision-making

Automated eligibility, security and content checks can stop an individual action, such as a generation request. Account suspensions and lasting restrictions on Generator access are decided by a person. If you believe a check was applied incorrectly, contact support@visxy.com. We do not profile you for advertising.

A model's refusals do not limit you. A model provider may decline a request; we record it (Section 2.5), but no number of refusals stops or limits your access to the AI Generator or your account. Stopping your Generator access and suspending your account are decided by a person, who reviews the decision if you contest it.

Generator access stopped automatically before. The Service used to stop Generator access automatically after repeated refusals; it no longer does. Where a stop made that way is still in place, it stays until a person reviews it. You can ask for that review at any time: write to support@visxy.com, and a person will hear your explanation and restore access where the stop was wrong.

3.3 Who inside Visxy can see your data

Access is limited to the people who need it to run the Service. Our administrative tools do not show your private prompts, reference files or generated media. When an administrator — or a moderator handling a report assigned to them — needs to see them, they open a recorded review: they state why (a report or case, a safety signal on your account, a pattern that needs a person, a legal request, or an appeal you made), and each prompt they open and each file they are sent is recorded with who, when and why (Section 2.5). A moderator sees only what the report they handle is about. When you ask for a generation or a profile photo to be made public and no check has cleared it yet, an administrator looks at the files and the prompt that would be shown, in the same recorded way, before approving it. Cases about the safety of children are handled by administrators alone, through a separate restricted procedure: no previews are shown, each original file is opened one at a time with a recorded reason, and the material is never sent to any outside service. Our engineers can also reach stored data through the database itself — to maintain the Service, handle a security incident, resolve a billing dispute or meet a legal obligation — and that access is not part of the review record. We access your material only where there is such a reason. We do not read prompts or view generated media for curiosity, for training, or to build any public or promotional content — other than showing, where you published it, what you yourself chose to publish, and reviewing publications when we moderate them.

4. Cookies and Tracking Technologies

We use cookies and similar technologies for the following purposes:

  • Essential cookies: required for authentication and core functionality (e.g., keeping you logged in).
  • Analytics cookies: Google Analytics, used to understand usage patterns and improve the Service.
  • Cookieless site measurement (Vercel): Web Analytics and Speed Insights run on public pages and are not switched off by declining the cookie banner. They set no analytics cookie, but Web Analytics uses the temporary identifier described in Section 2.7. Cookieless measurement remains subject to applicable privacy rules.
  • Security cookies: Google reCAPTCHA uses cookies and behavioral signals to detect and prevent automated abuse when bot protection is enabled. reCAPTCHA may run on account sign-in, sign-up, password reset, and the contact form. Use of reCAPTCHA is subject to Google's Privacy Policy and Terms of Service (see also Section 5). We disclose this in our legal documents rather than repeating it on every form.
  • Generator drafts and recent prompts: the Generator keeps your unsent draft and the last prompts you generated with in your browser, separately for each account, so they survive a reload. They are stored on your device, are not cookies sent with every request and are not used to profile you. Signing out removes them from that browser.
  • Local storage used by AI Tools: the free tools keep a few preferences in your browser — recently opened tools, your last filter choices, a flag recording that you have seen the introduction, and, for a guest, the identifier used to count a daily free allowance. These are stored on your device, are not cookies sent with every request, and are not used to profile you. Section 2.9 describes each of them.
  • Creator Partnership referral marker: if you open a partner's referral link and accept cookies, a first-party marker remembers the referral for up to 30 days. If you decline cookies, we do not keep that marker on your device. It is used for referral attribution, not advertising profiling, and is not shared with the partner or an advertising network. Section 2.10 describes the related records.
  • Sponsored placements: the promotional slots shown to Guest and Free Account users are sold and served by us directly — they are not a third-party ad network, they set no advertising cookies, and nothing about you is shared with the sponsor. We count how many times a placement was shown and how many times it was clicked, in aggregate, so we can tell a sponsor how their placement performed. Those counts are not tied to your profile and are not used to build an advertising profile of you. Premium subscribers do not see sponsored placements at all. We do not currently use any third-party advertising network. If that changes, we will name the provider in this Policy before it runs, and you will be able to manage personalization through that provider's settings or industry opt-out tools.

You can control cookies through your browser settings. Disabling certain cookies may affect the functionality of the Service. Where required by applicable law, we will request your consent before setting non-essential cookies, and you may withdraw that consent at any time.

5. Third-Party Services

We share data with the following third-party service providers, each governed by their own privacy policies:

  • fal.ai, Replicate, kie.ai and Higgsfield: AI model inference for the Generator and server-based AI Tools, including free text requests. Only the provider handling a request receives its submitted text and relevant files or frames. We do not send account identity or billing details, but your submitted content may itself contain personal data. Each is governed by its applicable privacy and content policy (fal.ai, Replicate, kie.ai, Higgsfield). Higgsfield API training use is restricted as described in Section 2.5. A reseller request may also be processed by the upstream model vendor under that vendor's own terms; a Higgsfield training exclusion does not automatically bind an upstream provider whose terms differ. Higgsfield also hosts the example pictures shown in a model's style library, which your browser loads from it directly (Section 2.7).
  • Supabase: database, authentication, and storage infrastructure.
  • Payment providers: no web provider is currently accepting purchases for Visxy. We will identify the selected provider and its data role before opening checkout.
  • Apple: sign-in authentication (Sign in with Apple) and, if an iOS purchase channel launches, store billing, governed by Apple's Privacy Policy.
  • Google: sign-in authentication (Google Sign-In), usage analytics (Google Analytics), bot protection (reCAPTCHA), and, if an Android purchase channel launches, store billing, governed by Google's Privacy Policy and Terms of Service.
  • Sentry (Functional Software, Inc., sentry.io): error monitoring and crash reporting. When an application error occurs, technical information such as the error message, stack trace, browser/device information, page URL, and approximate timestamp may be sent to Sentry. We configure Sentry to scrub personal data (including email addresses, user-generated content, cookies, and IP addresses) before transmission, in line with the principle of data minimization. This processing is carried out on the basis of our legitimate interest in maintaining the security and proper functioning of the Service.
  • Vercel, Inc.: hosting, Web Analytics and Speed Insights. Measurement includes page URLs, device/browser information, approximate location and page-performance metrics. Web Analytics uses a daily, request-derived identifier rather than a persistent cross-site identifier. These tools run on public pages, not the admin panel or Generator, and currently run independently of the cookie banner. See Web Analytics privacy and Speed Insights privacy.
  • Cloudflare, Inc.: content delivery, network security and media storage. Cloudflare processes network-level data including IP addresses and request metadata in transit.
  • Brevo (formerly Sendinblue, SAS): service email only — account verification, password reset, email-change confirmation, security notices, receipts, support reply notices and the other messages described in Terms Section 6B.1. Brevo receives the recipient address and the email needed for delivery. For a member's support reply notice, that is a general message and a link, not the support conversation or its topic. Brevo is not used for marketing email.
  • Resend (Plus Five Five, Inc.): marketing and broadcast email — the product news you opted in to, and occasional announcements sent to all members. Resend receives your email address, the content of the message, and the events its own systems record about it (whether it was delivered, bounced, or reported as spam, and whether it was opened or a link was clicked). It is a separate provider from Brevo on purpose: a complaint about a marketing message cannot then affect the delivery of a password reset. See Resend's Privacy Policy.
    • Open and click measurement. Marketing messages may include a small tracking image and links that pass through Resend before reaching their destination. This is how "opened" and "clicked" are recorded. Open tracking is unreliable by design of modern mail clients — Apple Mail Privacy Protection loads images for everybody — so we treat it as a weak signal, never as proof that you read something. Unsubscribing stops future marketing messages. Tracking already embedded in a received message may still contact the provider if you later open it or follow a link. Where tracking requires consent, permission to send marketing alone is not sufficient.
    • Suppression. If an address hard-bounces or reports a message as spam, we add it to a suppression list and send it no further marketing or broadcast email; account, security and billing messages are not affected. That list holds the address and the reason, and exists so an objection cannot be undone by a later mistake.
  • Google reCAPTCHA: bot detection and abuse prevention. reCAPTCHA may collect behavioral signals, IP address, and browser/device information to assess whether interactions are made by a human user. This data is transmitted to Google and is governed by Google's Privacy Policy and Terms of Service.
  • Meta: the Instagram comment and public-reply integration described in Section 2.6. Meta processes social account interactions under its own privacy terms; our infrastructure handles the records needed for that integration. Instagram automated DMs and Facebook automation are not currently active.
  • Advertising networks: none. Sponsored placements are served by us directly, as described in Section 4; no third-party advertising provider receives your data today. Any future provider will be named here before it is enabled.

We do not sell your personal information to third parties.

6. Data Retention

We retain your account information for as long as your account is active. If you delete your account, we will delete or anonymize your personal data, except where retention is required for legal, accounting, or fraud-prevention purposes (e.g., transaction records).

Backups. Deleting your account removes your data from our live systems. Routine encrypted backups may still contain a copy until they are overwritten on their normal rotation schedule. During that period the backup is not used for any other purpose, and is not searched, restored, or analysed except to recover the service from failure.

Support and contact records (Section 2.12). Member support conversations, status history, read positions and notification records stay with your account so that you can return to earlier requests. Marking a request resolved does not delete it. Completing account deletion removes those records from the live support system; an open request does not prevent deletion. Backup copies follow the rule above, and deleting an account cannot recall email already delivered to an inbox. You may ask for earlier erasure under Section 8.

Notification records (Section 2.13). Whether you read, followed or dismissed an announcement from Visxy is kept for 120 days after it was sent. After that we keep only the totals for that announcement, with no link to you, and delete the records about each member. Your read and dismissed marks for other notifications are kept with your notification settings and dropped as the notifications they refer to leave your list. Deleting your account removes them.

Guest contact messages and correspondence sent directly by email are separate from account support requests. We retain them for handling and following up on the enquiry and, where necessary, a specific complaint, legal obligation or legal claim. They are not automatically attached to a later account or erased by deleting that account; contact us under Section 8 to request their erasure. We do not treat an enquiry being marked resolved as a reason to retain unrelated information indefinitely.

License and copy records (Section 2.4) are retained as part of your subscription history for the life of your account, including after individual Premium periods end, so that your record of commercial usage rights remains available to you. These records are removed when you delete your account (see Section 7), subject to the legal and accounting retention exceptions above.

AI Generator data is retained as follows:

  • Generated media you delete goes to Trash for 3 days, unless an earlier retention deadline applies, and is then permanently removed by scheduled cleanup.
  • Once you hold neither an active Generator plan nor any usable credits, a 90-day retention period starts for your generated media. After that deadline, scheduled cleanup permanently removes it. Export work you want to keep before the deadline.
  • Reference files you upload are kept until you delete them or delete your account, and follow the same 90-day retention period as your generated media: once you hold neither an active Generator plan nor any usable credits, scheduled cleanup permanently removes them after that deadline. Starting a plan again, or holding usable credits again, stops that clock. A reference file a live publication shows is kept for that publication.
  • Pinned models, saved setups, collections, characters, brand kits, albums and the Visxy items you save are kept until you change or delete them, or delete your account. Deleting one deletes no file or result, and none of them keeps a file longer than the rules above: a reference file or result that you delete, or that scheduled cleanup removes, simply leaves them. A Visxy item that Visxy takes down leaves your saves at once.
  • Reports on Visxy items are kept while the item exists — for an item Visxy took down, as part of the record of that takedown — for handling the report and later complaints about the item; if you delete your account, a report stays without your account attached.
  • Generation and credit ledger records are retained for the life of your account as the audit trail behind your balance and charges, and are removed when you delete your account, subject to the legal and accounting exceptions above.
  • Credit pack purchase records are transaction records: like refund records below, they are kept after an account is deleted with the account identifier removed, because a seller must be able to evidence a sale. Unused credits are forfeited on deletion (Section 7.2).
  • Model refusal records are kept for as long as your account exists and are deleted with it. Generator access records — a restriction of your access to the Generator, its reason, when it started and ended and who decided it — are kept for as long as your account exists; if you delete your account, they stay without your account attached, as the record of what staff did.
  • Profile and creation reports are kept while they are open and after they are settled, as the record of how they were handled. When you send a new report, your settled reports older than 90 days are cleared, and no more than 20 of your reports are kept. Deleting your account, or the reported account, deletes the reports.
  • Trust & Safety case records are kept after the reports in them are cleared, so a decision can be reviewed and a later report on the same ground recognised. When an account is deleted, the cases about it keep no link to it, and a report it sent stays in its case without the account attached.
  • Staff review records are kept for as long as your account exists; if you delete your account, they stay without your account attached, as the record of what staff did.
  • Content-rule records, decisions, restricted files, appeals and report protection records are kept as part of the Trust & Safety record while it is needed to review a decision and recognise a repeated ground, and lose their link to your account when you delete it. The kept text of a request in a child-safety case stays only with that case and its legal hold.
  • Acceptance and age records are kept for as long as your account exists and are deleted with it.
  • Legal holds. When a court order, a request from a competent authority, a legal claim, an investigation or a legal duty requires it, we can keep specific files, reports and the records describing them past the deletion described in this section — including after you delete them or your account — for as long as that reason stands. Each hold is limited to what the reason concerns, is reviewed at least every 90 days, and does not make anything visible to anyone; once it ends, its files are deleted under the normal rules.
  • Publications stay public until you withdraw them, we remove them, or your account is deleted. A plan ending, or your private library passing its retention period, does not remove them: the files a live publication shows are kept for it. After a withdrawal or removal, the record of what was published and when it ended is kept for as long as your account exists, as evidence of your consent and of its withdrawal; the files are deleted once nothing else uses them.

Higgsfield's retention is separate. Its standard API terms allow request parameters and output metadata to be kept while the API account remains active. Generated media is available for at least seven days and may be deleted by Higgsfield after that period; this is not a promise that all copies are erased on day seven. Deleting an item or your account on Visxy does not itself erase the provider's records. An exclusion from model training does not mean zero retention. Contact support@visxy.com for a request concerning data sent through Visxy; we handle it under Section 8, including any applicable legal retention exceptions.

AI Tools data (Section 2.9) is retained as follows:

  • Nothing at all for a tool that runs in your browser. There is no record to retain, because the content never reaches us.
  • Daily usage counts hold a tool, a date and a number, with no user identifier. They are aggregate statistics rather than personal data, and are kept for as long as they are useful for deciding which tools to keep.
  • Free-allowance counters are day-scoped and cleaned up regularly. A guest counter uses a pseudonymous browser identifier; it is not necessarily anonymous personal data.
  • Server text-tool responses are returned to you without being saved in the Generator library. Paid requests retain job and credit-ledger records; free requests retain allowance counters. Image and video paths that save media follow the AI Generator rules above. Providers may retain request data under their own applicable policies.
  • Preferences stored in your browser are not retained by us at all, because we never receive them. They persist until you clear your browser's site data.

Creator Partnership data (Section 2.10) is retained as follows:

  • Per-device referral records are kept only while the 30-day referral window is open, then deleted; only an anonymous daily count remains. A referral linked to an account keeps the device identifier only while it is open. After that it is kept without it, as the record of which partner the account came through, together with any commission it produced.
  • Devices a partner used on their own link are kept for 180 days after last use.
  • Daily traffic counts hold a partner, a date and numbers, with no visitor identifier, and are kept for as long as the partnership's statistics are useful.
  • Commissions, the balance ledger and partnership records are kept for as long as the Program runs, including after a partnership ends, as the record behind every balance. If a partner's account is deleted, these records are kept with the account identifier removed, for the same accounting and dispute reasons as refund records below.
  • Applications are kept for as long as the account exists. If the account is deleted, the application is kept with the name, links, promotion text, notes and reasons removed, so that only the channel type, audience band, country, decision and dates remain for statistics.

Email subscription data (Section 2.11) is retained as follows:

  • Your subscription and the record of your consent are kept for as long as you hold an account, and for as long as the consent could need to be evidenced after you withdraw it. We retain the evidence needed to demonstrate permission and honour objections under applicable law; withdrawing consent stops marketing but does not necessarily erase evidence of earlier permission.
  • A subscription with no account is kept while you are subscribed. After you unsubscribe we keep the record of your consent and its withdrawal, for the reason above. Delivery and suppression records follow the separate rules below. Scheduled cleanup deletes an unconfirmed address after its confirmation link expires.
  • Per-recipient delivery records of newsletters and announcements, with their delivery and engagement events (delivered, delayed, bounced, complained, opened, clicked), are kept for 24 months from the day the campaign began sending. After that we remove your address, the delivery provider's identifiers and the link to your account or subscription, and the events lose their detail; only each record's outcome and date remain, in totals that identify nobody.
  • The send log — one line for each email we send you or try to, service or marketing: the address, the kind of email and whether it went out, failed or was not sent (for example because the address was not confirmed) — is kept for 24 months, then deleted.
  • Suppression records — an address that hard-bounced or reported us as spam — are kept indefinitely, on purpose. The whole point of the list is that we send that address no further marketing or broadcast email, and deleting the record would defeat it. It holds the address and the reason, nothing else.
  • Deleting your account turns marketing email off, removes your subscription — including one made without an account at the address your account confirmed — and your per-recipient delivery records, and leaves aggregate campaign totals that identify nobody. A suppression record survives, for the reason above.

Refund and dispute records (Section 2.3) are transaction records. They are retained under the legal, accounting and fraud-prevention exception above, which means they can outlive the account itself — with the account identifier removed where we no longer need it — because tax and commercial law require a seller to be able to evidence a sale and its reversal for a fixed number of years.

Account enforcement records (Section 2.8) are kept for as long as the account exists. Where a suspension relates to a dispute, a complaint, a payment chargeback, or a report we are required to make, the record is kept for as long as we need it for that purpose, without treating suspension itself as a reason to refuse erasure of unrelated data (Section 7).

Instagram comment, identifier and reply records are retained for comment management, deduplication and troubleshooting only as long as those purposes require. We do not currently collect automated DM delivery records.

7. Account Suspension, Deletion & Email Changes

7.1 Suspension

  • We may suspend an account in the circumstances set out in the Terms of Service, Section 11.2. A suspension blocks sign-in and deletes nothing — your account, content, purchases, and records stay exactly as they were.
  • You are told the reason. Because a suspended account cannot read anything inside the Service, we also send the reason to the email address on the account.
  • A person makes the decision and a person reviews it if you contest it at support@visxy.com (see Section 3.2).
  • What we record about a suspension, and for how long, is described in Sections 2.8 and 6.

7.2 Deletion

  • You can request deletion from account settings where self-service deletion is available, or contact support@visxy.com, including if you cannot sign in.
  • Deletion is scheduled 21 days ahead by default. Nothing is removed during that period and your account keeps working normally, so you can sign in and choose Keep my account at any point to cancel it. This window exists to protect you against an accidental or unauthorised deletion — it is not a delay we impose on your rights.
  • If you want your data erased without waiting, tick Delete without the 21-day recovery window when you confirm. We then delete on the next scheduled run.
  • When deletion runs, we permanently remove your profile, favorites, collections, copy and like history, license records, generated media, uploaded reference files, how you organised your Generator work and the Visxy items you saved (Section 2.5), your member support requests and their messages, history and notification records, and your publications and public profile. Where someone else's publication reused an input of yours, that input is removed from it too and shown there as no longer available. Records we must keep for accounting, tax, or fraud-prevention reasons — what was purchased and when — are kept with your identity removed, as described in Section 6. Backups and separate guest or email correspondence follow the rules there.
  • Subject to any refund or other mandatory rights, unused AI Generator credits are forfeited when deletion completes. Requesting deletion marks an active Generator plan to end in Visxy at the end of its current period. Cancel billing managed by a seller or app store through that channel (see the Terms of Service).
  • Content you authored and that we published — prompts or articles — is transferred to a Visxy-operated profile rather than removed, so that the public library is not broken by an account closing. This does not apply to generations you published yourself, which are removed as described above.
  • Creator Partnership accounts have self-service restrictions while the partnership is active or suspended or a balance remains. Contact support to resolve the partnership and request erasure. These product restrictions do not remove statutory privacy rights or justify retaining unrelated data. Following deletion, partnership records are handled as described in Section 6.
  • Owners of active Business workspaces must transfer ownership to an active member or start closing the workspace before using self-service deletion. You can still contact us to make an erasure request.
  • Suspended accounts cannot use self-service deletion. Contact support for erasure. We assess each request and may retain specific records where a legal obligation or a necessary legal-claims exception applies; suspension alone does not justify refusing the whole request. We explain any restriction and erase data for which no valid retention reason remains.

7.3 Email changes

  • You may change your account email address at any time. For your security, this requires confirmation via links sent to both your old and new email addresses.

8. Your Rights

Your rights depend on the law that applies. They may include access, correction, erasure, restriction, portability, objection and withdrawal of consent. To make a request, email support@visxy.com or write to the address in Section 13. You do not need access to your account. We may ask for proportionate information to verify that the request is yours.

  • EEA and UK: where the GDPR or UK GDPR applies, we normally respond within one month. An extension of up to two further months is available only where the law permits it; we explain it within the initial month. Requests are normally free; refusal or a reasonable fee requires the applicable legal grounds, such as a manifestly unfounded or excessive request. You may complain directly to your competent EEA supervisory authority or the UK Information Commissioner.
  • Türkiye: where KVKK applies, Article 11 includes rights to learn whether and why data is processed, learn recipients, seek correction or erasure where its conditions are met, seek notification to recipients, object to an adverse result based solely on automated analysis, and seek compensation for unlawful processing. We respond as soon as possible and within 30 days. Any fee must follow the applicable statutory tariff; the GDPR extension and fee rules do not apply automatically. A complaint to the Personal Data Protection Board requires first applying to the controller. If the reply is rejected, insufficient or absent, the complaint deadline is generally 30 days from learning the reply and in any event 60 days from the original application.
  • Other jurisdictions: applicable local rights, deadlines and appeal routes remain available. Contact us to exercise them; these examples do not restrict them.

Account deletion is an erasure request. The 21-day recovery window runs within the applicable response period, not on top of it. You can waive the window in the deletion flow or request erasure through support. An account restriction, suspension or partnership balance is not itself a legal exception to erasure.

If we restrict or refuse any part of a request, we explain the legal basis and complaint route. We retain only the data needed for the justified purpose and coordinate with relevant processors where necessary.

Where the GDPR or UK GDPR applies, you can object to direct marketing at any time. Use the unsubscribe link in a marketing email or contact us using the details above.

We do not sell or share personal information for cross-context behavioural advertising as those terms are used in the CCPA and similar laws. Direct sponsored placements disclose no visitor information to sponsors. If this changes, we will update the notice and provide any required opt-out mechanism before the new processing starts.

9. Children’s Privacy

The Service is for adults: you must be 18 or older to use it (Terms of Service, Section 3). We do not knowingly collect personal information from anyone under 18. If you believe someone under 18 has given us personal information, please contact us so we can remove it.

10. Data Security

We implement technical and organizational measures appropriate to the risk, including:

  • Access controls limit who can view account data, with access for authorised service administration and sharing you choose. Section 3.3 explains administrator access.
  • Private media storage keeps generated media and reference files out of the public gallery unless you choose to share or publish them.
  • Encryption in transit, throughout the Service and to every provider listed in Section 5.
  • Data minimisation for error reports shared with our monitoring provider (Section 5).

No method of transmission or storage is completely secure, and we cannot guarantee absolute security. If a breach affects your personal data and is likely to result in a risk to your rights, we will notify the competent supervisory authority and, where the law requires it, you — without undue delay.

11. International Data Transfers

Visxy is operated from Türkiye and uses international infrastructure. The providers in Section 5 may process data outside your country, including in the United States and other locations used by their hosting services and subprocessors. This includes account and storage services, AI inference (and upstream model vendors used by resellers), email delivery, hosting, security, analytics and social integrations.

Transfers must meet the rules that apply to the particular data flow. Where the GDPR or UK GDPR applies, this may require an adequacy decision or safeguards such as the applicable standard contractual clauses and additional measures. A provider policy or a generic claim of compliance alone does not establish a lawful transfer.

For transfers subject to KVKK, Article 9 requires a separate applicable mechanism. An EU agreement or a provider DPA does not automatically satisfy it. Where Turkish standard contracts are used, the applicable signing and notification requirements also apply.

Contact support@visxy.com for information about the destinations and safeguards applicable to your data, and a copy of relevant safeguards where available and required. Acknowledging this notice or using the Service is not consent to restricted transfers and does not replace a required transfer mechanism.

12. Changes to This Policy

We may update this notice as the Service or our processing changes. We update the date and bring material changes to your attention: account holders by email or by a prominent notice in the Service, subscribers without an account in the next newsletter we send them, and a suspended account when it is reinstated. If a change requires new consent, we ask for it before the relevant processing; continued use is not that consent.

13. Contact

Data controller: Murat Dinç, operating as Visxy.

Email: support@visxy.com

Correspondence address: Hamidiye Mah., Sanayi Sit., 15029 D:24-A, 10300 Edremit, Balıkesir, Türkiye.