SILO is an operations workspace operated by Baseballism (“we”, “us”). Companies use SILO to bring their sales, inventory, purchasing, finance and marketing data into one place. This policy explains what data SILO holds, why, and how it is protected.
SILO is used by the employees, contractors and agents of companies that use SILO (“customer companies”). Access is by invitation from a customer company’s administrator; there is no public sign-up and no consumer use. SILO does not display advertising, set advertising cookies, or track users across other websites.
This policy also covers people who submit the public early-access interest form. Submitting that form does not create a SILO account or workspace.
When you join the early-access queue, we collect your name, company name and email address to review your interest and contact you about SILO early access. These details are visible only to SILO platform administrators and the service providers needed to operate the queue. They are not shared with other customer companies or used to enroll you in an automated marketing mailing list.
We retain these details while handling your early-access interest. You can ask to review, correct or delete them by emailing support@get-silo.com.
| Category | Examples | Why |
|---|---|---|
| Account data | Name, work email address, role, department, profile photo | Authentication, permissions, and attribution of actions |
| Business operations data | Purchase orders, suppliers, inventory, product records, tasks, internal requests | Running the customer company’s operations |
| Personnel data | Performance review content, compensation requests | The customer company’s HR processes, visible only to the specific managers and approvers involved |
| Connected-service data | Sales, inventory, payouts and orders from Shopify; accounting records from QuickBooks Online; website, search and advertising metrics from Google and other advertising platforms | Reporting, reconciliation, and preparing accounting entries |
Each customer company’s data is kept separate. A user can see only the data of the company they belong to.
A customer company’s administrator can choose to connect the company’s own Google accounts. SILO requests only these permissions, and uses them only to show that company its own reporting inside SILO:
analytics.readonly) — read-only access
to website sessions and conversions for the company’s properties.webmasters.readonly) — read-only
access to search clicks, impressions and positions for the company’s websites.adwords) — campaign spend and results for the
company’s ad accounts. SILO only reads reporting data; it does not create, change or
delete campaigns, ads or budgets.How this data is handled:
Where a QuickBooks Online company is connected to SILO, we access it under OAuth using
the com.intuit.quickbooks.accounting scope, and only for the connected
company. Specifically:
A customer company’s administrator can choose to connect the company’s own Meta business assets with Facebook Login for Business. SILO requests only these permissions, and uses them only to show that company its own reporting inside SILO:
ads_read, business_management) —
read-only access to campaign, ad set and ad performance, ad creative and its destination, for
the ad accounts the administrator selects. SILO does not create, change, pause or delete
campaigns, ads, audiences or budgets.pages_show_list,
pages_read_engagement, read_insights) — the list of Pages
the administrator grants, and those Pages’ post and Page insights.instagram_basic,
instagram_manage_insights) — the connected Instagram professional
account’s media and its insights. SILO does not publish, comment or message.SILO does not request or store information about the people who see or interact with those ads and posts beyond the aggregate metrics Meta reports. Meta data is stored in SILO’s database, is visible only to users of the company that connected it, and is never sold, used for advertising, or used to build profiles. Access tokens are readable only by SILO’s server-side functions and by administrators of the connected company. Removing the connection in SILO’s Integrations page deletes the stored token; access can also be removed at any time in Meta Business Settings → Integrations → Connected apps.
A customer company can install SILO’s Shopify app on its own store. SILO reads orders, products, inventory, locations, draft orders, reports, publications and Shopify Payments payouts, read-only, to show that company its sales, inventory and payout reporting. Order records include the customer’s name, email address and customer id as Shopify provides them; SILO does not read customer addresses, phone numbers or payment details. SILO does not change anything in the store. SILO honours Shopify’s privacy requests automatically: a customer redaction request blanks that customer’s name and email on stored orders, and uninstalling the app closes the store’s connection and, 48 hours later on Shopify’s shop redaction request, blanks the store’s customer details.
To delete data SILO holds about you or your company:
If you are not a SILO user but believe SILO holds data about you through a company that uses it, email the same address; we will identify the company and act on the request with it.
We do not sell personal information. We share data only with the service providers required to operate SILO, and only to the extent needed to provide their service:
We may disclose data where required by law.
Business records are retained while the customer company uses SILO and as needed for operational, accounting and legal purposes. Account records are retained while a person has access and for a period afterwards for audit and attribution. Connected-service tokens are deleted when the integration is disconnected.
People who use SILO can ask to review, correct, or delete their account information, subject to the customer company’s and our record-keeping and legal obligations. Contact us using the address below.
SILO is a workplace tool and is not directed to, or usable by, anyone under 16.
We may update this policy. The revision date at the top of this page always reflects the current version.