Legal
Privacy Policy
This Privacy Policy describes how Many Software Enterprises LLC handles personal data when you visit fromenance.com and when institutions use Fromenance, the communication provenance service we operate. It is written to be read, not skimmed; the short version is that we store as little as the service needs, hash what we can, encrypt the rest, and delete on a schedule.
- Effective date:
- Provider:
- Many Software Enterprises LLC, a Delaware limited liability company (manyent.com)
1. Who we are and what this covers
Fromenance is operated by Many Software Enterprises LLC, a Delaware limited liability company ("we", "us"). Our website is manyent.com. This policy covers two situations:
- Website visitors and prospects, for whom we act as the controller of the limited data described in section 2.
- The Fromenance service, which we operate on behalf of institutions (banks, credit unions, insurers, utilities, and similar organizations, our "tenants"). For data processed in the service we act as a processor on the tenant's instructions under our Data Processing Addendum. Section 3 explains what that data is so that the tenant's customers can understand it too.
If you are a customer of a bank or other institution and you forwarded a message to that institution's verify address or pasted it on their verify page, the institution is the controller of that data. Direct your questions and requests to them; the reply you received contains their fraud contact. We will assist them in answering.
2. Data we collect on this website
2.1 Contact and pilot forms
When you submit the contact or pilot form we collect your name, work email address, institution, role, segment, approximate customer count, your message, the page you submitted from, and the IP address of the request. We use this to reply to you and to run the sales conversation you asked for. It is stored in our database (Neon) and a notification is sent to us through our email provider (Resend). We keep it for as long as the conversation is active and for up to 24 months after our last contact, unless you ask us to delete it sooner.
2.2 Interactive demo
The demo on this site sends whatever you paste to the Fromenance service on a demonstration tenant, together with the email address in the demo form if you change it, and your IP address for rate limiting. Demo submissions are stored with the same protections as production submissions (section 3.2) and deleted after the demo tenant's retention window of 90 days. Do not paste real customer messages or real personal data into the demo.
2.3 Server logs and analytics
Our hosting provider, Cloudflare, records request logs (IP address, user agent, URL, timestamp) for security and operations. We may use Cloudflare Web Analytics, which is cookieless and does not fingerprint visitors. We do not use advertising trackers.
2.4 Cookies
fromenance.com sets no cookies beyond those strictly necessary for security and to operate a form or session. The admin application at app.fromenance.com sets an essential session cookie for signed in users. We do not use marketing or analytics cookies and do not show a cookie banner because there is nothing to consent to.
3. Data processed in the Fromenance service
We designed the service so that we hold the minimum needed to answer "did the institution send this?". The categories below are exhaustive.
3.1 Registered communications
When a tenant registers a communication at send time we store: a verify code; a one way HMAC-SHA256 hash of the recipient's email address computed with a secret we issue to the tenant (we never receive or store the address itself on this path, and the database has no column for it); a one way content fingerprint (a 64 bit SimHash and a SHA-256 of the normalized visible text, from which the text cannot be recovered); the message id; the sending address; the sent time; the domains of links in the message; and optional template and campaign identifiers the tenant assigns. We do not store the message body. Registrations expire at the end of the tenant's retention window, 90 days by default.
3.2 Customer submissions
When a customer forwards a message to a tenant's verify address, or submits it on the tenant's verify page, we store: the forwarded message (raw MIME) or uploaded screenshot, encrypted with a key specific to that tenant, in object storage under a prefix specific to that tenant, for the tenant's retention window (90 days by default), after which it is deleted with a deletion record; the customer's email address as a one way hash for matching; the customer's email address in encrypted form only for the purpose of sending the reply, purged 30 days after the reply; the signals extracted from the message (verify code, fingerprint, header authentication results); and the indicators extracted from it (URLs, domains, IP addresses, phone numbers, email addresses, QR payloads), which describe the suspicious message and its sender, not the customer.
3.3 Verdicts and replies
Each submission receives one verdict: Verified, Not verified, or Known fraud, with the rule that produced it and any analyst override. The reply we send on the tenant's behalf never quotes the suspicious message, never includes its links, and never names its sender. Verdicts and indicators are retained for the life of the tenant account because they are the tenant's fraud record.
3.4 Mail that fails the trust check
Mail arriving at a tenant inbox that does not pass DKIM or ARC for a domain the tenant owns, or whose domain lacks the tenant's DNS trust record, is held for 24 hours so the tenant's onboarding can be diagnosed, is never processed or replied to, and is then deleted.
3.5 Tenant staff accounts
Users of the admin application are identified by name, email address, role, and authentication credentials (magic link tokens and passkeys). Every action in the admin application is written to an audit log with the actor, action, target, and before and after values, retained for the life of the tenant account.
3.6 Cross tenant intelligence
Our internal views that span tenants, and the intelligence features on our roadmap, operate on indicators and counts only (for example, that a domain appeared in submissions to more than one tenant). They never include submissions, message content, or customer identifiers, and tenant identities are never disclosed to other tenants.
4. Purposes and legal bases
We process website data to respond to you and to operate and secure the site (our legitimate interests, and performance of the contract you asked us to enter). We process service data on the documented instructions of the tenant under the DPA, for the purpose of verifying communications, replying to their customers, and producing fraud intelligence for that tenant. Where a law such as the California Consumer Privacy Act applies, we act as a service provider to the tenant.
5. Sharing and subprocessors
We do not sell personal data and we do not share it for cross context behavioral advertising. We share data only with:
- Subprocessors that host or support the service: Cloudflare (hosting, edge compute and storage, screenshot OCR, bot protection), Neon (Postgres database), Resend (inbound and outbound email), Stripe (billing), and Sentry (error monitoring). All are located in the United States. The current list, with purposes, is in Annex III of the DPA and on the Security page. We notify tenants 30 days before adding a subprocessor.
- The tenant whose customer submitted the message, which is the point of the service.
- Authorities when required by law, after reviewing the request and, where permitted, notifying the tenant.
- A successor in a merger or acquisition, under this policy.
6. Data residency and transfers
All service data is stored and processed in the United States. If you access the service from outside the United States, your data is transferred to the United States. Tenants who need contractual transfer terms will find them in the DPA.
7. Retention summary
| Data | Retention |
|---|---|
| Registered communications | Tenant retention window, default 90 days |
| Forwarded messages and screenshots | Tenant retention window, default 90 days, then deleted with an audit record |
| Encrypted submitter address | 30 days after the reply |
| Mail failing the trust check | 24 hours |
| Verdicts, indicators, audit log | Life of the tenant account, then deleted within 30 days of termination unless the tenant exports first |
| Contact and pilot form data | Up to 24 months after last contact |
| Server logs | Per Cloudflare's retention, typically under 30 days |
8. Security
Recipient addresses are hashed before they reach us. Message content is encrypted at rest with per tenant keys wrapped by a master key held only in our runtime's secret store. Every tenant's data carries a tenant identifier and every query is scoped to it; an automated test suite asserts that no endpoint reads across tenants. Staff sign in with passkeys or magic links; our internal backoffice sits additionally behind Cloudflare Access with hardware keys. All traffic uses TLS. Credentials are rotated on a schedule. Full detail is on the Security page.
If we confirm a security incident affecting a tenant's data, we notify that tenant without undue delay and no later than 72 hours after confirmation, with what we know and what we are doing.
9. Your rights
Depending on where you live you may have rights to access, correct, delete, or export personal data we hold about you, to restrict or object to processing, and to withdraw consent. To exercise them for website data, emailprivacy@fromenance.com. We respond within 30 days and may ask you to verify your identity. If your request concerns data processed in the service on behalf of an institution, we will pass it to that institution and assist them. You may also complain to your local supervisory authority. We do not discriminate against anyone for exercising these rights.
10. Children
fromenance.com and the Fromenance service are directed at institutions and their staff. We do not knowingly collect personal data from anyone under 16, and the service is not intended for use by children. If you believe a child has provided us data, contact us and we will delete it.
11. Changes to this policy
When we change this policy we update the effective date above and, for material changes affecting tenants, notify tenant administrators by email at least 30 days before the change takes effect. Earlier versions are available on request.
12. Contact
Privacy questions: privacy@fromenance.com. Legal notices:legal@fromenance.com. Security reports:security@fromenance.com. Postal address available on request tolegal@fromenance.com.