This Privacy Policy describes how smore ("the App," "we," "us," or "our") collects, uses, discloses, and retains information in connection with your use of the App and its associated server infrastructure (collectively, the "Services"). By accessing or using the Services, you acknowledge that you have read and understood this Privacy Policy.
The Services are intended for users located in the United States and are not directed to children under the age of thirteen (13). We do not knowingly collect personal information from children under 13. If we become aware that we have collected such information, we will delete it promptly.
1. Information We Collect
1.1 No Account Registration. The Services do not require the creation of an account and do not collect your name, email address, or password. Upon installation, the App generates a random device identifier ("Device ID"), which is stored in your device's secure keychain. The Device ID is transmitted with each request to our server to associate your linked financial institutions with your device, and is provided to Plaid as the user reference for each bank-linking session so that Plaid can attribute the resulting connection to your device. It is not disclosed to any other party. The Device ID does not identify you personally.
1.2 Financial Account Linking. Financial institutions are linked to the App through Plaid Inc. ("Plaid"). When you link an account, you provide your banking credentials directly to Plaid through Plaid's interface; we do not receive, transmit, or store your banking username or password at any time. Plaid provides us with an access token (the "Access Token") that permits the App to retrieve your account balances and transaction data. Plaid's collection and use of your information are governed by Plaid's End User Privacy Policy.
1.3 Data Stored on Our Server. For each linked financial institution, our server stores only the following:
- (a) the Device ID associated with your device;
- (b) the Plaid Access Token, and Plaid's identifier for the connection it belongs to;
- (c) the name of the financial institution (e.g., "Chase"); and
- (d) three dates: when the institution was linked, when a refresh of its data was last requested, and when your device last contacted our server.
We do not store transactions, balances, account numbers, or any other financial account data on our server. When the App refreshes your data, transaction and balance information is transmitted from Plaid, through our server, to your device without being written to persistent storage, and all such responses are designated as non-cacheable.
1.4 Product Analytics and Error Reporting. The App uses PostHog, Inc. ("PostHog") to measure how the App's features are used and to receive automatic reports when the App encounters an error. This information is transmitted to PostHog's United States cloud infrastructure. PostHog assigns your installation a random analytics identifier that it generates itself; that identifier is separate from the Device ID described in Section 1.1 and is not linked to it. We do not call PostHog's user-identification feature, and no PostHog person profile is created for you.
The information sent to PostHog consists of:
- (a) usage events recording that an action occurred in the App, such as completing the introductory walkthrough, linking or unlinking a financial institution, setting a goal, planning a period, correcting a category, completing a lesson, or changing a setting, together with small descriptors of the action: the check-in rhythm you have chosen, which of the App's predefined categories, settings, or screens was involved, yes-or-no choices, counts, and whether the event came from a development or released build of the App. These descriptors never include amounts, balances, transaction descriptions, merchant or financial institution names, or account identifiers. We will provide the current list of events on request (see Section 10);
- (b) screen views within the App, identified by screen name (a lesson's screen carries the lesson's title, and a category's screen carries the category's name), and lifecycle events such as the App being installed, opened, or sent to the background;
- (c) technical characteristics of your device: device model, manufacturer, and type; operating system name and version; App version and build number; screen dimensions; language; time zone; and network connection type;
- (d) your IP address, which PostHog receives with each request and uses to derive an approximate location (such as country, region, and city);
- (e) where the App encounters an unhandled error, a diagnostic report containing the error's type, its message, and the sequence of code locations at which it arose; and
- (f) if you allow notifications, a push token Apple issues for your device, which lets us send you notifications about the App (for example, that a new version is ready) through PostHog. The token identifies your device to Apple's notification service and carries no financial information. Turning notifications off for the App in iOS Settings stops these notifications; turning usage sharing off stops the token from being sent.
We do not send transaction descriptions, amounts, balances, account numbers, financial institution names, or goal amounts to PostHog, and the App does not record your screen. You may turn usage sharing off at any time in the App (Settings → Privacy → Share usage data); no further events are sent from that moment, and the choice persists across launches. PostHog's handling of this information is governed by PostHog's Privacy Policy.
2. Transaction Categorization
When you use the App's categorization feature, the App transmits transaction descriptions and amounts (e.g., "Corner Coffee, $4.75") to our server, which submits them, numbered by position, to Google LLC's Gemini API for assignment to one of the App's predefined categories. The resulting categories are returned to and stored solely on your device. Neither our server nor the App retains any copy of this data. The requests contain no transaction identifiers, account identifiers, dates, financial institution names, or Device ID, and no information regarding your identity.
We use Google's paid API tier, pursuant to which Google does not use submitted data to train its models and retains such data only for a limited period for abuse-monitoring purposes, as described in the Gemini API Terms of Service.
3. Service Providers and Hosting
We rely on the following service providers, each receiving only the information described where noted:
- Plaid Inc.: connecting your financial institutions and retrieving their data (Section 1.2). Plaid also acts under its own End User Privacy Policy;
- PostHog, Inc.: product analytics and error reports (Section 1.4), and beta sign-ups (below);
- Google LLC: assigning transactions to categories (Section 2);
- Railway Corp.: hosting our server (below);
- Cloudflare, Inc.: hosting this website (below); and
- Apple Inc.: distributing the App's beta through TestFlight (below).
Our server is hosted on Railway Corp. ("Railway"). Requests to our server pass through Railway's infrastructure in the ordinary course. Our server does not log the contents of requests or responses. It records operational diagnostics only: for each answer, the number of rows returned and the date range covered; when an answer fails an internal consistency check, the identifiers of the rows involved and the names of the fields that disagreed, never their amounts; and, when Plaid returns an error, Plaid's error code and message. The Device ID is not written to the log. Railway's practices are described in Railway's Privacy Policy.
This website. smore.money is a static website hosted by Cloudflare, Inc. The website does not use cookies. If you use the light or dark mode switch, your preference is stored locally in your browser and is not transmitted to us. Cloudflare processes requests to the website as described in Cloudflare's Privacy Policy.
Beta Program. If you request access to the App's beta, we collect the email address or phone number you provide. We use this information solely to invite you to the beta through Apple's TestFlight and to contact you about the beta by email or text message. We store this information with PostHog (see Section 1.4), do not sell it or share it with third parties other than our service providers, and delete it when the beta ends or upon your request (see Section 10). We also record, without identifying you, when the beta invitation is opened; we do not record this if your browser sends a Do Not Track or Global Privacy Control signal. Your use of TestFlight is governed by Apple's privacy policy.
4. Data Stored on Your Device
Your transactions, balances, categories, goals, and lesson progress are stored locally on your device. Deleting the App from your device permanently removes this data. Two things survive deletion: the Device ID, which iOS retains in the keychain so that reinstalling the App restores your linked institutions, and the Access Tokens on our server, which are removed as described in Section 6. To remove those as well, unlink each institution before deleting the App, or contact us under Section 6.3.
5. What We Do Not Do
We do not: (a) use advertising identifiers or cross-application tracking technologies; (b) display advertisements; (c) record your screen or use session-replay technology; (d) sell or rent your personal information, or share it for cross-context behavioral advertising; or (e) disclose it to anyone other than the service providers listed in Section 3, for the purposes described there. Our use of analytics is limited to what Sections 1.4 and 3 describe.
6. Data Retention and Deletion
6.1 Unlinking. You may unlink a financial institution at any time within the App (Accounts → Manage). Unlinking revokes the associated Access Token with Plaid and immediately and permanently deletes it from our server. If all institutions are unlinked, our server retains no information associated with your device. Settings → Privacy → Start over does this for every institution at once and also erases everything the App has stored on your device, other than the Device ID.
6.2 Automatic Deletion. When a device has not contacted our server for twelve (12) consecutive months, each Access Token linked to it is automatically revoked with Plaid and deleted from our server, together with its associated Device ID. The check runs daily; where Plaid cannot be reached, the removal is retried on subsequent days until it succeeds.
6.3 Deletion Requests. You may contact us at the address in Section 10 to request deletion of any information our server holds in connection with your device, or to request a description of such information.
6.4 Analytics Retention. Usage events, screen views, device characteristics, and error reports sent to PostHog under Section 1.4 are retained for thirty (30) days and then deleted.
7. Security and Incident Response
All data transmitted between your device, our server, Plaid, and Google is encrypted in transit using HTTPS (TLS). The most sensitive information held on our server consists of Plaid Access Tokens. In the event we become aware of a security incident affecting Access Tokens, we will promptly revoke the affected tokens with Plaid and provide notice on this website and, where the App can carry it, in an App update, in addition to any notification required by applicable law.
8. Children's Privacy
The Services are not directed to children under 13, and we do not knowingly collect personal information from children under 13, consistent with the Children's Online Privacy Protection Act (COPPA).
9. Changes to This Privacy Policy
We may update this Privacy Policy from time to time. The effective date above will be revised to reflect any update. In the event of a material change, we will provide notice on this website, and in the next App update, before the change takes effect. Your continued use of the Services following the effective date of any update constitutes your acknowledgment of the revised Privacy Policy.
10. Contact
Questions, requests, or concerns regarding this Privacy Policy may be directed to: team@likivo.com.