Felren Privacy Policy

Effective 28 October 2026 · Felren (“we”, “us”) · Contact: team@felren.com

1. What Felren is

Felren is a Mac app, with a companion Chrome extension, that builds a private picture of your world from your own data: the people you are close to, arranged in relationship rings with short summaries, and a shopping assistant that knows your preferences, what you have bought, and what you are running low on. When you approve a purchase, it can prepare the checkout for you, and you place the order yourself.

2. What we collect

We collect data only from sources you choose to turn on. Every source is off until you turn it on. Gmail is read only once you connect a Gmail account, and the Chrome extension records nothing until you turn capture on in it (see §3). Once a source is on, every conversation in it is included.

The per-source switches are in version 0.4.23 and later of the Mac app. An earlier version has no switches: it reads every source on your Mac that macOS lets it read, from the moment you sign in. Update the app to choose source by source.

Derived data. From the above we compute classifications, relationship summaries and ring positions, facts about your preferences and needs as a buyer (for example sizes, brands, dietary constraints and devices you own), purchase history, and restock suggestions. Derived data is stored with your account and is covered by the same deletion rights.

Controls. Switching a source off stops future collection from it. Switching it back on imports that source again, which can include what arrived while it was off. Disconnecting a source stops future collection and removes its credentials; for Gmail it also revokes Felren’s access at Google. None of these erases data already collected; deleting your account does. Muting a person or hiding them from the graph changes what you see, not what is stored.

3. The Chrome extension

The extension records no browsing until you sign in, read its disclosure, press Start capturing, and grant Chrome website access. The shopping agent (below) is separate: it stays off until you turn it on in the extension, under its notice, and then works only on a purchase or a seller message you approve in the Felren app on your Mac, whether or not capture is on.

What it records

For each page you visit: the site, the page title, a sanitized URL (sign-in tokens, codes and other credentials removed), time actively spent on the page, the linking site and the navigation type. On a product page it also records the product’s name, brand, price, currency, availability, SKU and GTIN, read from the page’s structured data (schema.org and OpenGraph). On Amazon, whose pages carry no structured data, the product’s name comes from the page title and its product code (ASIN) from the URL, both of which it already records; nothing else on the page is read. While you browse it does not record page text, form entries, text selections or incognito browsing.

Major banks and brokerages, some patient portals, password managers, identity providers, webmail (Gmail, Outlook, Yahoo Mail, Proton Mail, iCloud Mail and others) and sign-in pages are blocked by default, and you can block more sites in the extension’s Settings. You can pause capture from the toolbar.

The shopping agent

When you approve a purchase in the Felren app, the extension opens the store in a new tab and moves through the product, cart and checkout pages using Chrome’s debugger. Chrome shows a “debugging this browser” bar the whole time, and cancelling it, pausing the extension or signing out stops it. While it works it sends our server an outline of the store page it is on. On a product page or in a cart pop-up, the outline has the page’s text, headings, buttons, links, choices and field names; on cart and checkout pages, only the names of buttons, links, choices and fields, plus the page type, the order’s subtotal, totals and currency, whether a payment method is chosen, whether it has a recurring charge and, on an order confirmation, the order number. It never sends the contents of a form field, but the outline can include what the store itself shows, such as a saved address or card description offered as a choice, or a note displayed in a cart. Once a personal or card field on the page is filled in, it sends only the names of the page’s buttons, links, choices and fields and those page facts, leaving out any name that repeats a word of four or more letters or digits, or a run of three or more digits, of what was filled in and, once a card field is filled in, any name with a digit in it. Our server passes that outline to our AI provider (OpenAI) to choose the next step from a fixed list, and does not store it. The extension can fill your saved shipping address and the purchase’s one-time card from the Felren app on your Mac. The card is never sent to our servers. It stops before placing the order: you press the final button yourself. When you ask it to find something used on Craigslist, it opens one Craigslist search page at a time in a background tab and sends our server that page's outline with its listing links, so Felren can suggest listings; when you pick one, it opens the listing, presses its reply button once to show the seller's relay email address, and opens a drafted email in your mail app. It never sends a message: you press Send. On Facebook Marketplace, when Felren offers it, it searches the same way, reading only the page's main area, and types a draft into the listing's own message box; you press Send. After that, for up to 7 days and only while Chrome is open, it re-opens that listing in a background tab at most every 2 hours, presses Message Seller, and sends our server that one conversation so Felren can show the seller's reply; you can stop it in Settings.

