How Studio handles your data.

What is processed

Depending on the tool, the request may contain your idea, Pine Script or Python, TradingView List of Trades CSV rows, visual-behavior notes, validation settings, chronological trade returns, a client-managed strategy ID, a research ledger, and an approved blueprint hash. This content is held in request memory long enough to produce the result. The full research ledger is returned to the client rather than automatically retained. A separate optional memory tool can save selected summaries with your explicit consent.

Optional preferences and project memory

Memory is off by default. The optional memory permission is separate from research permissions and is unchecked during consent. Permission alone does not enable storage. When you explicitly enable it, PrimeSync can remember language, explanation depth, experience, preferred markets/timeframes/sessions/timezone, output language, execution and risk preferences, evaluation objective or balance, response length, and code-comment detail.

Only project summaries you specifically request are saved: title, mode, confirmed rule summaries, assumptions, objective, code version and fingerprints, user-reported evidence references, rejected-experiment summaries, and next step. Never paste code, CSV rows, complete conversations, credentials, or financial account details into memory fields. Research calls do not automatically copy their contents into memory.

Records belong to your verified sign-in identity, not a user ID supplied in tool arguments. Shared reviewer accounts cannot save personal memory. Current requests override saved preferences; inferred preferences remain provisional. Your chosen AI client still controls the wording of its answers.

Saved preferences and summaries remain until you reset or delete them. Resetting preferences keeps projects. Turning memory off or deleting all memory erases both. Export, reset, disable, and per-project deletion are available in Account; you can also correct or delete information through the separately named memory tools. Revoking one OAuth connection stops that connection but does not erase account-wide memory. Copies already exported or retained in AI conversations remain subject to their own providers’ policies.

What PrimeSync stores

• OAuth client name and registered redirect URI.
• Your Whop user identifier for the connection owner. Login cookies may contain your Whop name or email in encrypted form.
• Hashed authorization codes and tokens, approved scopes, creation, expiry, use, and revocation times.
• A one-way hash of the connecting IP for OAuth client-registration abuse prevention, retained for no more than 24 hours.
• For 30 days: tool name, required scope, client name, time, and status. The audit log does not store tool inputs, strategy code, CSV data, or tool outputs.

Usage and abuse controls

PrimeSync stores monthly question counts, purchased-credit balances, payment-event references used to prevent duplicate awards, and a server-generated guest identifier derived with a one-way keyed hash from connection and browser metadata. Client-supplied guest identifiers are not trusted as account identity.

Training and sharing

PrimeSync does not use Studio strategy inputs or outputs to train models and does not sell them. Your chosen MCP client still receives the conversation and tool result; that provider's own privacy and retention terms apply. Whop processes sign-in, and the hosting provider transports and runs requests.

First-party website statistics

When you allow statistics in Cookiebot, our first-party analytics records public page paths, referrer domains, country-level location, device category, and predefined button-click categories. It uses random browser and session identifiers, removes events older than 90 days during normal analytics operation, and does not store raw IP addresses, URL queries, form entries, or assistant conversations. Browser identifiers expire after 90 days; sessions expire after 30 minutes of inactivity. Withdrawing statistics consent stops collection and removes the browser identifiers. Reporting is private to the site owner.

Statistics storage details

These two first-party local-storage entries belong to the Statistics category. The traffic script is held back until Cookiebot permits Statistics and also checks consent before every event.

• ps_traffic_browser_v1: a random browser identifier used to count consenting visitors across visits, with a 90-day application expiry.
• ps_traffic_session_v1: a random session identifier, last activity time and referring website origin used to group consenting visits and attribute traffic sources. It expires in the application after 30 minutes of inactivity.

Local storage has no automatic browser expiry: expired entries are replaced on the next permitted statistics event. Rejecting or withdrawing Statistics removes both entries, including older entries left by a previous visit. Do Not Track and Global Privacy Control also prevent this collection.

Optional Whop marketing measurement

When you explicitly allow Marketing in Cookiebot, Studio loads Whop's website pixel for the PrimeSync AI Studio business to measure public page visits and marketing attribution. It remains off if you have not answered, decline Marketing, or use Do Not Track or Global Privacy Control. Statistics consent alone does not enable it.

Our integration sends page commands with public page paths, excluding query strings and fragments, and does not add purchase, signup or other conversion events. We disable the SDK's automatic form-identity capture, link decoration, cross-frame identification, URL-identity extraction and automatic page tracking. The pixel loads in the main page only after Marketing consent. Optional verification and fingerprint modules are blocked, and page payloads exclude form text, identity details, query strings, fragments and referrers. It is not loaded on account, sign-in, OAuth or API pages.

