Privacy Policy

How SkynetLabs handles your data

Plain-language privacy policy for the website at skynetjoe.com and any consulting engagement run by Waseem Nasir. Written to be lawyer-readable but founder-friendly.

Last updated: 2026-10-20 Operating from Bali, Indonesia

1. Who we are

SkynetLabs is the operating name of the sole-proprietor consulting practice run by Waseem Nasir, based in Bali, Indonesia. We build AI automation, websites, and content systems for clients across nine countries.

If you need to reach a human about any data question, email waseem@skynetjoe.com.

2. What we collect

We try to collect the smallest amount of data needed to actually reply to you and ship the work.

• Site visit data — an anonymous, cookieless funnel counter we run ourselves. On page load, booking-link clicks and completed bookings, the browser sends the site name, event name, page path (no query string), referring domain, booking step and (on a click) the address of the booking link you clicked to our own self-hosted n8n server. No cookies, no local storage, no user or device identifier; it stays silent if your browser sends Do-Not-Track or Global Privacy Control. Like any web request, the receiving server sees your IP address in transit; it is not written to the events table. The same n8n server separately receives the details you enter on a lead form (for example name, email, phone, business details, the answers or problem you typed, and campaign tags such as utm) so we can respond quickly — that is a lead alert, not part of the anonymous counter.
• Advertising measurement — the Meta Pixel loads on every page and sets Meta cookies, governed by Meta's privacy terms. Google Analytics / Tag Manager are not loaded on this site today.
• Lead forms and tool email gates — when you enter an email to unlock a free tool result or submit a lead form, that email (plus the tool you used) is sent to our CRM so we can follow up, and the tool remembers it in your browser so you are not asked twice. When the Meta Conversions API integration is switched on, a hashed (SHA-256) copy of that email plus browser identifiers is also sent to Meta server-side so ad results can be matched to enquiries. The details you submit through the contact form, landing-page forms (including the /lp/speed-to-lead and /lp/ai-audit qualifiers), tool email gates, the prompt-library form, the exit-intent pop-up, the tool feedback box (if you add an email) and the referral form (only the address of the person submitting, never the friend you name) are also stored in our operations dashboard (hq.skynetjoe.com, self-hosted on a server rented from Contabo in France) and as a contact record in Brevo (EU, France) on a separate list that receives no marketing email. You only join the email list if you tick the box (offered on the contact form, the freight, home-services, logistics and ops-audit landing-page forms, the tool email gates and the prompt-library form) or use the sign-up card. The two paid-campaign landing-page qualifiers, the exit-intent pop-up, the referral form and the tool feedback box have no tick box and are lead-only.
• Contact form (/contact) — name, email and the project brief or problem you describe; nothing else is required. It goes to our n8n lead alert (see section 4), to our operations dashboard (your email and first name), and to our CRM when its webhook is configured. A copy is also kept in a file on our web host server if the CRM write does not go through.
• Referral form — your own email and the email of the friend you want us to reach out to (plus a name or note, if the form ever asks for one). Your friend's details are not sent to the operations dashboard, Brevo, the enquiry-triage model or the n8n alert. They go to a note on your contact record in our CRM or, if that does not go through, to a file on our web host server and to an internal backup email when that is configured. The n8n alert only says a referral arrived. We contact your friend once, to introduce ourselves, and delete their details on request. Please only share an address if your friend is happy to hear from us.
• Tool feedback — the message you type into a free tool's feedback box and, if you add it, your email; sent through the n8n lead alert to our internal Slack and saved in a file on our web host server so we can read it, and — if you gave an email — that email is also saved to our CRM as a contact tagged with the tool name so we can follow up, and to our operations dashboard and Brevo as a contact on the separate list that receives no marketing email. The feedback box has no email-list tick box, so it is lead-only.
• Email correspondence — anything you email to us is stored in Google Workspace inside our mailbox.
• Newsletter and resource emails — when you enter your email in the prompt-library form (you only join the email list if you tick the box there; otherwise it is saved as a lead only), or to unlock the Claude Code video prompts (you only receive new prompts by email if you tick the email-list box), we collect your email address (and a name, only if the form asks for one) and record which form it came from. The prompt-library form also remembers your email in your browser so it is not asked twice. A small email-list sign-up card may also appear once per browser; if you fill it in it collects your email, optionally your first name and the topic you picked, and the page you were on. Section 3a below explains how we use it.

