Privacy Policy
Effective date: 2026-10-02
1.Introduction
Feel More Energy LLC (“we”, “our”, “us”) operates moreconnected, a customer-relationship platform that businesses use to manage their contacts, their campaigns, their calls, and their relationships with social-media creators.
This policy explains what we collect, why, who else sees it, and what you can ask us to do about it. It covers the web application at moreconnected.ai and the services behind it, including the Meta app named “Connecti Roster”.
moreconnected is sold to businesses. If you are an individual whose details a business stores here — a contact, or a creator they found — you are not our customer, but this policy still describes what we hold about you and what you can ask for. See section 10.
2.Who controls your data, and how to reach us
| Controller | Feel More Energy LLC |
| Address | 1000 Brickell Avenue, Suite 715 PMB 431, Miami, FL 33131, USA |
| Privacy contact | support@feelmoreenergy.com |
| Response target | 30 days |
3.What this platform does — and does not do
The product does the following:
- Stores a business’s contacts, notes, campaigns, and message history, and moves its leads through a pipeline of stages the business defines.
- Places and receives phone calls and text messages from the browser. This includes a power dialer that works through a list of leads, and bulk text messages sent to many leads at once, which go out only after a person approves the campaign.
- Records calls, where the business chooses to, transcribes them so the business can search them, and writes AI summaries of them.
- Scores recorded sales calls with AI, to coach the team (Coach).
- Provides team chat, including recorded voice messages, and video calls and meetings. Guests without an account can join a meeting through a link once a host lets them in. When a team member starts a recording, a meeting is recorded and transcribed, with an AI summary.
- Keeps a calendar, and a booking page where people can request a time to meet.
- Tracks tasks.
- Stores and shares files (Vault).
- Sends documents for electronic signature through a signing link.
- Sends and receives email on a business’s behalf, from mailboxes that business has connected: a Google account, or any mailbox connected with its IMAP and SMTP password.
- Runs email and text-message flows that a business sets up. Once a person publishes a flow, its email and text steps send on the schedule the flow sets. A step that uses AI to draft a follow-up waits until a person reviews it and sends it.
- Collects the answers people submit on public web forms a business publishes, including the contact form on our own website.
- Reads receipts with AI to record expenses (Ledger).
- Keeps staff schedules and clock-in times (HR).
- Offers Pulse, an AI assistant that tracks a team’s projects and creates project items once a person confirms them.
- Searches public sources and Instagram’s Creator Marketplace for creators matching criteria the business describes, reading public Instagram, TikTok, and YouTube profiles.
- Shows a business the Instagram direct messages people send to its connected Instagram business account, and lets a person on the team reply, within the time Meta allows for a reply.
- Publishes social posts on a business’s behalf, to the accounts that business has connected for that purpose: Instagram, Facebook, TikTok, YouTube, LinkedIn, Pinterest, Threads, and X. Publishing runs through Ayrshare, using credentials the business supplies for it. See section 5 for why this is separate from the Meta connection Roster uses.
It does not do the following:
- Start a conversation, or send an unsolicited direct message, on Instagram or Facebook. Meta does not allow a business to message someone who has not written to it first, and we do not attempt to. The only Instagram direct messages the product sends are replies a person on your team sends to someone who messaged your business first.
- Comment, like, or follow through any connected social account.
- Sell personal data to anyone.
- Use the data one business stores to serve another business, or combine data across businesses into any cross-customer profile.
- Make automated decisions producing legal or similarly significant effects. Creator scores and AI suggestions are advisory and a person decides what to do with them.
- Run advertising, analytics, or crash-reporting SDKs. There are none in the application.
4.What we collect
From the businesses who use the product. Names, email addresses, and the organization each user belongs to. Whatever those users choose to store — contacts, notes, campaigns, messages, files.
From connected accounts. When a business connects an external account we store the access credential needed to act on that connection, encrypted at rest, together with the data that connection returns. A mailbox can be connected with a Google account or with its IMAP and SMTP password; a password is encrypted the same way, and is used only to read and send that mailbox’s mail.
Instagram direct messages. When a business connects its Instagram business account, Meta sends us the direct messages people send to that account: the message text, any attachments Meta includes, the sender’s Instagram-scoped ID (a number Meta assigns, not a username), and the time it was sent. Replies a team member sends are stored the same way, together with who sent them. They are part of the business’s data and are kept as section 8 describes.
About creators and contacts. Businesses use the product to research and reach creators and their own contacts. A record may hold a public username, a public biography, publicly listed contact details, whether an account is verified, past brand-partnership history where a platform publishes it, and the business’s own notes and scores.
Calls, meetings, and text messages. Calls placed or received through the product are carried as live audio, recorded where the business chooses to record them, and may be transcribed to text so the business can search and review them. A video meeting is recorded and transcribed only when a team member starts a recording, and the transcript is summarized with AI. Text messages sent or received through the product are stored with their content and the numbers on each end.
From people who fill in a web form. A business can publish web forms, and what a visitor submits is stored in that business’s account. If you write to us through the contact form on our own website, we receive your name, email address, subject, and message, and they are stored as a lead in our own account in the product so that we can answer you. If the form cannot reach us, it opens your email app instead, and nothing is sent to us until you send that email.
From a business’s own store. A business can connect its Shopify store, and we then receive the customer records that store sends us — name, email address, phone number, and postal address — so those customers appear as contacts in the product. This happens only for a business that has connected a store, and only for the customers that store sends.
Technical data. Server access logs, including IP address, browser user agent, and the time of each request.
5.How we use Meta data specifically
This section describes the Meta app named “Connecti Roster”. It applies when a business connects its Facebook Page and the Instagram business account linked to it.
- We store a Facebook Page access token, encrypted at rest, so the product can make requests on that business’s behalf.
- We use it to read the connected account’s identity, to search Instagram’s Creator Marketplace for creators matching criteria the business sets, and to receive and reply to the Instagram direct messages people send the business.
- The Creator Marketplace API is read-only. It returns a creator’s username, biography, contact email where the creator has published one, profile picture, verification status, onboarding status, badges, and brand-partnership history.
- When someone messages the connected Instagram account, Meta sends us the message as described in section 4. When a team member replies, we send Meta the reply text and the recipient’s Instagram-scoped ID, and Meta returns an ID for the sent message.
- Results and messages are visible only to authorized users of the business whose account was connected.
We do not post, comment, like, or follow through any connected Meta account, and we never start a conversation from it. The only messages sent through it are replies a person on the business’s team sends to someone who messaged the business first, within the time Meta allows for a reply. We do not use Meta data for advertising, and we do not sell it. We do not share it with other businesses using the product, and we do not use it to build any profile spanning our customers.
A business can disconnect at any time inside the product, which deletes our stored credential. Access can also be removed from Facebook’s own Business Integrations settings.
6.Why we use it, and on what legal basis
| Purpose | Data used | Legal basis (GDPR) |
|---|---|---|
| Provide the core product — contacts, campaigns, calls, creator discovery | Account details and whatever the business stores in the product | Contract (Art. 6(1)(b)) |
| Search Instagram’s Creator Marketplace on a business’s behalf | The connected Instagram account and the business’s search criteria | Consent, given when the business connects the account (Art. 6(1)(a)) |
| Interpret search descriptions and score creator profiles | The prompt text and public creator profile data | Legitimate interests (Art. 6(1)(f)) |
| Send and read mail, and read calendar availability | Mailbox and calendar content | Consent, given when the business connects Google or a mailbox (Art. 6(1)(a)) |
| Receive and reply to Instagram direct messages sent to a business | The messages people send the business’s Instagram account, and the replies | Legitimate interests, in answering people who wrote to the business (Art. 6(1)(f)) |
| Answer people who write to us through our website’s contact form | Name, email address, subject, and message | Legitimate interests, in replying to the person who wrote (Art. 6(1)(f)) |
| Carry and transcribe calls | Call audio and its transcript | Contract (Art. 6(1)(b)) |
| Security, fraud prevention, and debugging | Server access logs, including IP address | Legitimate interests (Art. 6(1)(f)) |
7.Who else receives information
We do not sell personal information. We share it with the service providers that operate the platform on our behalf, for the purposes named here and no others:
| Vendor | Purpose | Data shared |
|---|---|---|
| Meta (Facebook and Instagram) | Connecting a business Instagram account, searching for creators, and receiving and replying to Instagram direct messages | The search criteria the business sets, and the text of each reply a team member sends with the recipient’s Instagram-scoped ID. Meta sends us the messages people write to the business. See section 5. |
Gmail and Google Calendar, for sending and reading mail and reading calendar availability; Google Maps, for showing maps and suggesting addresses as you type; Geocoding, for turning postal addresses into coordinates; YouTube, for looking up channels and videos; and Google Docs, for reading a public document a user links as a project brief | Mailbox and calendar content, for businesses that connect a Google account; addresses being located, typed, or shown on a map, and the IP address of the browser showing the map; the YouTube channel handles and video IDs being looked up; and the ID of the linked Google Doc | |
| OpenStreetMap (Nominatim) | Turning postal addresses into coordinates | The address being located |
| Anthropic | The product’s AI features: interpreting creator searches and scoring creators; drafting emails, text messages, and follow-ups for a person to review; scoring and summarizing calls (Coach); summarizing meetings and tidying dictated text; writing social post copy; reading receipts (Ledger) and profile screenshots; and the Pulse and Atlas assistants | The material each feature works on: search descriptions and public creator profiles; call and meeting transcripts; the conversation history and contact details a draft needs; dictated text; post media and copy; receipt images and uploaded screenshots; and the questions users ask the assistants, with the business’s own data those assistants read to answer |
| Apify | Retrieving public creator profile data, and publicly listed contact details, from social platforms and websites | The public usernames, web addresses, and search terms being looked up |
| Exa | Keyword search used to surface public creator profiles | The search terms |
| ATTOM | Property data lookups | The property address being looked up |
| Telnyx | Carrying phone calls and text messages, recording calls, and transcribing recorded audio | The phone numbers on each end, call audio and its recordings, the transcribed text, and the content of text messages |
| Ayrshare | Publishing social posts on a business’s behalf to the accounts it has connected | The post content and any attached media, and the social-account credentials the business supplies for publishing |
| LiveKit | Open-source software we run on our own servers, carrying live audio and video for team calls and video meetings, and recording a meeting when a team member starts a recording | Nothing leaves our infrastructure for LiveKit itself: call and meeting audio and video pass through the LiveKit server we operate, and recordings are saved to our own storage |
| Deepgram | Converting audio to text, including live meeting transcription, and text to speech | The audio being transcribed, including meeting audio while a meeting is transcribed, and the text to be spoken |
| Cloudflare | Serving the site and terminating its secure connections, and storing the files kept in Vault (Cloudflare R2) | Traffic to and from the product, and the files uploaded to Vault |
| Follow Up Boss | Keeping leads and their notes in step with Follow Up Boss, for a business that connects its own Follow Up Boss account | The lead notes we create, update, or delete there. We read that account’s people and notes to match them to leads by email address and phone number |
| Supadata | Fetching YouTube video transcripts and channel details to build training lessons | The YouTube channel and video IDs being looked up |
| OpenAlex | Checking the published-research record of people found through a people search | The person’s full name, and the OpenAlex author ID that search returns |
| Hostinger | Running the servers and the database the product itself runs on | Everything the product stores, at rest on its infrastructure, including the encrypted credentials for the accounts a business connects |
| Stripe (including Link) | Selling and billing subscriptions. Link, a Stripe service, is the merchant of record and collects your payment details directly at checkout; we never receive card numbers. | Our identifier for your organization, attached to your subscription so we can match a payment to your account. |
The database, call and meeting recordings, and most uploaded files are held on infrastructure we operate, on servers provided by the hosting company named above. Files kept in Vault are stored with Cloudflare R2. We also disclose information where the law requires it, or to protect our rights or someone’s safety.
8.Where data is held, and for how long
Data is stored in the United States. Some of the providers listed above operate in other countries, so information may be transferred internationally; those transfers are covered by the providers’ own data-processing terms and protected in transit by TLS.
We keep a business’s data for as long as its account is active. After an account closes we delete or anonymize it within 90 days. That deletion is carried out by hand rather than on an automatic schedule — we do not run a background job that erases data on a timer, and we would rather say so than imply one. A business can delete an individual contact at any time from within the product. Calls, recordings, Instagram direct messages, and creator records surfaced by Roster are removed on request — there is no in-product control for those yet, and we would rather say so than point you at a button that does not exist. We act on a deletion request from a creator or contact directly.
9.Security
Traffic is encrypted in transit with TLS. Credentials for connected services are encrypted at rest with a key held outside the database. Every request that carries a business’s data is authenticated and authorized against the organization the user belongs to, so one business cannot read another’s. Some routes are necessarily public, and those are protected by other means rather than by a signed-in session. For example, the endpoints that Meta (for Instagram direct messages) and a connected store post to check each delivery’s signature. The callback a social platform redirects a browser to only completes a connection a signed-in user started. Public web forms, including the contact form on our website, accept a submission from anyone and store only what the form asks for.
Sessions use a short-lived access token held only in memory, paired with an httpOnly refresh cookie — the access token is never written to browser storage.
No system is perfectly secure. If you believe an account has been compromised, write to support@feelmoreenergy.com.
10.Your rights
Depending on where you live, you may have the right to access, correct, delete, or export your personal information, to restrict or object to certain processing, and to withdraw consent. Exercising a right never costs you anything and we will not treat you differently for it.
If you use the product through your employer or a client, that business controls your data. Contact them first; we will support their response.
If you are a creator or a contact stored by a business using the product, we hold that record on their behalf. Write to support@feelmoreenergy.com and we will route your request to them and, where we are able, act on it ourselves. You can also ask us to remove a creator record sourced from Instagram’s Creator Marketplace.
You may also complain to your local data protection authority. We would rather you came to us first so we can fix it.
11.Cookies
We use essential cookies only. The session cookie keeps you signed in; without it the product cannot work. Our website runs no advertising cookies, no tracking pixels, and no third-party analytics. Separately, an email a business sends through the product can carry a small image that tells the business when the message was opened.
12.Children
This is a business product, it is not directed to children, and accounts may not be created by anyone under 18. If you believe a child has given us personal information, write to support@feelmoreenergy.com and we will delete it.
13.Changes to this policy
We will post any change on this page and update the effective date above. For material changes — a new category of data, a new provider, a new legal basis — we will notify account administrators before the change takes effect.
14.Contact us
Feel More Energy LLC · 1000 Brickell Avenue, Suite 715 PMB 431, Miami, FL 33131, USA
Privacy requests: support@feelmoreenergy.com
Phone: +1 (305) 846-8382
You can also reach us through our contact page.