Whop may receive technical information such as IP address, browser and device information, cookies and local-storage identifiers. The vendor SDK supports a device fingerprint, but this integration blocks that module and excludes fingerprint values from page payloads. Its SDK may associate identifiers across subdomains. Known optional entries include _wuid, _wuid_link and _wfp; provider behavior and retention are described in Whop's privacy policy.

Use the cookie button to withdraw Marketing consent. This immediately blocks new tracking sends, clears known optional browser-tracking entries, and reloads the page to end the loaded SDK. Your current homepage brief is kept temporarily in this tab's session storage for the reload, then removed on recovery; unused recovery data expires after five minutes. Sign-in data is not cleared. If the browser cannot preserve your brief, you can copy or download it before reloading. Requests already sent cannot be retracted by removing a script; withdrawal does not erase information Whop already received. You can contact us or use Whop's privacy controls for data requests.

Website controls

Cookiebot manages consent choices on ai.primesync.me. Use the cookie button to reject, review or withdraw optional choices. First-party statistics remain off unless a consent response allows statistics, and stop when consent is withdrawn. Security, sign-in, consent and requested-service functions may still process the technical information needed to operate. Cloudflare provides hosting and human verification, UserWay provides the accessibility menu, and Whop handles sign-in and purchases and, only after Marketing consent, the Studio measurement described above. These providers may process technical information under their own privacy terms. The marketing website at primesync.me additionally uses preference-gated Weglot translation and marketing-gated Whop website tracking.

Website assistant and support

The website assistant is separate from Studio's MCP research tools. It processes questions you choose to send to provide an answer. The current Studio website assistant uses built-in guided responses on our hosting infrastructure; its question-answer route does not call an external generative-AI model. It uses the current question, not earlier conversation messages. This differs from using Studio through ChatGPT or Claude, where your selected AI provider receives your conversation and tool results under its own terms. PrimeSync does not use assistant questions to train models. Usage and abuse records described above are separate from the conversation content.

Submitting questions or support details is voluntary, but the requested service needs the relevant information to respond. Do not send passwords, API keys, payment-card details or unnecessary sensitive information. For support or accessibility requests, email [email protected] or use the main support form. The support privacy notice explains ticket storage, providers, retention and rights. A support request is not permission for unrelated promotional messages.

Retention and your choices

Saved preferences and project summaries stay until you delete them. Usage, credit, payment and account records are retained as needed to operate the service, maintain balances, prevent abuse, resolve disputes and meet legal obligations; they do not have the research-input or 30-day audit-log retention period. Contact us to request access, correction or deletion, subject to applicable law and necessary recordkeeping. Cookie withdrawal stops the optional collection for the categories you withdraw but does not delete account records or optional memory.

The main PrimeSync Privacy Policy also explains privacy rights, children's privacy, security and international processing. PrimeSync operates in Israel; providers may process data in other countries under applicable safeguards.

Operator and contact

PrimeSync AI Studio is published by PrimeSync Project and legally operated by נביה חיר in Israel. Privacy, access, and deletion requests can be sent to [email protected].

Purposes and privacy requests

We process service requests and account information to provide the features you request, verify access and maintain usage balances. Security and abuse-prevention records protect the service; payment records also support dispute handling and necessary legal recordkeeping. Optional statistics and marketing use the consent controls described above. Where applicable, processing relies on performance of the service agreement, legitimate interests in secure operation, legal obligations, or consent for optional processing.

Depending on applicable law, you may request access, correction, deletion, portability, restriction or objection by emailing [email protected]. We may need proportionate information to verify ownership before disclosing or changing account records. Never send passwords or tokens. Some records must remain for necessary accounting, security or legal reasons. You may also complain to the relevant privacy authority. Withdrawing optional consent does not undo prior lawful processing.

We update this page when our practices change and revise its date. See security details for current safeguards and limitations; no online service can promise absolute security.

Control and deletion

You can revoke a connection immediately from Account & activity. Expired audit metadata is deleted after 30 days during normal service operation. For an access or deletion request, contact [email protected]. The broader PrimeSync website policy remains available at primesync.me/privacy ↗.

Studio analysis accounting

For paid Studio access, we verify the signed-in Whop user's membership with Whop using read-only server credentials. We do not store the membership response or payment-card details. A separate accounting ledger stores the Whop user ID, month, tool name, job status, timestamps and a keyed request fingerprint used to avoid duplicate counts. It does not store strategy inputs, code, CSV data or analysis output. Monthly-allowance entries older than 90 days are removed when that account next submits an analytical job. Purchased-job accounting and payment references are retained to preserve carry-forward balances and prevent duplicate payment awards. Whop payment and refund notifications are signature-verified; only payment references, Whop user IDs, credited jobs, status and timestamps are stored, not full notifications or card details. This ledger is separate from the 30-day OAuth activity log and website question credits.