Privacy policy

Who we are

1Signal is operated by FounderScale LLC, Fort Lauderdale, FL 33309, United States. In this policy, “we” and “our team” mean FounderScale LLC. For anything about your data, email [email protected].

The design partner application

When you send the application form on this site, we receive:

• Your name and work email.
• Your agency’s name and, if you give them, its website and your role.
• How many active clients you have, your main client type and the band of Meta ad spend you manage.
• Your answers on how you review results with clients, whether you have a client ready for a first program and what you want from 1Signal.
• That you ticked the consent box, and when.
• Your separate, optional choice about Meta advertising measurement, and the wording version for that choice.

We also record the address of the page you applied from, any utm campaign parameters in that address, the user agent your browser sends, whether the email address belongs to a free email provider, and how many times you have sent the form. We do not store your IP address with the application or in our database. Our server keeps it only in its working memory, to limit repeated submissions, and our hosting and network providers may record it in their request logs.

What happens to it

• The application is saved in our database.
• When our application campaign is connected, one record also appears in its lead report. It keeps your actual answers and campaign attribution. Our fit check can compare those answers with the program’s buyer profile using Anthropic. Missing evidence stays unknown; sending an application does not establish that you are a qualified lead or a customer. Our team can record a booked call or customer outcome later.
• A person on our team gets an alert with your answers by email, and a record of the alert, answers included, is kept in our internal notification list.
• If the database cannot save the application, your answers are sent to our team by email and by text or WhatsApp message instead, so the application is not lost.
• If you send the form again with the same email address, your newer answers replace the older ones, and we keep the earlier answers with the record so any change stays visible.
• Nothing is sent to you automatically. Sending the form does not create an account and does not add you to a mailing list. We may email you about your application.

Why: to review your application and contact you about it, as you agreed when you ticked the consent box. You can withdraw that consent at any time by emailing [email protected].

How long: we keep an application until you ask us to delete it. There is no automatic deletion schedule.

Optional advertising measurement

The application has a separate checkbox asking whether Meta may measure it for advertising. It is off by default and you can apply without selecting it. Only if you select it, and you have not declined cookies or enabled a browser privacy signal, may our server send a Lead event to the pixel configured for our application campaign. That event contains your email and name in hashed form, page address, browser details, IP address and any existing Meta browser or ad click identifiers. Your application answers are not part of the event. Our database records the measurement choice, event identifier and whether the event was received, but never your IP address. Hashing does not make the information anonymous.

This choice does not give us permission to send marketing emails. You can withdraw it by emailing [email protected], or by leaving the advertising box unchecked when you send updated answers. Withdrawal stops future measurement from that record; it cannot recall an event Meta has already received.

Analytics, only if you accept

On your first visit, a banner asks whether you accept analytics. Until you click Accept, none of the tools below loads and nothing is sent to them. If you click Decline, they never load.

If you accept, the site loads:

• PostHog, to count page views and clicks, measure page speed and record sessions. Session recordings mask everything typed into form fields and never record what the page sends to our server. PostHog’s click events skip the application form. Its heatmaps and session recordings can still show where on the page you clicked, never what you typed. The PostHog project is shared with FounderScale’s own website.
• Microsoft Clarity, for heatmaps and session recordings of how the page is used. The application form is masked in its recordings.

There is no Meta browser pixel, no Google Tag Manager and no advertising script on 1signal.io. The separate server event described above needs its own opt in. If you send the application after accepting, PostHog records one event saying that an application was sent. It carries none of your answers. The 1Signal app works differently; see The 1Signal app below.

These tools receive technical data such as your IP address, browser and device details and the pages you view, and they set cookies or use similar storage in your browser. Each provider handles that data under its own privacy terms.

You can change your choice at any time with Cookie settings at the bottom of every page. If you decline, or withdraw consent after accepting, the site removes the cookies and browser storage these tools set on this site and, if they were running, reloads the page without them.

What your browser stores for this choice

Your choice (accepted or declined) is saved in your browser’s localStorage under the name 1signal_consent, so the banner does not ask on every page. When you send the application, that choice accompanies the request to prevent advertising measurement after a decline. Clearing this site’s data in your browser removes it, and the banner asks again.

