Privacy policy

What is stored

• Account data: name, email, avatar, technical Google sign-in data, and service data for one-time email codes.
• Bank connection: encrypted token, token last characters, profile name, and number of detected accounts.
• Bank data for calculations: transactions are stored encrypted and are not stored in plain form.
• User settings: date format, selected community for tax payment accounts, and reminder settings.
• Billing data: customer, subscription, and transaction identifiers, payment statuses, refund requests, and links to billing documents if the payment provider provides them.

What is not stored in plain form

MYFOP UA does not store bank transaction history in plain form. Bank data is used to calculate income, taxes, and deadlines in the user's workspace.

The service does not store payment card data and does not execute payments from your bank accounts.

Why data is used

• To authenticate the user and show the workspace.
• To verify bank connection and collect income for calculation.
• To show taxes, deadlines, payment accounts, and reminders.
• To grant or end paid access according to subscription status.

Services involved

The product may use Google Sign-In, Mailgun, Vercel, Neon PostgreSQL, bank integrations for statements, Telegram, and Monobank for payments.

Payment card data is processed by the payment provider. MYFOP UA receives payment, subscription, and refund statuses, but not the card number.

Data requests

Requests to access, change, or delete your data can be sent to contact@myfop.com.ua.