PRIVACY

Privacy notice

Current status: figures entered in the free calculator stay in the browser and are not sent to Wosavest. Saved accounts are an invitation-only private beta. The service does not accept payments, show advertising, use behavioral analytics or send marketing email.

Who operates Wosavest

Wosavest is operated by Vedast Sanxis, based in the Philippines. For privacy questions or requests about your personal information, contact privacy@wosavest.com. Account-related email is sent from accounts@wosavest.com.

Information stored in readable form

The service stores an account email address, beta access status, account dates, access timestamps and security-related request metadata. Hosting infrastructure may process IP addresses and browser information in ordinary server logs.

Account email and verification

Public registration is currently closed. The administrator account was created during installation without email verification. Wosavest now uses Hostinger email over an authenticated, encrypted SMTP connection for account messages. A delivery test does not verify an account or open registration.

When public registration is enabled, a new user must enter a six-digit code sent to their email address in the same browser where registration began. The code expires after ten minutes, allows up to five verification attempts and is replaced by a new code request. The application keeps the email address, a keyed digest of the code, its expiry and an attempt counter in the requesting server session. It does not store the code in plaintext there. Successful registration consumes the challenge. Expired challenges cannot be used; expiry is not a promise that the session file or a delivered email has already been deleted.

Hostinger processes the recipient address, delivery metadata and message contents to send account email. These messages contain no financial plan, password or bank credentials. Messages you send to our contact mailboxes are also processed by Hostinger and can be read by the operator to handle your request. Please do not email passwords, verification codes, recovery codes or bank credentials.

Encrypted financial information

Financial profiles, countries, currencies, assets, debts, balances, tax assumptions, categories, transactions, scenarios and work-time calculations are encrypted in the browser before the plan is uploaded. The server stores an encrypted copy of the plan and the technical information needed to save and open it. Market lookups and optional bank or broker connections process some information separately, as described below. The protection and its limitations are explained in the security page.

Why readable account data is used

Readable account data is used to authenticate users, prevent abuse, provide encrypted synchronization and operate the beta. It is not used to profile financial behavior. Saving or opening the encrypted plan does not send its readable contents to the server. If you request a bank or broker report, its financial records pass through the server before reaching your browser for review.

Sharing and service providers

Hostinger provides the website hosting and account email infrastructure. Its hosting infrastructure processes the data needed to deliver requests and store encrypted plans. The beta does not use a payment provider, advertising network, remote analytics service or email-marketing service. Encrypted plans may appear in hosting backups but remain encrypted.

If you ask the account to identify a listed investment or update its closing price, the browser sends the server only the ticker, ISIN or investment name, the relevant exchange identifier, the confirmed quote unit, and the listing and main currencies needed for the lookup and conversion. Marketstack, the configured closing-price provider, receives the search term or public symbol and exchange needed to answer the request. For supported listings, the server also retrieves public prices from Yahoo Finance, Moscow Exchange and SIX. Cryptocurrency references use Coinbase or CoinGecko. These requests use public instrument or currency identifiers. None of these price providers receives the number of units you own, balances, purchase costs, transactions, bank or broker account details, email address or other contents of the encrypted plan. The installation keeps a shared cache of public symbols, exchange identifiers and closing-price responses so the same successful market listing is not requested again during its daily market cycle. A listing-specific empty or invalid response is also held until the next market cycle. Temporary provider failures instead trigger a shared backoff and can be tried again after that pause. A local safety counter stops new provider units before this installation exceeds the allowance chosen by the site owner for that UTC month, but it cannot see earlier or external use of the same provider account. Exact site-wide usage is shown only to the site owner. These cache and counter entries are not linked to a user, institution, quantity or portfolio. Recently requested public listing identifiers can also be refreshed by a scheduled hosting task while the application is closed. This shared demand expires 45 days after the last foreground price request; background updates do not extend it. The scheduled task uses the same provider allowance and never reads or changes encrypted plans. On first activation, public quotes cached within the preceding 45 days can enter the queue with their original expiry. Currency conversion uses general reference-rate data from the European Central Bank and, for supported ruble conversions, the Bank of Russia. These requests do not send personal financial information.

