dmscs is a private, invite-only portfolio analysis tool run by an individual, not a company. This page explains what it stores about you, who can see it and how to have it deleted.
What is stored
- Your sign-in identity. When you sign in with Google, dmscs receives your name, email address and Google's account identifier. It never sees or stores your Google password.
- Your portfolio data. The accounts, holdings, cost basis, transactions, income and planning inputs you enter or import.
- Linked financial accounts, if you choose to link any. Connections go through Plaid. You give your bank or brokerage login to Plaid, never to dmscs. dmscs stores the access token Plaid issues, encrypted, the balances and holdings it retrieves, and the identifiers, dates and quantities of recent trades, kept only to keep those holdings in step.
- Security records. Your sign-in sessions, with the IP address and browser each one started from, and the service's logs of requests (the time, IP address and page or data asked for) and errors. Logs are kept for 90 days and used only to run and secure the service.
- Activity records. Which parts of the app you open, which features you use, minutes you were using the app, per day, and when you last signed in. Never what you entered. Details under Activity in the app.
- Bug reports you send. What you write, plus details that help fix the problem: where you were in the app, your recent requests and errors, your display settings, your browser and the app version, and counts such as how many accounts and holdings you have. A report never includes balances, amounts, account names or numbers, or your email address, and you can see exactly what will be sent before you send it.
Activity in the app
dmscs records how invited people use the app, so it can see which parts are useful, where people get stuck and what to improve. For each person, for each day, it records:
- which parts of the app you open (tabs and views);
- which features you use, for example adding an account, refreshing prices, running a forecast or exporting a table. Use is counted, such as "added an account twice", not what was added;
- how many minutes you were using the app: open in front of you, with a key press, tap or mouse movement in the last minute (the minutes are counted, not what you did);
- when you last signed in.
It does not record amounts, balances, holdings or ticker symbols, account names, anything you type, or your clicks or scrolling. None of it is sent to a third-party analytics service.
Each person's daily records are deleted after 180 days. When you last signed in is kept with your account. The daily totals across everyone, which hold no per-person figures, are kept.
How it is used
To show you your own portfolio analysis, to run and secure the service, and to understand how the app is used (see Activity in the app). Your data is not sold, rented, used for advertising or shared with anyone for their own purposes.
Who can see it
Your portfolio data is visible only to you, inside the app. Each person's data is kept separate from everyone else's. The operator has administrative access to the database to run and repair the service, and does not look at your portfolio data except to fix a problem you report or when required by law.
The operator gets a daily summary of activity totals across everyone: how many people were active, the minutes spent, which features were used and how many accounts were added. The summary leaves out per-person detail. Your own daily activity records are kept so the operator can follow up with people about how setup is going.
Services involved
- Google confirms your identity when you sign in.
- Cloudflare delivers and protects traffic to the app and this site, and keeps its own records of access checks.
- Amazon Web Services hosts the app and its encrypted database in the United States.
- Plaid connects financial accounts, only if you link one.
- GitHub stores the bug reports you send, privately, so they can be tracked and fixed.
- Market data sources (Yahoo Finance, OpenFIGI, SEC EDGAR, fund issuers' websites) receive the ticker symbols and security identifiers needed to look up prices and fund contents. These requests never include your name, email, amounts or account details. Company logos are fetched from Google's favicon service by the company's website address.
Market data the app keeps (prices, fund contents, analyst estimates) is shared across users, but it contains only public facts about securities.
Security
Traffic is encrypted in transit. The database and backups are encrypted at rest, and linked-account tokens are encrypted separately. Access requires an invitation and a sign-in. The security page has more.
Invite requests
If you ask for an invite on the request page, the only thing you give is an email address. It is sent to the owner as an email and is not stored on this site.
- Where it goes: the request is checked and forwarded by email to the operator, through Cloudflare. Logs record only whether a request was accepted or refused, never the address.
- The bot check: the form uses Cloudflare Turnstile to tell people from bots. It looks at signals from your browser while the page is open; it sets no advertising cookies and isn't used to track you across sites.
- On your device: after you send it, your browser keeps the address for ten minutes so the confirmation page can show it back to you. Only that page can read it.
- What it's used for: only to decide on and send an invite, and to reply to you.
- How long: until you're invited, when the request becomes your invite, or for at most 12 months, after which it is deleted.
- Deleting it sooner: email [email protected] and ask.
Keeping and deleting your data
Your data is kept while you have an account. Email [email protected] to get an export or to have everything deleted. Deletion removes your data, including your activity records, and disconnects any linked accounts at Plaid. Copies in encrypted backups are not edited; they are deleted when those backups expire.
Changes
If this policy changes in a way that affects you, invited users will be told before the change takes effect.