Cloudflare, which carries every request to this site, sets one short lived security cookie named __cf_bm before you choose anything. It tells people apart from automated traffic, expires after 30 minutes, is needed for the site to work and is not used for analytics.

Clients in a program

When an agency runs a program with one of its clients:

• The client connects its Meta ad account with one button in the app, using Facebook Login for Business. In the Facebook window the client picks its business, one ad account, one Page and, if it has one, its pixel. Meta then gives us an access key that belongs to the client’s business and reaches only what the client picked. We store that key encrypted, use it only for that client, and never show it in a browser. With it we check that we can read the ad account and create paused ads (the check creates nothing), create a pixel if the client asks us to, and share the chosen ad account, Page and pixel with FounderScale’s Meta business portfolio as a partner. Once a day we check that the connection still works, and if it stopped, we email the client a link to connect again.
• A client can also send a connect link to the person who manages its ads. The link works without a login for 7 days and connects the same client only. Clients connected earlier through FounderScale’s Meta Business Manager partner access keep that connection.
• We use the partner access to read and manage ads for the program: to set up the test ads, run them, pause each variant at its cap and read the results. We also use it to read the account’s past and current campaigns and their results, and we store summaries of them (account totals, a monthly trend and a summary for each campaign) with the client’s record, so each test starts from what was already tried. We never post on the client’s Page, read its messages or change its payment details. The client can remove this access at any time in Meta Business Settings: under Integrations for the login connection, and under Partners for the partner access.
• The client’s account in the app holds what is needed to run the program, such as the intake answers, the offer report, the tests and their results, and the name and email of each person with access.
• The app emails the people with access that we set up with the agency: the login email, the intake invitation and reminders, reminders to connect the Meta ad account, an email to connect it again if the connection stops working, a note when the offer report is ready, a note when a test is ready for review and when a test or campaign goes live and, when asked, a password reset email. Each one goes out in the agency’s name, or as 1Signal, from our team’s address. When the agency gives us a reply address, replies go there, and that address gets a short note when the client has connected its Meta ad account.
• Our app and our sales systems send a person in a client program no other email. Program emails are not copied into our CRM, and taking part in a program does not add anyone to our CRM, our newsletter or our sales follow up.
• We keep a working profile with each client’s record, built from the intake answers, the offer report, the test results, the ad account summaries above and, where a call was recorded, summaries of that call.
• The offer report, the test copy drafts, the analyses and the Lab suggestions are written with an AI model (Anthropic) from the client’s intake answers, website, test results and working profile. To research the offer report, web research services (Firecrawl, Apify and Exa) read the client’s website and search public comments in its market with search phrases built from the intake.
• For the Image step, image services (Higgsfield and Pikzels) draft pictures from prompts built from the client’s test brief. Test images and other program files are stored with our file storage providers, DigitalOcean (Spaces) and Vercel (Blob).

Leads from a client’s campaigns

A lead is a person who answers one of a client’s ads, on the client’s landing page or in a Meta lead form. We handle a lead’s data for the client: to deliver the lead to the client and to help the client see which leads are worth a call. We switch each step below on per client, so not every step runs for every client.

What we receive

• From a landing page: the answers the lead types into the form (usually name, email, phone number, company and the client’s qualifying questions), the address of the page, the utm campaign parameters in that address, which name the ad, and Meta’s click and browser identifiers when the page sends them.
• From a Meta lead form: the answers the lead gave in the form, when it was sent, and the ad, ad set and form it came from. We fetch these from Meta when Meta tells us a new lead arrived. Meta’s own test leads are dropped.
• We do not store a lead’s IP address or browser details. Our server keeps the IP address in its working memory to limit repeated submissions, and passes both to Meta for the client’s own pixel, as described below.
• If the same email address sends the form again, the newer answers are added to the same record.

What happens to it