The cloud shopping agent

When Felren offers it and you turn it on, the same shopping agent can run in a cloud browser instead of your own Chrome, for example when your Mac is asleep. It runs on our cloud-browser provider, Amazon Web Services (Bedrock AgentCore Browser), in a fresh browser started for that one purchase and closed when it ends, at most 10 minutes later. It works only on stores we have approved for it (never Amazon, eBay, Target, Walmart or Best Buy), identifies itself to the store as an automated agent, and checks out as a guest: it never signs in to the store, never solves a CAPTCHA (it stops and hands the purchase to you), and is never given a card or a login code. It fills in your saved shipping details (your name, email and address), which our server reads one line at a time for that purchase only and does not keep, and it stops at payment: you pay yourself. Recording is off for these sessions. It sends our server and our AI provider the same page outline as in your own Chrome. You can pause it or turn it off at any time, and sites you block for it are kept, encrypted, on our servers so it can respect them.

Deleting extension data

Delete any recent visit from the extension’s toolbar popup, and it is deleted on our servers too. Signing out clears your sign-in, recorded visits and upload queue on this device. Excluded sites and your account identifier remain; pending deletion requests keep account and visit IDs until our server confirms them. Deleting your account erases everything (see §10).

4. Purchases and payments

Purchases require your approval each time. Payment uses your own Link account (by Stripe), connected from the Felren app on your Mac. For each purchase you approve, Link issues a one-time card for the approved amount, and it is used only on your Mac and in your browser. We store the purchase record (merchant, item, amount, status and order number), never your card number.

Your shipping details go only to the store you’re buying from. When you ask Felren to buy something, it passes your name, email and shipping address only to the store you are buying from, never to any other store, in one of two ways: in a cart our server prepares for that store (for a Shopify store, our server sends them to the store’s Storefront API to create the cart, or puts them in the checkout link it gives you to open), or typed into the store’s checkout by your shopping agent, on your Mac or in your cloud browser on AWS (see §3). Our server reads them from the shipping details you saved, for that one purchase, and keeps no copy of what it sends. The store handles them under its own privacy policy.

5. How we use data

• To build your relationship rings and summaries.
• To power your shopping assistant: your buyer facts, purchase history, restock and product suggestions, and preparing checkouts for purchases you approve.
• To operate, secure and debug the service, and to prevent abuse.

We do not sell your data, use it for advertising or share it with data brokers, use it to decide creditworthiness or for lending, or use it to train our own or anyone else’s general-purpose AI models.

6. Information about people you communicate with

Your messages, calls and contacts include information about other people. We process it only to provide Felren to you. We never contact those people, never build profiles of them for anyone else, and never sell or advertise with their information.

7. Security

• All data travels over encrypted (TLS) connections.
• Message content is encrypted at rest with a per-user key managed by AWS Key Management Service. Some fields derived from content are not yet encrypted at rest, and closing that gap is ongoing work.
• Every request is scoped to your account by our application code. Connected-account tokens are stored encrypted, and our secrets are held in AWS Secrets Manager.
• Our servers must read your content in order to process it, for example to classify a message or summarize a relationship. That processing is automated.

Report a security issue to team@felren.com.

8. Who at Felren can see your data

No person at Felren reads your data except: with your explicit permission (for example, when you ask us to fix a problem you are seeing), when needed to investigate a security incident or abuse, or when required by law.

9. Service providers

We share the minimum each provider needs to run Felren for you. None may use your data for its own purposes.

