About this policy
This policy explains what personal data Belo collects, why, how long we keep it and what choices you have. Belo is a marketing platform for small and medium businesses. Today it offers a CRM for leads; landing pages and websites with forms, which we host for the business; visit measurement and A/B tests on those pages; writing and images with artificial intelligence (AI); planning of social media content; and account notifications. Connecting the business’s Meta (Facebook and Instagram) account, to show its campaigns and their results and to bring leads from its lead forms into the CRM, is being tested with internal test businesses of ours and is not available to customers yet.
Belo is operated by the company named under “Who we are” at the end of this page. “We” in this policy means that company.
We wrote this policy for the Israeli Privacy Protection Law, 5741-1981, including Amendment 13, and the Privacy Protection (Data Security) Regulations, 5777-2017. Because our database is hosted in the European Union, we also follow the EU General Data Protection Regulation (GDPR) where it applies to you.
Whose data, and our role
Belo is used by businesses that subscribe to it (“customers”) and by the people they invite (“team members”). For account, team, billing and security data, we decide how the data is processed: we are its controller (in Israeli law, the controller of the database).
The leads and customer records a business keeps in Belo, and the details of other people it adds to its Business Brain and pages (such as team members and customer testimonials), belong to that business, which is their controller. We process them only on the business’s behalf and according to its instructions, as its processor (in Israeli law, a holder), under the data processing section of our terms of service. The business is responsible for collecting them lawfully, including any notice and consent it needs.
If you are a lead of one of our customers, please contact that business first; we will help it handle your request.
What we collect
- Account data: your email address, an optional display name, your language preference, your role in each business and sign-in records, including the IP address and the browser and device of each signed-in session (you can see and end your sessions in the app). Passwords are handled by our authentication provider and stored only in hashed form.
- Invitations: the email address and role of each person a business invites to Belo.
- Business data (the Business Brain): the business name and the information you enter about the business, such as its description, offers and prices, audiences, goals, phone and WhatsApp numbers, website, locations and opening hours, frequently asked questions and competitors; team members (name, role, a short bio and a photo, with a record of each person’s consent to use the photo); testimonials and customer quotes; and the photos, logos and other media you upload or create with AI.
- Leads (CRM): the details people send to the business through the forms on its pages and through Meta lead ads, and leads the business adds by hand or imports from a CSV file. These include name, phone number, email address, message and answers to the business’s own form questions; where the lead came from (the full address of the page and of the page that referred the visitor, campaign tags (UTM), ad click identifiers such as fbclid and gclid, and the page version in an A/B test); and the lead’s status, notes, follow-ups, assigned team member, expected and actual deal value and any consent the business recorded.
- Data from Meta, only if the business connects its Meta account (see the next section).
- AI chat history: the requests you type in a page’s AI chat and Belo’s short replies, with email addresses and phone numbers masked. For each AI request we also record its type, the business, who asked and its cost, without the text that was sent or received.
- Billing data: the plan, payments, invoices and receipts, and, once they are on sale, purchases of AI credit packs. Card details are entered on the payment provider’s page; we keep only the provider’s token reference, the card brand, the last four digits and the expiry date, never the full card number or security code.
- Email delivery data: the recipient’s address and whether our emails were delivered, bounced or marked as spam, so that we stop sending to addresses that cannot receive them. Our emails do not track whether they were opened or which links were clicked.
- Developer access (off unless turned on for a business): API keys, stored only as a one-way hash, and the addresses of the webhook endpoints the business sets up.
- Technical and security data: server logs and an audit trail of important account actions (who did what, and when). Secrets are removed from logs, and email addresses and phone numbers in them are masked.
You are not required by law to give us this data, but without account, business and billing data we cannot provide the service.
Data from Meta (Facebook and Instagram)
An owner or administrator of a business can connect the business’s Meta account to Belo with Facebook Login. Belo then asks Meta for the permissions below and uses each one only for the purpose shown:
- ads_readRead the business’s ad accounts, campaigns, ad sets, ads and their results (spend, impressions, clicks and leads) to show them in Belo.
- ads_managementMake the campaign changes the business asks for: pause and resume campaigns, change budgets and names (for one campaign or several at once, or under automation rules the business turns on), delete paused campaigns, and create new campaigns as paused drafts; and report lead results to Meta’s Conversions API (see below). These actions are not available to customers yet. Changing paused campaigns and creating paused campaigns are switched on only in Belo’s internal test businesses, where they were tested on paused test objects; resuming a campaign and reporting lead results have not been used there.
- business_managementAccess the ad accounts and pages that the person who connects grants to Belo, and read the names and IDs of their business portfolios, to show which portfolio Belo is connected to. Belo does not read the portfolio’s users or settings.
- pages_show_listList the business’s Facebook pages so that it can choose which ones Belo uses.
- pages_read_engagementRead basic information about the chosen pages, obtain the page access token Belo needs to work with them, and list their lead forms. Where the import of existing content (see Social publishing below) is switched on for a business, also read the posts already on the chosen pages, without changing them.
- pages_manage_metadataSubscribe a chosen page to lead notifications, so new leads reach Belo.
- leads_retrievalRead the lead form submissions of the chosen pages and add them to the business’s CRM.
- pages_manage_adsList the lead forms (instant forms) of the chosen pages, so that the business can see them and choose one, and attach the chosen form to a lead ad that Belo creates for the business as a paused draft. Campaign creation is not available to customers yet; in Belo’s internal test businesses the campaign and its ad set were created paused, and Meta does not yet allow the ad itself while Belo’s app is in development mode. Meta requires this permission, together with lead retrieval, to work with lead ads.
Social publishing: Belo asks for the nine permissions below only for a business that Belo has set up for social publishing. For that business, Belo uses a separate Facebook Login configuration that includes them, and an owner or administrator is asked for them when connecting or reconnecting Meta. Every other business is asked only for the permissions above. Today this is set up only for an internal test business of ours, which publishes test posts to Belo’s own test Page and Instagram account.
- instagram_basicFind the Instagram professional account linked to a chosen Page (its ID and username), so that the business can choose it as a channel, and read the link of each post Belo published there and, where the import of existing content is switched on, list the account’s existing posts. Meta requires this permission together with the other Instagram permissions in this list.
- instagram_content_publishPublish the posts approved in Belo to the Instagram professional account the business chose: an image, a carousel of images, a Reel or a Story.
- instagram_manage_commentsRead the comments on the Instagram posts Belo published and, where the import of existing content is switched on, on the account’s other posts; and, when the business’s team asks for it in Belo, reply to a comment, hide it, show it again or delete it, and turn comments off or on for a post Belo published.
- instagram_manage_contentsDelete a post Belo published to the Instagram account, when an owner or administrator of the business asks for it in Belo.
- instagram_manage_insightsRead the metrics of the Instagram posts Belo published (such as reach, views, likes, comments, shares and saves), to show the business how each post did.
- pages_manage_engagementReply to, hide, show again or delete comments on the Facebook posts Belo published and, where the import of existing content is switched on, on the Page’s other posts; and change the text of a post Belo published or delete it. Each only when the business’s team asks for it in Belo.
- pages_manage_postsPublish the posts approved in Belo to the Facebook Page the business chose (text, photos, videos, Reels and Stories), and change the text of such a post or delete it when the business’s team asks for it in Belo.
- pages_read_user_contentRead the comments people write on the Facebook posts Belo published and, where the import of existing content is switched on, on the Page’s other posts, so the business’s team can see them in Belo and answer them.
- read_insightsRead the metrics of the Facebook posts, videos and Reels Belo published (such as views, reach, clicks and reactions), to show the business how each post did.
From Meta we store: the Meta user ID and name of the person who connected, the permissions granted or declined, the access token, the names and IDs of that person’s business portfolios, the chosen ad accounts, pages, pixels and lead forms, and the Instagram professional account linked to a page (its ID and username); the campaign structure, with the ad texts and the addresses of the ad images; daily advertising results, including reach and frequency, and aggregated breakdowns by age, gender and placement; a history of changes to campaigns; records of synchronisation runs and of the notifications Meta sends us; and lead form submissions.
For social publishing, Belo stores the Facebook Pages and Instagram accounts the business chose (their IDs and names) and, for each post Belo published: its ID at Meta and, where Meta gives one, its link; its format; when it was published; whether it was later changed or deleted at Meta, or its comments were turned off; and its metrics as Meta reports them (such as reach, views, reactions, comments, shares, saves and clicks), read about 1 hour, 24 hours, 7 days and 28 days after publishing.
Belo also stores the comments on those posts and the replies to them, including the Page’s or account’s own replies: each comment’s ID, the commenter’s name as Meta gives it (a Facebook name or an Instagram username; Meta may leave it out), the text, the time, the number of likes, whether it is hidden, and Belo’s own marks on it (answered, handled, or needing attention because of the words in it). It also records the actions the business’s team takes in Belo, with who asked and when: replying to a comment (with the reply’s text), hiding it, showing it again or deleting it; and changing a post’s text (with the new text), turning its comments off or on, or deleting the post.
Belo reads metrics only for posts it published. It reads comments on the posts it published and, where the import of existing content described below is switched on, on the other posts of the Page and Instagram account; always only on the Page and Instagram account the business chose. It does not store a commenter’s Meta user ID or profile picture, and it does not read the Page’s messages or who its followers are. This data is kept for that business only; in Belo, only its owners, administrators and marketing team members can see it.
Existing content (not switched on for any business yet): where this is switched on for a business, Belo also reads, without changing them, the posts already on the chosen Page and Instagram account, including posts made before Belo was connected or outside Belo, scheduled posts and posts used in the business’s ads, even ones that appear only in ads. For each such post it stores its ID at Meta and its link, its text (up to 2,000 characters), its format, its times, whether it is published or scheduled, whether it is used in an ad and, on Instagram, the numbers of comments and likes Meta gives; it does not store their images or videos, only the address of a preview image on Meta’s servers, which expires and which the browser loads from Meta. It also reads, a few times a day, the number of followers of the chosen Page and Instagram account and the number of posts in the Instagram profile, and keeps one count per day. Belo reads their comments too, as described above. A comment written before Belo first read its post is kept as history: Belo never replies to it, hides it or deletes it on its own. When the business stops choosing a Page or Instagram account, Belo deletes the posts, comments and follower counts it imported from it.
To publish, Belo sends Meta the post’s text, if any, and its photos or video; Meta fetches the files through a temporary link that stops working after one hour. When the business’s team replies to a comment or changes a post’s text, Belo sends that text to Meta.
The access token is encrypted (AES-256-GCM) before it is stored, with a key kept outside the database. It is never shown in the app or written to logs. Belo’s screens show data that was synchronised from Meta and stored by us; they do not query Meta while you browse. The one exception is ad images: Belo shows them directly from Meta’s servers, so your browser contacts Meta when it displays an ad preview.
We use data received from Meta only to provide Belo to the business that connected it. We do not sell it and we do not use it to build advertising profiles.
Campaign actions run only at the request of an authorised team member, or under automation rules the business turns on, within the limits the business sets. Automation rules only send notifications unless the business decides otherwise. Today they are switched on only in Belo’s internal test businesses, where they were used only on paused test objects.
Belo publishes a post only after it is approved in Belo: by a person or, where an owner or administrator turned this on, automatically when the approval deadline passes. Belo replies to, hides, shows again or deletes a comment, and changes or deletes a published post, only when the business’s team asks for it in Belo. Automatic handling of comments by AI is off. Belo never changes or deletes a post it did not publish.
If you remove Belo from Facebook
When the person who connected Facebook removes Belo in their Facebook settings and asks for their data to be deleted, Facebook sends us a deletion request and we act on it at once:
- Removed: the access token, the link between the business’s Belo account and your Facebook identity (your Facebook user ID and name), and your Facebook user ID in our records of your Facebook permission changes (those records are deleted after 90 days in any case).
- Kept: the advertising reports and leads already synchronised for the business, and its social publishing records (the posts Belo published for it, their metrics, and the comments on them with each commenter’s name as Meta gave it, including any comment you wrote yourself), which belong to the business’s account and are deleted when the business asks us to; and security audit records and billing records, which we must keep. The audit records do not contain your Facebook user ID.
Why: these records belong to the business’s own ad accounts, Pages and customer relationships, not to the Facebook user who connected them, and the business needs them for its own records and obligations.
Reporting lead results to Meta (off unless the business turns it on)
Belo can tell Meta which leads became real customers (Meta’s Conversions API), so that Meta shows the business’s ads to people who are more likely to become customers.
This feature is off. It is not active in Belo today, and once it is available it stays off for each business until an owner or administrator of that business turns it on and accepts the section of our terms of service that covers it. When it is on, Belo sends:
- Leads that came from the business’s Meta lead forms, identified to Meta only by Meta’s own lead ID (no email address or phone number is sent).
- Other leads only if the business recorded the lead’s explicit consent. They are identified by a one-way hash (SHA-256) of the email address and phone number, calculated in our database; the readable email address and phone number are not sent.
- Nothing about any other lead. A lead recorded as not consenting is never sent.
The stages reported by default, with their Meta event names:
- LeadA new lead arrived.
- ContactedThe business contacted the lead.
- QualifiedLeadThe business marked the lead as relevant.
- ScheduleA meeting was scheduled.
- PurchaseThe lead became a customer, with the deal value and currency.
Leads marked as lost are not reported, and each stage is reported at most once per lead. We keep a record of what was sent and when, without the contact details or their hashes. The business can change the reported stages or turn the feature off at any time.
For these leads the business is the controller and decides whether to use the feature. It is responsible for telling its leads about it and for any consent the law requires.
Visit measurement on sites and landing pages businesses publish with Belo
A landing page or website a business publishes with Belo includes basic visit measurement: how many page views and visitors there were, on which pages, what kind of source they came from (for example search, social media or a campaign), and how many visitors saw a form, clicked a button or sent a form. For this data the business is the controller; we process it only on its behalf and on its instructions, as a processor.
We do the measurement ourselves, without cookies, without storage in the browser and without third-party code. The visitor’s IP address and browser details (User-Agent) are not stored: they are used only to limit abuse and to count a visitor once per day, through a one-way hash with a secret key and a random daily value that is deleted after two days, so the same person’s visits cannot be linked across days or across sites. In the visit measurement, only the name of the referring site is kept, not the full address of the page the visitor came from. If the visitor sends a form, the lead the business receives keeps more about the visit: the full address of the page and of the referring page, campaign tags (UTM) and ad click identifiers.
If the business runs an A/B test, each visitor is shown one version of the page based on a calculation made in memory from the IP address and browser details, without storing them and without a cookie. The version shown is stored with the visit and, if the visitor sends a form, with the lead, so the business can see which version brought more enquiries.
The visit events themselves are kept for up to 14 days; daily totals, which contain nothing about individuals, are kept for about 26 months. Visitors who block JavaScript, and robots and automated tools we recognise, are not counted.
The pages are delivered by our hosting provider, which processes each visitor’s request, including the IP address, to serve the page. A page loads no third-party code, but an image the business adds from another website’s address is loaded from that website.
How we use data
- To provide Belo: sign-in, the CRM, the business’s pages and forms, reports, AI features, notifications and support.
- To bill subscriptions and issue invoices.
- To send service emails, such as invitations, security and billing messages, and the notifications you choose.
- To keep the service secure: preventing abuse, investigating incidents and keeping an audit trail.
- To meet legal obligations, such as accounting and tax rules.
We do not sell personal data, and we do not use a business’s leads or Meta data for anything other than providing Belo to that business.
Insights and recommendations in Belo are calculated by fixed rules from the business’s own data. Features that write text or create images with AI use outside providers, as described in the next section.
Artificial intelligence (AI) features
Some Belo features use outside AI providers: Anthropic (Claude) writes and edits text, and OpenAI creates images. Belo’s site writer is on by default: when a business builds a site, Belo writes its first texts with AI. Other AI features, such as editing a page in the AI chat and the AI studio, are available only where they are turned on for the business.
What is sent to these providers:
- The business’s details from the Business Brain that the task needs, such as its name, description, services, offers, audiences, tone and frequently asked questions. Testimonials and competitors from the Business Brain, and prices the business marked as private, are not sent.
- The text of the business’s pages, when Belo writes or edits them. It can include names and quotes that already appear on a page, for example in a reviews or team section.
- The requests a person types in the AI chat, and the descriptions and tags of photos a request refers to (not the photos themselves).
- For images: the scene description a person types, or a scene Belo builds from the business’s industry, and, when the text is drawn into the image, the headline. An image the provider creates may be sent to Anthropic to check the text in it.
Before text is sent, email addresses and phone numbers in it are replaced with placeholders. The only exception is the business’s own phone number, which a social media caption or reply may need.
No lead record from the CRM is sent to an AI provider, and photos you upload are not sent to the image provider.
A feature that classifies public comments on the business’s social media pages and suggests replies would send the comment text, without the commenter’s name. It is off.
Requests typed in the AI chat and Belo’s replies are kept for up to 90 days, at most 200 per page. For other AI requests we keep a usage record (type, cost and who asked) without the text sent; the text the AI writes is saved where it is used, for example on the page.
Legal bases (where the GDPR applies)
Where the GDPR applies, we rely on these legal bases:
- Performing our contract with the customer, and steps before it: accounts, the service, support and billing.
- Our legitimate interests in keeping the service secure, preventing abuse, and supporting and improving the service, balanced against your rights.
- Legal obligations, such as accounting, tax and answering lawful requests.
- Consent, where we ask for it. You can withdraw it at any time; this does not affect processing that already took place.
Service providers
We use these providers to run Belo. They process data on our behalf, only for the purposes below:
- SupabaseDatabase, sign-in, file storage (such as uploaded photos), server functions, scheduled jobs and daily backups (kept for 7 days); it also sends the sign-in emails, such as password reset and sign-in links. The database is hosted in the European Union (Frankfurt region).
- VercelHosting of the Belo web application and of the pages and websites businesses publish with Belo (it processes each visitor’s request, including the IP address), and the DNS service for the usebelo.com domain.
- PostmarkSending service email, such as invitations, notifications and billing messages. It receives the recipient’s address and name and the content of the message, which can include, in a new-lead alert, the lead’s name (or, when the lead has no name, its phone number or email address), or the address of a person invited to a business.
- iCountPayment processing and invoicing. The card is entered on iCount’s own payment page and its details stay with iCount; we send iCount the business name and an internal account reference. iCount issues the invoices and receipts and sends them by email.
- AnthropicAI text (Claude): writing and editing texts and checking the text in AI-generated images, as described under “Artificial intelligence (AI) features”.
- OpenAIAI images: creating images from a scene description, as described under “Artificial intelligence (AI) features”.
- GitHubHosting of our source code and automated jobs, such as tests, a monthly test that restores a backup of our development database, and maintenance tasks. These jobs run on GitHub’s servers and may process data while they run.
- Forward EmailReceives email sent to our support and privacy addresses on usebelo.com and forwards it to our team’s mailbox. It processes the sender’s address and the content of the message.
- MetaOnly when a business connects it, as described above.
Our database is in the European Union. We have not yet confirmed in which countries each of the other providers processes data; it may include countries outside Israel and the European Union, such as the United States. Israel and the European Union recognise each other’s level of data protection as adequate. For transfers to other countries the law requires safeguards, such as the European Commission’s standard contractual clauses; we have not yet confirmed them with every provider.
If we add or replace a provider that processes personal data, we will update this list.
We may also disclose data when the law or a competent authority requires us to.
Security
- Data travels over encrypted connections (HTTPS).
- Each business’s data is separated from other businesses’ data in the database itself, and this separation is tested automatically.
- Meta access tokens are encrypted with a key kept outside the database.
- API keys, invitation links and deletion confirmation codes are stored only as one-way hashes.
- Our staff need a second sign-in factor to use the admin console, and staff actions are recorded. When staff look into an account to help with a support request, the access is read-only, needs a recorded reason, lasts at most 60 minutes and is visible to the business.
- Card details are entered only on the payment provider’s page and never reach our servers.
Our security measures are designed with the Privacy Protection (Data Security) Regulations, 5777-2017 in mind: access is limited to people who need it, important actions are recorded, backups are taken daily, and an automated test checks every month that a copy of the database can be restored.
No system is completely secure. If we learn of a security incident that affects your data, we will notify you, the Privacy Protection Authority and any other authority as the law requires.
How long we keep data
- Account, business and lead data, including the business’s pages and their versions, media, notifications and invitations: kept while the business’s account is active, and deleted when the business asks us to. No fixed period has been set yet.
- Meta data: while the connection is active. When a business disconnects Meta in Belo, synchronisation stops, and the encrypted access token is kept for up to 24 hours only so that Belo can withdraw its access at Meta, and is then erased. The same applies to the previous person’s token when someone else reconnects the business’s Meta account. The Meta user ID and name of the person who connected stay on the disconnected connection until that person asks for their data to be deleted. When the person who connected removes Belo in their Facebook settings, the access token is deleted at once and synchronisation stops. Advertising results already synchronised stay part of the business’s reports until the business asks us to delete them.
- Records of notifications from Meta: 90 days. Breakdowns of advertising results by age, gender and placement: 60 days. Records of synchronisation runs: 30 days. Records of Facebook data deletion requests, which contain no Facebook user ID: 730 days.
- Social publishing: the posts Belo published, with their Meta IDs, links and metrics, are kept while the business’s account is active, like other business data. Belo is built to delete comments, the actions on them and requests to change a published post 365 days after the comment was written or the request was made; this automatic deletion is not switched on yet, so until it is, they are kept like other business data. While Meta is disconnected, including after the person who connected removes Belo in Facebook or asks Facebook to delete their data, Belo publishes nothing and reads no metrics or comments, and the data already stored stays in the business’s account. Imported existing content (not switched on yet) is kept while the business chooses the Page or Instagram account it came from, and is deleted when the business stops choosing it.
- Visit measurement on published pages: visit events up to 14 days, and daily totals about 26 months.
- Records of form submissions on published pages (the page, the form version and whether consent was given, without the answers): 400 days. The answers are kept with the lead.
- Email delivery events, with the recipient’s address: 180 days. Addresses that bounced or marked our email as spam stay on a suppression list, without a fixed end date, so that we do not send to them again.
- AI chat messages: up to 90 days, and at most the newest 200 per page.
- Contacts imported from a CSV file: the contact data of each row is deleted from the import as soon as the row is processed, an import that was never started is deleted after 24 hours, and the import report is deleted 30 days after the import ends.
- Audit and security records: kept without a fixed end date and protected from change, to investigate incidents and show what happened. They are kept even when other data of the business is deleted.
- Billing records and invoices: for as long as accounting and tax law requires.
- Backups: our database provider keeps daily backups for 7 days, so deleted data can remain in a backup for up to 7 days after it is deleted.
- Server logs: kept according to our hosting providers’ settings; we have not set a period of our own.
- Closed accounts: there is no automatic deletion yet. When a business asks us to close its account or delete its data, our team does it manually, except billing and invoice records that the law requires us to keep.
Where a deletion step is not yet automated, our team carries it out on request.
Your rights
Under the Israeli Privacy Protection Law and, where it applies, the GDPR, you may have these rights:
- To see the personal data we hold about you.
- To ask us to correct data that is wrong, incomplete, unclear or out of date.
- To ask us to delete your data, except data we must keep by law (for example, invoices) or for a legal claim.
- To receive data you gave us in a common, machine-readable format. Owners and administrators can export the business’s leads to a CSV file in the app; we prepare other data on request.
- To object to or restrict some uses of your data, and to be removed from direct marketing.
- To withdraw consent you gave, at any time.
To make a request, email the privacy address under “Who we are”. We may first need to confirm your identity. We answer within 30 days, or sooner where the law requires.
If your data is in Belo because a business uses Belo (for example, you are one of its leads), that business decides on your request; we will pass it on or handle it together with the business.
You may also complain to the Privacy Protection Authority in Israel or, in the European Union, to the data protection authority where you live or work.
To delete the data Belo received from your Facebook account, see the data deletion page.
Service messages and marketing
We send service messages that are part of the service, such as invitations, security alerts, billing messages and the notifications you choose. You can change your notification preferences in the app; some security and billing messages are always sent while you use Belo.
We send advertising about Belo by email, text message or similar means only with your prior consent or as section 30A of the Communications (Telecommunications and Broadcasting) Law, 5742-1982 allows. Every such message says that it is advertising and lets you unsubscribe at any time, free of charge.
Cookies and local storage
Belo does not use advertising or analytics cookies, and it does not load third-party trackers or advertising pixels.
The app keeps only what it needs to work in your browser’s local storage:
- Your sign-in session, so that you stay signed in, and a temporary security value used while you sign in.
- Your language choice (Hebrew or English).
- The business you last selected, if you belong to more than one.
- An invitation link you opened, until you accept it.
- Display choices, such as light or dark mode and hiding the setup checklist.
- Your recent searches in each business, which can include names or phone numbers you searched for.
- Changes to a page you are editing that are not yet saved, kept on your device while you are offline until they can be saved.
This data stays on your device. Signing out ends the session, and you can remove the rest by clearing this site’s data in your browser. Because these items are needed for the service to work or record your own choices, we do not ask for cookie consent.
When an owner or administrator connects Meta, Belo opens Facebook’s own sign-in page, where Meta’s cookies and policies apply. Ad previews are loaded from Meta’s servers (see “Data from Meta”).
Children
Belo is a service for businesses and is not intended for people under 18.
Changes to this policy
We will publish any change on this page with a new “last updated” date, and tell account owners by email or in the app before a significant change takes effect.
Who we are and how to contact us
Belo is a service operated by the company whose details appear here.
- Operator (legal entity)
- B.D.Y Yazamut VeHashkaot Ltd. (ב.ד.י יזמות והשקעות בע״מ)
- Company registration number
- 516898467
- Registered address
- 2 HaHagana St., Kiryat Bialik 2701602, Israel
- Privacy and data requests
- privacy@usebelo.com
- Support, billing and cancellation
- support@usebelo.com