UOS

UOS Privacy Policy

Effective date: 18 November 2026

UOS (https://uos.co.il) is a team of AI assistants that runs on a business's own computer and works with the business's own tools. It is operated by Ubiz Marketing Agency ("UBIZ", "we"), Israel. On Meta's login and settings screens it appears as "UOS by UBIZ".

This policy covers the data UOS receives when a business ("customer") connects its own advertising account to UOS through our connection service at https://connect.uos.co.il.

1. Who is responsible

The customer is the controller of the data in its advertising accounts. UBIZ processes that data only on the customer's behalf, to provide the features the customer turned on. Each customer's connection is separate from every other customer's.

2. Data we receive from Meta

When a customer connects

The person connecting signs in with Facebook Login for Business and chooses which ad accounts to share with UOS. Meta then gives UOS an access token. We store:

While an ad account is connected

We do not request or receive data about individual people: no audience or customer lists, no lead form answers, no comments or messages, and no profile data beyond the ID of the person or integration that connected the account.

The permissions we ask for, and why

PermissionWhat UOS uses it for
ads_readRead the campaigns, ad sets, ads and performance of the ad accounts the customer shared, so the customer and its assistant can see how they perform
ads_managementPause or resume a campaign, ad set or ad, or change its budget, and only after the business owner approves that specific change in UOS
business_managementList the ad accounts the person manages through a business portfolio, so the customer can choose which to connect

3. How we use it

UOS never creates campaigns, ads or audiences, never changes payment methods or account settings, and cannot raise a budget to more than twice its current value in one change. We do not sell data, use it for our own advertising, build profiles, or share it with anyone other than the providers in section 4.

4. Where the data goes

WhereWhat happens there
Our connection service (Cloudflare, Inc., database in the European Union)Stores the encrypted access token and the list of shared ad accounts. It requests data from Meta when the customer's UOS computer asks for it, and passes it on without storing it. It keeps a record of each change it made or refused (section 5).
The customer's own computerReceives the campaign and performance data and keeps it in the customer's UOS business folder, under the customer's control. The customer's assistants read it there with Claude, an AI model by Anthropic, using the customer's own Claude subscription and under the customer's own agreement with Anthropic.

UBIZ itself does not send data received from Meta to any AI model, and the access token never leaves our connection service.

5. How long we keep it

DataRetention
Access token and list of shared ad accountsWhile the account is connected. Deleted immediately when the customer disconnects in UOS, removes "UOS by UBIZ" from its Meta business settings, ends its UOS subscription, or when Meta tells us the token is no longer valid
Campaign and performance data on our connection serviceNot stored. Passed to the customer's computer when requested
Record of each change made or refused (object, action, value before and after, time, and a reference to the owner's approval)12 months, so the customer can see what was changed in its account
Records of deletion requests from Meta12 months

Data on the customer's own computer stays under the customer's control and is deleted by the customer.

6. Security

Access tokens are encrypted at rest with a key kept separately from the database, so a copy of the database alone cannot open any account. Tokens are never sent to the customer's computer or browser. Every request from a customer's computer is signed with a key that exists only on that computer, and the connection service accepts only computers we registered. The service can perform only the reading and the three kinds of changes described in section 3, whatever it is asked. All traffic is encrypted with HTTPS, and every notification from Meta is verified with Meta's signature.

7. Access and deletion

8. Requests from public authorities

We disclose data to a public authority only when the law requires it, after reviewing the legal basis of the request, and we disclose no more than the request lawfully requires.

9. Changes

If we change this policy we update the effective date above. If a change affects what we do with data from a connected account, we tell connected customers in UOS before it applies.

Ubiz Marketing Agency, Israel