3. Why we collect it

• To reply to inbound work briefs and questions.
• To ship the project you've engaged us for.
• To send invoices and accept payment.

We do not sell, rent, or trade your data. We never have.

3a. Our newsletter

• What we collect: your email address and, if the form asks for it, your name, plus the name of the form or tool you signed up through. The sign-up card also records the topic you picked and the page you were on.
• Why: to email you the newsletter and free resources you asked for (for example new prompts for the prompt library and the Claude Code video prompts). If you join through the sign-up card or tick the email-list box on a form you will get a welcome email when you join, three more over the next two weeks, then only occasional emails. Brevo records whether these emails are opened and which links are clicked, so we can see what is useful.
• Legal basis: your consent. You give it by ticking the box or using the sign-up card, and you can withdraw it at any time.
• Where it goes: the signup is sent to our CRM (GoHighLevel), tagged with the form it came from. If the CRM write does not go through, the details are kept in a file on our web host server and in our operations dashboard so the signup is not lost. Every lead form, the contact form and the sign-up card included, also sends an alert with the details entered on that form to our self-hosted n8n server when that alert is switched on. Sign-up card entries are also stored in our own operations dashboard (hq.skynetjoe.com, self-hosted on a server rented from Contabo in France), which passes them to Brevo, the email service that sends the welcome email and the newsletter. The other processors listed in section 4 may also see it where they are described there (for example Meta, which receives a hashed copy of the email when the Conversions API integration is on).
• Unsubscribe: every list email has a one-click unsubscribe link, which stops all list emails immediately; our dashboard never emails you itself. Replying "stop" to any email works too and is handled by hand. The topic you pick on the sign-up card only decides which links the welcome email sends you. You can also write to waseem@skynetjoe.com.
• How long: until you unsubscribe or ask us to delete it. After you unsubscribe we keep only what we need to remember not to email you again, unless you ask for full deletion.
• Contact: waseem@skynetjoe.com.

4. Who we share it with

The small number of third-party services we rely on to run the business:

• Stripe — payment processing for clients who pay by card. Stripe sees the transaction data needed to settle the payment.
• Wise — international bank transfers for clients who prefer wire payment. Wise sees the transfer details.
• Google Workspace — for email correspondence with clients and inbound briefs.
• Hostinger — hosts skynetjoe.com.
• Our self-hosted n8n server (on a server rented from Contabo in France, the same one as our operations dashboard) — receives the anonymous funnel counts and the lead alerts described in section 2. A lead alert is stored in that server's database and posted to our internal Slack with the details you entered on that form (for example name, email, phone, business details, the answers or problem you typed, and campaign tags such as utm). Tool feedback goes the same way.
• Meta Platforms — receives Meta Pixel events for advertising measurement.
• GoHighLevel — our CRM; receives whatever you enter on a lead form, a tool email gate, a tool feedback box or, when the CRM webhook is configured, the contact brief (name, email, phone/WhatsApp, company, website, role, current tool stack, how you heard about us, your brief, and which form or tool it came from) so we can follow up.
• Resend — transactional email service. It is a backup route that can send us an internal notification carrying the same lead details, and it is used only when it is configured on our server; when it is not, the details are kept in a file on our web host server and in our operations dashboard instead.
• Our operations dashboard (hq.skynetjoe.com, self-hosted on a server rented from Contabo in France) — stores email-list sign-ups and the lead-form details described in section 2 (email, optional first name, chosen topic, page, which site, and whether you ticked the email-list box).
• Brevo — email-sending service; receives the same details from our dashboard (lead-form contacts go on a separate list that is never emailed) and, for email-list sign-ups, sends the welcome email, the welcome series and the newsletter, and records opens and link clicks on them. Every one of those emails carries Brevo's unsubscribe link.
• Slack — our n8n lead alert posts each new lead to our internal Slack with the details you entered on that form (for example name, email, phone, business details, the answers or problem you typed, and campaign tags such as utm) so we can follow up quickly. Tool-feedback messages and the optional email attached to them go there too.
• Enquiry triage — when enabled, the name, company, message and page of a contact-form submission (never your email or phone) are sent to a typed-decision model (TypeSafe Jev via OpenRouter) to decide how quickly we reply. Email addresses and phone numbers typed into the message itself are stripped before it is sent. Not used for training.
• Calendly — runs the call booking on /contact and the landing pages; when you book, your name, email, time zone and any answers you type go to Calendly under its own privacy terms, and Calendly emails us the booking details. If we switch on Calendly's booking notifications, the booking name and email are also stored in our operations dashboard and in Brevo as a no-marketing contact.
• GitHub — source code storage. No client business data lives here unless a client has explicitly asked us to host their repo for them.