• The lead is saved in our database with the client’s record. The client and its agency see their leads in the app.
• Phone check: when a client asks for a phone number, Twilio checks that the number works and whether it is a mobile, landline or internet number.
• Rules: for some clients, fixed rules sort the lead into A, B or C from its answers. No AI is involved in this step.
• Lookup: for some clients, when the form does not say where the lead works, we look it up. AirScale receives the part of a work email address after the @, or the lead’s name, or for a personal email address the full address. LeadMagic receives the email address to find a LinkedIn profile. We store the company, its size and industry, the job title and the LinkedIn profile that come back. The AI fit check below runs the same lookup by email for a lead that gave no company and no role.
• Email check: for a client that has it switched on, AirScale also receives the lead’s email address to check whether it exists, so we can tell the agency that mail to it will bounce. We store only the result (valid, invalid, catch-all or unknown) and when we checked it. It never blocks a lead.
• AI fit check: when a client’s offer has a buyer profile on record, each of its leads gets an A, B or C grade from an AI model (Anthropic) against that profile. The model receives the lead’s name, the part of its email address after the @ (never the full address), its company, role, industry, company size and country, the ad it came from, whether it booked a call, its form answers (which can include its phone number) and any lookup results. We store the grade, a short reason and the facts the model received.
• Alerts: our team gets an email for each new lead with its details and answers, and a record of it is kept in our internal notification list. Where we set it up for a client, the same details go to the client’s own inbox, or to its sales person by email, text or WhatsApp message.
• Meta: when a client’s page has its pixel set up, our server sends a Lead event to the client’s own Meta pixel, never to FounderScale’s. The event carries the lead’s email, phone number, first and last name and city in hashed form, and its IP address, browser details, page address and Meta identifiers. A Schedule event can follow when the lead books a call. For some clients a lead graded C is not sent.
• Email to the lead: when the page promises something, such as a guide, a report or a booking link, we email it to the lead through Resend, in the client’s name. On some pages the lead also gets a text with a booking link.

The voice agent

For clients where we set it up, an AI voice agent built on Retell calls new leads at the phone number they gave in the form. The first call comes about 10 minutes after the form arrives. It tries again over the next three days, at most five calls in all, and only between 9:00 and 20:00 in the lead’s time zone. It never calls a lead who already booked, a number found not to work, a lead older than nine days or a lead graded C. Retell receives the lead’s phone number, first name, email and company, and our own numbers for the lead and the client.

The agent asks a few qualifying questions, such as what kind of business it is and who decides, and can book a call with the client’s team. The booking is an event in the host’s Google Calendar: the lead is added as a guest, gets the invitation, and the event holds the lead’s name and email, plus the phone number for a phone meeting.

Retell records and transcribes each call and keeps the recording and the transcript under its own settings. We read the transcript to grade the call: an AI model (Anthropic) reads it unless the agent’s own answers already settle the grade. A call grade counts only with a short quote of the lead’s own words, which we store with the grade. A copy of a call’s transcript can also be kept in our file storage. We do not copy the recording.

Reminders for a booked call

• When a lead books through the voice agent or its booking link, we read the booking from the host’s Google Calendar and remind the lead: by text through Twilio, by email through Resend and with a short reminder call through Retell. The messages carry the lead’s first name, the host, the time and the video call link. Texts, apart from the one confirming the booking, go out only between 6:00 and 23:00 in the lead’s time zone.
• After a missed call, the agent can call the lead up to three times in the next five days.
• We store which messages were sent, to which number, and whether they arrived. We do not store the text of the messages we send.
• When a lead answers a text, the reply goes to the client’s sales person and to our team. A yes marks the call confirmed; a reply that cancels or moves the call stops the reminders for it. A lead who replies STOP gets no more texts from that number, and we switch to email.
• For these leads, we also check our own CRM (HubSpot) for a booking and note call outcomes there.

The client’s CRM and our CRM

• A client can connect its own CRM (Attio today) with a key. We keep the key on our servers and never show it in a browser; a key entered in the app is stored encrypted. We then add each new lead to the client’s CRM: a person with name, email and phone, a company from the email address, a note with the answers, the page, the ad and the lookup summary, and an entry in the client’s lead list. We read back the stage of each entry to learn how the client judged the lead. The client can disconnect at any time, which deletes the stored key.
• For one client’s leads, the lead’s name, email, phone number, company and qualifying answers are also added to our own CRM (HubSpot).

The client’s review page

