Privacy
ROASalina is a marketing-reporting application operated by Wang Technology Firm LLC. It reads advertising, organic social, and sales data from accounts you explicitly connect, and presents them back to you as blended return-on-ad-spend reporting. This policy explains what it stores, why, and how to get it deleted.
Effective 5 November 2026
ROASalina ("the Service") is operated by Wang Technology Firm LLC ("we", "us"). For any privacy question, correction, or deletion request, contact josh@wangtechnologyfirm.com.
The Service is organized into organizations. An organization is a customer workspace — a brand or company — and every connected account, every row of imported data, and every report belongs to exactly one organization.
We collect two kinds of data: the account you create to sign in, and the data we import from third-party platforms at your instruction.
Account data
Your email address and authentication credentials, handled by our authentication provider. Passwords are stored only as salted hashes; we never see them in plain text. We also record which organizations you belong to and your role in each.
Data imported from connected platforms
Only from accounts an administrator of your organization has connected through that platform's own OAuth consent flow. Nothing is imported from an account you have not connected.
| Source | What we import |
|---|---|
| Google Ads | Account identifier, descriptive name, and currency; campaign- and ad-level performance by date — cost, impressions, clicks, conversions, and conversion value. |
| Meta Ads | Ad account, campaign, ad set, and ad identifiers and names; spend, impressions, clicks, reach, and purchase conversions by date. |
| Instagram & Facebook Pages | Public post content and metadata for the connected business account — captions, permalinks, post type, and engagement counts such as reach, likes, comments, and saves. |
| Shopify | Order records — order number, totals, discounts, tax, currency, financial and fulfilment status, line items, traffic attribution fields, and the customer identifier and email address attached to each order. |
Order records include the email address and customer identifier of your customers. We import these so that revenue can be attributed to the campaign that produced it. We do not use them to contact your customers, we do not build profiles across organizations, and we never sell them.
ROASalina requests the https://www.googleapis.com/auth/adwords scope. It is used solely to read reporting data from the Google Ads account you choose during the connect flow, and to list which accounts your Google login can access so that you can pick one. ROASalina does not create, modify, pause, or bid-manage anything in Google Ads, and performs no keyword research or keyword planning. Our Google Ads integration page documents every API call we make.
ROASalina's use and transfer of information received from Google APIs to any other app will adhere to the Google API Services User Data Policy, including the Limited Use requirements. We do not transfer Google user data to third parties except as necessary to provide and secure the Service, we do not use it for advertising, and we do not allow humans to read it except with your explicit consent, for security purposes, to comply with applicable law, or where the data has been aggregated and anonymized.
Imported data is used only to produce reporting for the organization it belongs to: blended ROAS across paid and organic sources, spend and revenue trends, per-campaign and per-post performance, and recommendations about what to scale or cut.
We do not use your data or your customers' data to train machine-learning models, we do not sell or rent it, and we do not share it with other organizations on the Service or with advertisers.
When you connect a platform, we store the access and refresh tokens that platform issues. Those tokens are held in a separate, restricted table, are reachable only by server-side code running with elevated privileges, and are never exposed to the browser or returned by any client-facing interface.
Disconnecting a connection removes its stored tokens. You can also revoke our access directly at the source — for Google, via your Google Account permissions page — which immediately ends our ability to read anything, whether or not you also delete the connection here.
Every table holding imported data carries the owning organization's identifier, and database-level row-level security policies restrict every read and write to members of that organization. Access additionally requires an authenticated session; there is no public or unauthenticated route to any imported data.
We rely on the following providers to operate the Service:
| Provider | Role |
|---|---|
| Supabase | Database, authentication, and scheduled jobs |
| Cloudflare | Application hosting and content delivery |
| Resend | Transactional email, such as team invitations |
Each processes data only to provide its service to us. We do not authorize any of them to use your data for their own purposes.
Imported data is retained for as long as the connection exists and your organization has an account, because historical data is what the reporting is built on. Deleting a connection removes its stored credentials and stops further import.
To delete an organization's imported data, or your user account, email josh@wangtechnologyfirm.com from the address associated with the account. We will action the request within 30 days and confirm when it is done. Backups are retained on a rolling basis and purge themselves within 30 days of deletion.
Depending on where you live, you may have rights to access, correct, export, or delete personal data we hold about you, and to object to or restrict certain processing. Exercise any of them by writing to josh@wangtechnologyfirm.com. We will not discriminate against you for doing so.
Where your organization connects accounts containing data about your own customers, you are the controller of that data and we act as your processor, handling it on your instructions.
The Service is a business tool and is not directed to anyone under 16. We do not knowingly collect personal data from children.
If we change this policy materially, we will update the effective date above and notify organization administrators by email before the change takes effect.