Geographic information is checked automatically when you open your plan. To identify a company’s country, the browser sends the server its public company name, ticker or ISIN. The server first checks the bundled GLEIF company directory and reviewed issuer references. If those do not resolve the company, it may query Wikidata with those public identifiers. It does not send quantities, values, costs, transactions, institution or account details, or your email. An unambiguous match is saved in your encrypted plan with its source. Missing or ambiguous information stays Unclassified. Public company results are shared for 30 days; unsuccessful searches are cached for seven days. Wikidata structured data is available under CC0.

For supported funds, the server uses the public fund identifier and listing to obtain dated country data from iShares/BlackRock, State Street or Vanguard. Fund identifiers are shared; your holdings and account information are not. Successful allocations are cached across the installation for 24 hours per fund. The encrypted plan records the allocation, source and date and checks for updates on a later visit. Manually entered allocations are preserved. When a source is unavailable, the last successful information is kept.

The closing-price dialog lets you control automatic updates. For investments with updates enabled, opening your plan retrieves the shared closing prices and may start a check after the relevant cache has expired. The interface reports whether the background task has run recently. Your encrypted plan receives any new eligible valuations only after you open and unlock it. Opening an older plan may also retrieve a missing price for a supported Bitcoin investment, unless you have explicitly switched automatic updates off. This repairs the missing valuation without enabling ongoing updates or replacing a saved manual or broker valuation. Manual prices are not automatically updated.

Optional bank and broker connections

Interactive Brokers: when you request a Flex report, your reporting token and Query ID are sent through our server to Interactive Brokers. The returned report can contain account identifiers, balances, holdings and transactions. It passes through the server to your browser, where you review the changes before adding them to your encrypted plan. The connection requests reporting access only and does not ask for your IB password or provide trading actions.

Banks: where activated, connections use Enable Banking. You choose a supported bank and authorize access through the provider and bank. The service exchanges the authorization response and requests the account information you permitted. Bank account details, balances and booked transactions pass through our server to your browser. Bank sign-in takes place outside Wosavest. The connection provides account information only, with no payment actions.

The connection code processes tokens and downloaded reports temporarily; it does not save plaintext credentials or raw report copies to the application database, files or application logs. IB tokens are remembered only if you select that option, inside your encrypted plan. Bank connection references are protected and stored with your encrypted plan. Readable exports remove those access credentials. Password-protected backups can contain them. Interactive Brokers, Enable Banking and the selected bank process requests under their own privacy and retention terms.

Retention and deletion

Deleting an account removes its user record and encrypted plan from the active database. Hosting backups run weekly and may retain account records and encrypted plans after deletion from the active database. Hostinger's published hosting agreement describes two weeks of backup history. Existing copies rotate under the provider's schedule; deleting an account does not immediately erase them. Operational rate-limit records contain hashed request buckets rather than financial data. Shared public market-cache entries are not linked to an account or portfolio and are therefore not removed when one account is deleted. Removing a saved connection does not delete records held by the bank or broker. You can revoke its authorization with that provider.

Privacy questions and requests

Contact privacy@wosavest.com to request access to, correction of or deletion of your account information, or to raise a privacy concern. Include the email address associated with your account and describe your request. We may need to verify control of that address before changing or disclosing account information. The operator cannot decrypt your stored financial plan on your behalf; the export and deletion controls below work from your account.

Your controls

You can export a readable copy, create a separate password-encrypted backup, restore a compatible backup, optionally create or replace an emergency recovery code, sign out and delete the account. Without Remember me, your financial information is hidden after two hours without activity. Remember me keeps access on this browser for up to 30 days, including after closing it. This stores a secure device cookie and encrypted unlock material in browser storage; the server stores a hash of the device token and its expiry. Signing out or turning Remember me off removes remembered access for this browser. A readable export is no longer protected by the application's encryption. Keep exports, backup passwords and any recovery code somewhere safe.

Children

The beta is intended for adults managing their finances and is not directed to children.

Before public or paid registration

No paid plan is offered under this notice. Before accepting payment or opening registration generally, the remaining launch information must be completed, including applicable processing bases, hosting and email processing locations and international transfers, specific retention schedules for server sessions, logs and mailboxes, and any additional required operator contact details. Payment-related processing and commercial terms must be published before a paid service is offered. New accounts will also require email verification. Those details will not be presented as complete before they exist.