TribeOS Privacy Policy and Terms
TribeOS Privacy Policy and Terms
TribeOS Privacy Policy and Terms
Last updated: 16 October 2026
TribeOS is the internal operations tool of Igniting Tribes, a marketing agency in the Netherlands. It connects to Meta’s Marketing API through our Meta app “TribeOS” (app ID 2473331846403387). This page explains which data TribeOS receives from Meta, what we do with it, who processes it, how long we keep it and how you can have it deleted. Our general privacy policy for website visitors is at ignitingtribes.co/privacy-policy.
Last updated: 16 October 2026
TribeOS is the internal operations tool of Igniting Tribes, a marketing agency in the Netherlands. It connects to Meta’s Marketing API through our Meta app “TribeOS” (app ID 2473331846403387). This page explains which data TribeOS receives from Meta, what we do with it, who processes it, how long we keep it and how you can have it deleted. Our general privacy policy for website visitors is at ignitingtribes.co/privacy-policy.
Who we are
Who we are
Igniting Tribes, the Netherlands. Contact: luke@ignitingtribes.co. Igniting Tribes is responsible towards Meta for all data TribeOS receives. For data from a client’s ad account, the client is the controller under the GDPR and we process it on the client’s behalf.
Igniting Tribes, the Netherlands. Contact: luke@ignitingtribes.co. Igniting Tribes is responsible towards Meta for all data TribeOS receives. For data from a client’s ad account, the client is the controller under the GDPR and we process it on the client’s behalf.
What data TribeOS receives from Meta
What data TribeOS receives from Meta
• Ad data for our own ad accounts and for client ad accounts that the client shared with our Business Manager: campaigns, ad sets, ads, creatives, videos and their thumbnails, and performance figures such as spend, impressions, clicks and leads.
• Lead form submissions from a client’s lead ads. We do not store the plain contact details. We store only one way hashes (SHA-256) of the email address, phone number, name and company, plus the lead ID, form, ad and time.
• Profile and insight figures of our own Instagram account and Facebook Page.
TribeOS does not use Facebook Login and has no public users.
• Ad data for our own ad accounts and for client ad accounts that the client shared with our Business Manager: campaigns, ad sets, ads, creatives, videos and their thumbnails, and performance figures such as spend, impressions, clicks and leads.
• Lead form submissions from a client’s lead ads. We do not store the plain contact details. We store only one way hashes (SHA-256) of the email address, phone number, name and company, plus the lead ID, form, ad and time.
• Profile and insight figures of our own Instagram account and Facebook Page.
TribeOS does not use Facebook Login and has no public users.
How we use it
How we use it
• To show each client, and our team working for that client, which ads and creatives bring leads, sales calls and customers.
• To match a lead to the same person’s record in that client’s own CRM by comparing hashes, so the client can see which ad brought the lead.
• To create new campaigns in a client’s ad account at the client’s request, always paused, for the client to review and activate.
We never sell this data, never use one client’s data for another client, never combine data of different clients, never try to reverse a hash or re-identify a person, and never use it to train AI models.
• To show each client, and our team working for that client, which ads and creatives bring leads, sales calls and customers.
• To match a lead to the same person’s record in that client’s own CRM by comparing hashes, so the client can see which ad brought the lead.
• To create new campaigns in a client’s ad account at the client’s request, always paused, for the client to review and activate.
We never sell this data, never use one client’s data for another client, never combine data of different clients, never try to reverse a hash or re-identify a person, and never use it to train AI models.
Who processes it
Who processes it
We use these service providers to process the data on our behalf:
• Supabase: database hosting, data stored in Ireland (EU)
• Vercel: hosting of our internal dashboards (United States)
• Google Workspace: spreadsheets for our own reporting
• Anthropic: AI assistance when we analyse results and build our tools (United States)
• Slack: our internal team chat, where we post daily reporting summaries (United States)
• GitHub: our code repository, which also holds working notes with campaign IDs and aggregated ad figures (United States)
Working files are kept on our own company computers.
We use these service providers to process the data on our behalf:
• Supabase: database hosting, data stored in Ireland (EU)
• Vercel: hosting of our internal dashboards (United States)
• Google Workspace: spreadsheets for our own reporting
• Anthropic: AI assistance when we analyse results and build our tools (United States)
• Slack: our internal team chat, where we post daily reporting summaries (United States)
• GitHub: our code repository, which also holds working notes with campaign IDs and aggregated ad figures (United States)
Working files are kept on our own company computers.
How long we keep it
How long we keep it
We keep data while we work for the client and need it for reporting. We delete it within 30 days after the collaboration ends or after a valid deletion request, and backups are overwritten within 30 days after that.
We keep data while we work for the client and need it for reporting. We delete it within 30 days after the collaboration ends or after a valid deletion request, and backups are overwritten within 30 days after that.
Access and deletion
Access and deletion
Anyone whose data we hold through TribeOS, including people who filled in a client’s lead form, can ask us to see or delete it at luke@ignitingtribes.co. We respond within 30 days. You can also contact the advertiser whose form you filled in, or file a complaint with the Dutch Data Protection Authority (Autoriteit Persoonsgegevens).
Anyone whose data we hold through TribeOS, including people who filled in a client’s lead form, can ask us to see or delete it at luke@ignitingtribes.co. We respond within 30 days. You can also contact the advertiser whose form you filled in, or file a complaint with the Dutch Data Protection Authority (Autoriteit Persoonsgegevens).
Security
Security
Only members of our own team can access TribeOS data, behind a login. Database access is limited by role and an allow list, data is encrypted in transit, and access tokens are kept out of our code.
Only members of our own team can access TribeOS data, behind a login. Database access is limited by role and an allow list, data is encrypted in transit, and access tokens are kept out of our code.
Requests from public authorities
Requests from public authorities
Every request from a government or public authority for TribeOS data goes to the owner of Igniting Tribes. We have it reviewed for legality, challenge requests that are unlawful or too broad, disclose only the minimum required, inform the client where the law allows, and record every request. We have not received such a request.
Every request from a government or public authority for TribeOS data goes to the owner of Igniting Tribes. We have it reviewed for legality, challenge requests that are unlawful or too broad, disclose only the minimum required, inform the client where the law allows, and record every request. We have not received such a request.
Terms of use
Terms of use
TribeOS is an internal tool and is not offered to the public. Its outputs are only for Igniting Tribes and for the client the data belongs to. Everyone with access uses the data only for that client, keeps it confidential and follows Meta’s Platform Terms and Developer Policies.
TribeOS is an internal tool and is not offered to the public. Its outputs are only for Igniting Tribes and for the client the data belongs to. Everyone with access uses the data only for that client, keeps it confidential and follows Meta’s Platform Terms and Developer Policies.
Changes
Changes
We update this page when TribeOS changes and change the date at the top.
We update this page when TribeOS changes and change the date at the top.