We can send a client a private link to a page that lists its leads from the last 60 days with each lead’s company, name, date and ad. The client marks each lead Fit, Not fit or Became a customer, with the deal value if it wants, and that verdict overrules every other grade. The page shows no email, phone number, answers or grade, loads nothing from any other site, and its link stops working after 30 days or as soon as we replace it.

How long we keep it, and how a lead can ask for deletion

We keep a lead’s record, its grades, the records of messages and calls and the copies in our alerts until the client or the lead asks us to delete them. There is no automatic deletion schedule. A lead can ask by emailing [email protected]; the steps are on the data deletion page. What the client holds in its own CRM, inbox or calendar is the client’s to delete.

The 1Signal app

The Log in link on this site opens the 1Signal app at app.1signal.io, which we run. Agencies and the clients in their programs sign in there, and the links in program emails open there. The app loads no analytics, no Meta pixel, no Google tag, no session recording and no chat or voice widget, and it asks for no consent because it sets none of them. Its typefaces are served from our own server.

The app keeps you signed in with a cookie it needs to work, and your browser may keep your sign in in its localStorage. When a client outside a program finishes the intake questions, our server sends a registration event to FounderScale’s Meta pixel with the client’s email address (hashed), IP address and browser details. It sends none for a client in a program.

The app replaced the program portal on founderscale.ceo, which loaded Meta pixels, Google Analytics, Microsoft Clarity, PostHog, a live chat and a voice assistant. Its old addresses now open the matching page in the app. Data those tools received before the switch stays with them until it is deleted; see Your choices.

Call recordings

Our team records some calls with Fathom, a meeting recorder. If we record a call with an agency or a client, we keep the transcript as notes for the program. For a client in a program, summaries of its recorded calls (decisions, commitments, concerns and action items) may also be stored with that client’s record. Fathom’s own link to our CRM (HubSpot) can log a summary of a recorded call there, including a call with a client in a program. No test is generated from a recording.

Who receives data

We do not sell personal information. We share it with these recipients:

• Hosting, storage and delivery: DigitalOcean, which runs the site and our servers and stores program images and files, Vercel, whose Blob storage also holds program images and files, and Cloudflare, which carries every request to them and sets the security cookie described above.
• Database: Neon, which stores applications, program data and our internal notification list.
• Email: Resend, which delivers the alert emails to our team, the program emails to people in a client program, sent in the agency’s name or as 1Signal, and the emails to a client’s leads, and Google Workspace, which runs our team’s email and calendar: application alerts arrive there, as do emails you send us and meeting invitations.
• Text and WhatsApp messages: Twilio, which carries the alert to our team when an application could not be saved, checks a lead’s phone number, and carries the texts to a client’s leads and the lead alerts to a client’s sales person.
• CRM: HubSpot, which holds our records of the agencies we talk to, can hold summaries of calls we record and holds the leads described above. Emails the app sends to people in a client program are not copied to it.
• AI model: Anthropic, for the program work and the lead grades described above.
• Voice agent: Retell, which places the voice agent’s calls to a client’s leads and records and transcribes them.
• Lead lookup: AirScale and LeadMagic, for the lookup described above.
• The client’s CRM: Attio, when a client connects its own Attio workspace.
• Calendar: Google Calendar, which holds the calls the voice agent books.
• Image services: Higgsfield and Pikzels, for the Image step described above.
• Web research: Firecrawl, Apify and Exa, for the offer report research described above.
• Meeting recorder: Fathom, for calls we record.
• Error and performance monitoring: Sentry, which receives technical details of a request when something on our servers fails and timing data for a sample of requests.
• Analytics on 1signal.io, only if you accept: PostHog and Microsoft Clarity.
• Meta, for the ad accounts connected to a program, the lead forms and the lead events sent to a client’s own pixel described above, and for the intake registration event described under The 1Signal app, and for the optional application measurement described above.
• Anyone the law requires us to share it with.

Your choices

You can ask to see, correct or delete the data we hold about you by emailing [email protected]. The steps for deletion are on the data deletion page.

Children

1signal.io is for agencies and businesses. It is not meant for children, and we do not knowingly collect data from them.

Changes to this policy

If this policy changes, the new version is posted on this page with a new effective date.

Contact