Beyond the services listed here, we do not share your data with any other third party without your explicit written consent.

5. How long we keep it

• Active client records — kept indefinitely while the engagement is live, then for 7 years after engagement close (Indonesian tax record requirement).
• Leads and inbound briefs that don't become clients — there is no automatic deletion yet. These lead-only records (CRM, operations dashboard, the Brevo no-marketing list, the n8n lead database, Slack and the file on our web host server) are deleted by hand when you ask.
• Email-list subscribers — kept until you unsubscribe or ask us to delete your data (see section 3a).
• Anonymous funnel counts — aggregate rows only, no identifiers; we can't tie them back to a person. Meta Pixel data is retained under Meta's own policy.

6. Your rights

You can request any of the following by emailing waseem@skynetjoe.com with the subject line "Data request":

• A copy of every piece of data we hold on you.
• Deletion of your data (subject to the tax-record retention rule above).
• Correction of any data you believe is inaccurate.
• Export of your data in a portable format.

We respond to data requests within 14 days. No charges, no friction, no "we'll get back to you" loop.

7. Cookies

What this site stores in your browser:

• localStorage (browser-side store, never read by the funnel counter): the free tools keep your in-progress answers and the results you generate so a refresh does not lose them; if you unlocked a tool with your email, that email is remembered so you are not asked again (the same email was already sent to our CRM when you entered it); the call qualifier on the landing pages keeps your answers the same way; and small dismissal flags remember that you closed the announcement bar, the exit prompt or the sticky book-a-call bar.
• sessionStorage (cleared when the tab closes): flags that stop pop-ups, the chat bubble and article-view counters from repeating within one visit. Nothing identifying.
• The Meta Pixel sets Meta's advertising cookies (e.g. _fbp) so ad performance can be measured. Our own funnel counter sets nothing. Calendly's booking embed on /contact and the landing pages sets its own cookies, under Calendly's terms.

We do not currently show a cookie consent banner. Because the Meta Pixel sets advertising cookies (and Calendly sets its own on the booking pages), EU/UK visitors may be entitled to be asked first; a consent gate is under evaluation. Until it ships you can block the pixel with any tracker-blocking browser or extension, and our own counter already honours Do-Not-Track / Global Privacy Control.

8. Data location

The infrastructure we use is hosted in the United States and the European Union:

• Hostinger — website hosting (EU data center).
• Contabo (France) — the server running our self-hosted n8n (anonymous funnel counts and lead alerts) and our operations dashboard.
• Meta Platforms — US (Pixel and Conversions API data).
• Calendly — US (booking details).
• GoHighLevel — US (CRM contact records).
• Resend — US (internal lead-notification emails, only if that backup is configured).
• Brevo — EU, France (email-list contacts and the emails sent to them).
• Our operations dashboard — our self-hosted VPS, EU, France (email-list sign-ups).
• Slack — US (lead alerts and tool-feedback messages from our n8n server).
• Google Workspace — US and EU data centers.
• GitHub — US data centers.
• Stripe — US and EU.
• Wise — UK and EU.

No client data is stored on servers located inside Indonesia. We operate from Bali but our infrastructure is not in Indonesia.

9. Children's data

This service is not directed at people under the age of 18. We do not knowingly collect data from children. If you believe a child has submitted data to us, email waseem@skynetjoe.com and we'll remove it immediately.

10. Changes to this policy

Last updated 2026-10-20.

If we make material changes to how we handle your data, active clients will receive an email notice. The "last updated" date at the top of this page always reflects the most recent revision. Minor wording changes are made silently.

Questions about your data?

Email waseem@skynetjoe.com or send a note via the contact form.

Open contact form