📈 Invista — Terms of Use and Privacy Policy

Version of September 9, 2026 · invista.powerguido.pro · previous versions

Terms of Use

1. What the platform is

Invista is a tool for tracking of investments: it consolidates public market data (B3, CVM, Banco Central and quote providers), tracks the portfolios you register, calculates returns and provides an estimate of taxes on exchange-traded transactions.

2. What the platform is NOT

Nothing here is investment advice. Scores, rankings, reference prices (Bazin, Graham), rebalancing suggestions and AI assessments are methodological references calculated from public data, with assumptions displayed on screen. The decision to buy, hold or sell is entirely yours. Tax calculations are supporting estimates: check the amounts with your accountant before paying DARF or filing income tax returns.

3. Data accuracy

Data comes from external and free sources, which may contain errors, delays or gaps. The platform runs verification routines, but does not guarantee the accuracy of quotes, distributions or metrics. In case of a discrepancy, the official source prevails (B3, CVM, your broker).

4. Your account

Privacy Policy (LGPD)

5. Who processes the data and how to contact us

The controller is Rafael Gili, responsible for the Invista platform (invista.powerguido.pro). Contact for personal data matters: privacidade@powerguido.pro (you can also reply to any email sent by the platform). Requests concerning your data are answered within 15 days; when a complete response requires more extensive research, within 30 days (the deadline for small processing agents under CD/ANPD Resolution No. 2/2022), always acknowledging receipt beforehand. The platform operates as a small processing agent and maintains this channel instead of an appointed data protection officer, as permitted by that resolution.

6. What data is collected and why

7. Who handles the data

We do not sell data or share it with third parties for their own purposes. To operate, the service uses:

8. Isolation and security

Passwords are stored using strong hashing (argon2). Portfolio data is isolated by user at database level (row-level security), so each account holder accesses their own portfolios. Administrative support has read-only access to distribution reconciliation diagnostics, including the trades and receipts involved, to investigate inconsistencies. This permission does not allow general browsing of other users' portfolios. Administrative account actions are logged; administrative password resets trigger an email notice to the account holder. All traffic uses HTTPS.

9. Retention and deletion

Your data is stored while the account exists. Additional retention periods have automatic rules by category:

Unverified accounts, sessions, notifications and audit records are purged weekly: automatic deletion may occur up to 7 days after the stated retention threshold. Backups, access logs and statistics follow their specific cycles above.

When you delete your account (profile → Delete account), your account and portfolio data is removed from the database immediately. A minimal service record remains (internal identifier and date), subject to audit retention. An internal identifier does not guarantee anonymization while association remains possible; remaining backups and access logs follow their respective retention periods.

10. Your rights

Access and portability: the "Download my data" button in your profile — a file containing everything the system stores about you and your portfolios, available to every account regardless of plan or module. Correction: through the platform itself (profile and portfolio). Erasure: through self-service account deletion. Other LGPD rights (information about processing, review, objection): through the channel in section 5, within the deadlines stated there.

11. Changes

Significant changes to this text create a new dated version on this page, and the platform requests your acceptance again on your first access after publication — use is not treated as implied agreement. Your acceptance history is recorded with the date and version.

Version history

← Back to the platform