We may disclose data if required by law, or as part of a merger or acquisition, in which case this policy continues to apply to it.

Text messages

We text you a one-time verification code only when you ask for one in the app. Messages are delivered through AWS End User Messaging Notify. No mobile numbers will be shared with third parties or affiliates for marketing or promotional purposes. Text messaging originator opt-in data and consent will not be shared with any third parties. AWS does not share end user phone numbers with third parties for marketing or promotional purposes. Text HELP for help or STOP to cancel; the full terms are our SMS Terms.

10. Retention and deletion

We keep your data while your account is active, so Felren can remember long-term context. There is no automatic expiry. You control deletion:

• Export your data in the Felren app’s Settings › Privacy (Export my data…). You get a ZIP file of JSON files with your account’s data, including your messages and email decrypted, people, relationship graph, shopping data and settings, with a README that explains each file. It leaves out credentials, such as access tokens and device keys, and our security audit log. You can export once a day.
• Delete your account in the Felren app’s Settings. This permanently erases your messages, derived data, relationship graph, shopping data and credentials. What a service provider still holds under its own retention terms, such as the request content OpenAI keeps for up to 30 days to detect abuse (see §9), is deleted on that provider’s schedule. We keep a minimal record that the deletion happened, for security audit, and any opt-out a phone number sent us (see §2).
• Delete a visit from the Chrome extension’s popup.
• Switch a source off to stop collecting from it. What was already collected stays until you delete your account.
• Disconnect a source to stop collection and remove its credentials. For Gmail, this also revokes Felren’s access at Google.

Operational logs. To run and secure the service we keep technical logs: request IDs, your account ID, the API route called, status codes, timings, error types, and security events such as sign-ins (with IP address). From late September 2026 these logs are designed not to contain message content or the names, email addresses or phone numbers of the people you talk to. Log lines written before then can contain contact names and short summary previews, and they are deleted when their retention window below ends. The system journal on our server is kept for up to 30 days, and a tamper-resistant copy is kept in AWS for up to 400 days for security and audit purposes. The Mac app keeps diagnostic logs on your own computer, and we see them only if you send them to us.

11. Google user data

This section describes exactly what Felren does with data it receives from Google when you connect Gmail. It applies on top of the rest of this policy, and where the two differ, this section wins for Gmail data.

The permission we ask for

