Privacy Policy
This Policy explains how Strum collects, uses, stores and protects personal data of users of the investment, capital, budgeting, goals and analytics service.
Service operator
FOP Yutysh Oleksandr
7B Levka Lukyanenka Street, Apt. 11, Kyiv, 04212, Ukraine
Privacy contact: strum.yuinvest@gmail.com
1. Who is responsible for data processing
FOP Yutysh Oleksandr operates Strum and acts as the controller of personal data under this Policy.
Registered address: 7B Levka Lukyanenka Street, Apt. 11, Kyiv, 04212, Ukraine. For privacy requests or data deletion, contact strum.yuinvest@gmail.com.
2. Data we process
- Account data: email, name and other profile details provided by the user.
- Authentication and security data: sessions, technical tokens, login events and bot-protection checks.
- Financial and portfolio data entered or imported by the user: assets, transactions, goals, budgets, notes, broker reports and related calculations.
- Payment and billing data needed for card verification, trials, subscriptions, recurring charges or refunds. This may include a payment token, masked card number, card type, payment provider, transaction identifiers, statuses and amounts. Strum does not receive or store the full card number or CVV.
- Technical data: IP address, device type, browser, language, pages, error events and service logs.
- Support communications: messages, requests, replies and other information voluntarily provided by the user in the website chat or the Telegram support bot. When a user writes on Telegram, we receive their Telegram name and username, and their email if they provide it.
3. Cookies, analytics and marketing tags
Strum uses necessary technical storage for site operation, authentication, security and remembering the user cookie choice.
Google Tag Manager, Google Analytics, Microsoft Clarity and Meta Pixel load only after the user grants consent in the cookie banner. If consent is rejected, these tags do not load and known analytics cookies are cleared where technically possible.
- Google Analytics through Google Tag Manager helps measure page views, traffic sources, basic conversion events and technical visit parameters.
- Microsoft Clarity may be used to diagnose site interactions, clicks, scrolling, UX issues and de-identified session insights.
- Meta Pixel may be used to measure ad performance, registration or navigation events, and to build Meta audiences where the user has consented.
- Known cookies from these tools may include
_ga,_ga_*,_gid,_fbp,_fbc,_clckand_clsk. - The HelpCrunch support chat is a necessary tool and loads without analytics consent. It stores technical chat-session data in the browser so a conversation is not lost between pages.
- Consent is stored in the browser localStorage as
strum_tracking_consent_v1. The user can change the choice through the Cookies button on the site or by clearing browser data.
4. Why we use data
- To provide Strum, synchronize data and calculate portfolio, budgeting, goal and analytics views.
- To manage accounts, verify eligibility for the one-time 7-day trial, confirm a payment method, and process subscriptions, automatic renewals, payments, cancellations, refunds and support requests.
- To maintain security, prevent abuse, fix errors and keep the service stable.
- To improve product quality, UX, speed, content and marketing campaigns based on aggregated or de-identified data.
- To comply with legal, accounting, tax and regulatory obligations.
5. Legal bases
We process data to perform the agreement with the user, comply with legal obligations, protect Strum legitimate interests and rely on consent for optional analytics or marketing tags.
6. Who may receive data
We use providers needed to operate the service, including Supabase for database and authentication; plata by mono (monobank internet acquiring) for new subscriptions and card verification; WayForPay for subscriptions and payment methods created earlier; Google, Microsoft Clarity and Meta for analytics or marketing after consent; and hosting, communication and support tools.
The payment provider processes card credentials and returns a tokenized payment-method identifier and limited service data to Strum. Strum uses this information to start a trial, renew a subscription automatically, display a masked card, process payments, cancellations and refunds, and prevent abuse.
AI import
When you use AI import, Strum uses Anthropic's Claude API to interpret your request and prepare proposed transactions. We send the messages and attachments you submit, or their parsed contents, together with financial context needed for the request. This may include names of your portfolios and budget accounts, holdings, transactions, draft statement rows and previous proposals. Relevant information from your other portfolios or accounts may be included for comparisons. Financial changes are saved only after you confirm them.
Anthropic processes this data under its commercial API terms. Its published defaults are not to use API inputs and outputs to train models and to delete them within 30 days, subject to agreed terms and legal or abuse-prevention exceptions. See Anthropic's data retention and model training policies.
Strum stores your import conversation, uploaded sources and proposal snapshots so you can review a change, retry it or return to the chat. The conversation expires seven days after it starts. The existing cleanup process removes its messages, sources and proposals. Removing a chat from your history hides it immediately. Saved financial transactions and import or Undo receipts may remain longer under this Policy.
Support chat
We use HelpCrunch for the website chat and the Telegram support bot. When a signed-in user opens the chat, Strum sends HelpCrunch the account identifier, email, name and plan details (name, status, end date and payment channel), so we can see who is writing and reply faster. If a user gives an email in the Telegram bot, we match it to a Strum account and send HelpCrunch the same plan details. Messages sent through Telegram are also processed by Telegram under its own privacy policy.
We do not sell users personal financial data. Data is shared with third parties only to operate the service, comply with law, protect rights or with user consent.
Connected applications and MCP
When you connect an external app through the Model Context Protocol (MCP), Strum shows the app’s name. By default, the app can read your financial data. Write lets it add and edit transactions in the accounts and portfolios you select. Delete lets it remove them. You choose these permissions when you connect the app or later under AI apps (MCP) in Strum settings.
Before each direct deletion, the app shows the affected transactions, asks you to confirm in chat and relays your answer to Strum. Saving or undoing an import batch requires separate confirmation in Strum. Strum keeps a receipt of completed changes. Your conversation with the external app stays with that app.
Authorized applications can be reviewed and disconnected in account settings. Disconnecting an application revokes its active OAuth sessions and refresh tokens. Strum records limited MCP security activity, including the OAuth client identifier, tool name, time, status and duration, for up to 90 days. Strum does not store OAuth access or refresh tokens in these activity records.
7. Storage, security and retention
Data is stored as long as needed to provide the service, comply with legal obligations, resolve disputes, maintain security and keep accounting records. The user can delete the account through the deletion button in the service or contact us about specific data.
After deletion starts, Supabase removes the email from the user auth record, and Strum account data is anonymized. Some records can remain in the production database for a limited period until full deletion by a scheduled cron job, and in backups until the backup retention period ends.
We apply technical and organizational security measures, but no internet service can guarantee absolute protection against every risk.
8. User rights
- Access personal data.
- Correct inaccurate or incomplete data.
- Request deletion or restriction of processing.
- Withdraw consent for optional cookies and marketing tags.
- Export data where technically possible.
- File a complaint with a competent data protection authority.
9. Changes to this Policy
We may update this Policy when the service, law, providers or data processing practices change. The current version is always available on this page.