Felren asks for one Google permission: read-only access to Gmail (https://www.googleapis.com/auth/gmail.readonly). It cannot send, delete, label, move or change your email. We ask for it only when you choose to connect a Gmail account, after the Felren app explains what follows, and you can connect several accounts or none.

What we access

For the Gmail accounts you connect, we read each message’s plain-text body, subject, sender, recipients (To, Cc and Reply-To), date, labels, and message and thread identifiers. We skip Spam, Trash and drafts. We skip newsletters and other bulk mail unless it looks like an order, receipt, payment or shipping email. We never download attachments.

How we use it

Gmail data is used only to provide features you can see in the Felren app:

• Your purchases. Order, shipping and return emails become your purchase history, the Purchases drawer and restock suggestions. This is on by default for your first Gmail account, and you can turn it off per account (Commerce, in Settings › Sources).
• Your relationship rings. Who you email and how often places people on your rings, and their summaries draw on your conversations with them. This happens only for accounts with Context turned on.

To provide these features, email content is processed by our servers and by OpenAI (see §9). That processing is automated.

What we never do with it

• We do not sell Gmail data or transfer it to advertising platforms, data brokers or information resellers.
• We do not use it to serve advertisements, including personalized, retargeted or interest-based ads.
• We do not use it to determine creditworthiness or for lending.
• We do not use data from Google Workspace APIs, including Gmail, to develop, improve or train generalized or non-personalized AI or machine learning models, and our AI provider does not train on it.
• No person at Felren reads your Gmail data, except with your explicit permission for specific messages, when needed for security (such as investigating abuse or a bug), or to comply with law.
• We do not send Gmail data to sellers or merchants, and we do not show it to other Felren users. To find a product you bought before, its name and brand from your receipt may be sent as a search query, with nothing that identifies you, through our shopping search provider (§9) to Google Shopping and Amazon. The one exception is your choice: if you turn on purchase sharing, Felren users you are mutually connected with can see products you bought, with a rounded price, rough timing and, if you said what you thought of one, a short paraphrase of that opinion. They never see your emails themselves.

Who it is shared with

Only the service providers that run Felren for you, and only what each needs: OpenAI processes email content to classify messages, read receipts and write summaries. It does not use it to train its models, and it keeps it for up to 30 days to detect abuse (see §9). Amazon Web Services hosts our servers and database in the United States. Our shopping search provider receives a purchased product’s name and brand as a search query, to find that product to show you, and keeps that search for up to 31 days before deleting it. None of them may use your data for its own purposes.

How it is protected

Gmail data travels only over encrypted (TLS) connections. Email text is encrypted at rest with a key specific to you, managed by AWS Key Management Service. Other fields, such as subjects, addresses and labels, are stored in our database, which is encrypted at rest. Your Google access tokens are stored encrypted. Every request is scoped to your account.

Keeping, revoking and deleting it

• We keep Gmail data while your account is active, so Felren can remember long-term context. There is no automatic expiry.
• Disconnect a Gmail account in Settings › Sources to stop new mail. Disconnecting also revokes Felren’s access in your Google account. Email already collected is kept until you delete your account.
• You can also remove Felren’s access at any time at myaccount.google.com/permissions.
• Delete your account in Settings › Privacy to permanently erase your Gmail data, everything derived from it, and your Google tokens. Felren also revokes its Google access when you delete your account. Email content OpenAI is still holding to detect abuse is deleted on OpenAI’s schedule (see §9).
• Export your data in Settings › Privacy (Export my data…) to download a copy of your Gmail data and everything derived from it, as JSON files in a ZIP, once a day. Your Google tokens are not included.
• To ask us to delete specific data, email team@felren.com.

Step-by-step help is at Managing your Gmail data.

Limited Use

Felren’s use and transfer of information received from Google APIs to any other app will adhere to the Google API Services User Data Policy, including the Limited Use requirements. The use of information received from Google Workspace APIs will adhere to the Google Workspace API User Data and Developer Policy, including the Limited Use requirements.

The use of information collected by the Felren Chrome extension will adhere to the Chrome Web Store User Data Policy, including the Limited Use requirements.

12. Your rights

You can get a copy of your data yourself, in a machine-readable format (JSON), with Export my data… in the app’s Settings › Privacy, once a day (see §10). Account deletion is self-serve there too. You can also ask to access, correct or delete your data, or ask a question about it, by emailing team@felren.com. We answer within 30 days. Depending on where you live, you may have further rights under local law, and you can complain to your data protection authority.

Your data is stored and processed in the United States. Network traffic passes through Cloudflare’s global network on its way to our servers, and some service providers above may process data elsewhere under their own safeguards.

13. Children

Felren is not directed to children under 16, and we do not knowingly create accounts for them.

14. Changes

If we make a material change to this policy, we will email account holders before it takes effect and update the date at the top.

28 October 2026. ContextFlow, made by Finaimo, was renamed Felren, and the company is Felren too. The contact address is now team@felren.com. This version also adds two kinds of data we collect:

• The rest of each contact card. Beyond names, phone numbers and email addresses, Contacts now also sends birthdays and other dates, postal addresses, notes, company, department and job title, nicknames, related people, social profiles, websites and messaging handles, never photos (see §2). To write a person’s summary, OpenAI receives the company, department, role, nickname, related people and note from their card, never the address or birthday fields (see §9).
• Purchases you mention in your messages, with who they were for when you say so (see §2).

Otherwise, how we collect, use, share, protect and delete your data did not change. Text messages from us, such as verification codes, may still name ContextFlow until our messaging registration is updated.