artifocial Privacy Notice
Last Updated: October 3, 2026
What this notice covers
This notice covers the artifocial website, content, newsletters, waitlists, and readiness scan. We do not sell personal information or use it for cross-context behavioral advertising. Alarmly and Foundry have additional notices for their different data flows.
1. Scope and who is responsible
This notice explains how artifocial handles information on artifocial.com, its content pages, newsletter and waitlist forms, and the Agent-Native Readiness Scan. Product-specific notices add detail and control when they are more specific:
- Alarmly Privacy Policy for the Alarmly app and web experience.
- Foundry Privacy Notice for Foundry requests, scan follow-up, and the customer-hosted product boundary.
artifocial is the public brand responsible for this website, and it is the trading name of the individual operator of this Website rather than a registered company. No separate legal entity stands behind this notice today: that operator is responsible for the personal data described here, and is the counterparty for paid Foundry onboarding, which is publicly listed but is not accepting payment at present. We will add the registered legal name and mailing address here as soon as formation completes. Privacy requests can be sent to info@artifocial.com.
2. Information we handle
| Context | Information | Why we use it |
|---|---|---|
| Website visits | Page and route, timestamp, referrer, filtered campaign parameters, country or region, browser, operating system, device type, and a short-lived hash derived from the incoming request. | Host and secure the site, count aggregate visits, and understand which content works. |
| Creating an alarm in the Alarmly Web app | One event named alarm_created, carrying exactly two things: a campaign label drawn from a fixed list we publish (anything unrecognised is recorded asother), and a true/false flag for whether it is the first alarm you created yourself in that browser. Never the alarm's label, time, id or personality mode. It rides the same pipeline and the same short-lived request-derived hash as a page view, and creates no new identifier. | Tell whether people who arrive from one of our links go on to set an alarm, so we know which links are worth publishing. |
| Newsletter and waitlists | Email address, answers you submit, campaign and landing attribution, subscription timestamp, referrer metadata, and the public IP address used to subscribe. | Send confirmation and requested follow-up, manage subscriptions, route relevant requests, measure source effectiveness, and prevent abuse. |
| Readiness Scan follow-up | Your 14 answers, scores and segment calculated from those answers, and an internal fit-routing flag, but only if you choose to submit an email after seeing the result. | Send the result, avoid asking the same questions twice, and identify requests for human review. |
| Foundry request | Email, team-size band, onboarding preference, attribution fields, and an internal fit-routing flag derived from the two qualifier answers. | Prepare and route a relevant walkthrough or onboarding conversation. |
| Contact and feedback | Your email address, message, and anything else you choose to include. | Respond to you, troubleshoot, and improve our work. |
| Hosting and error logs | Request IP, route, time, user agent, and error details. If a waitlist write fails, a recovery log can temporarily include the submitted email and form metadata so the request is not silently lost. | Security, reliability, abuse prevention, and recovery of a submission you asked us to record. |
The readiness scan calculates its result in your browser. If you view the result and do not submit an email, the scan answers are not sent through our waitlist API. Product-created content has separate boundaries described in the relevant product notice.
3. Service providers
We use a small set of providers for the purposes described above:
- Vercel — website hosting, server logs, and Web Analytics. Vercel Web Analytics uses no third-party analytics cookies and creates a request-derived visitor hash that resets daily. Data points can include page, referrer, coarse location, browser, operating system, and device type, plus the single
alarm_createdevent listed in the table above. See Vercel's Web Analytics privacy documentation. - Buttondown — email confirmation, newsletter delivery, subscription management, waitlist metadata, and abuse prevention. Buttondown documents that subscriber records can include email, subscription IP, referrer metadata, and subscription time. See Buttondown's data-processing terms.
- PostHog and Formspree — used only for the Alarmly data flows described in the Alarmly Privacy Policy.
We may disclose information when reasonably necessary to comply with law, protect rights or safety, investigate abuse, or complete a business transaction subject to appropriate protections. We do not sell personal information, provide it to data brokers, or share it for cross-context behavioral advertising.
4. Retention
- Vercel's request-derived Web Analytics visitor hash expires after 24 hours. Aggregate analytics data remains subject to the Vercel project's retention settings. We do not build a cross-site advertising profile from it.
- Buttondown keeps subscription information for the duration of our email service and as needed to manage the subscription. You may unsubscribe from emails at any time and ask us to delete the associated record. A minimal suppression record may be retained when needed to honor an opt-out or meet legal obligations.
- Failed-write recovery logs are used only to restore a requested signup or diagnose the failure. They expire under the hosting log-retention window and are not a separate marketing database.
- Correspondence is kept only as long as reasonably needed to answer, maintain necessary business records, resolve disputes, and meet legal obligations.
5. Your choices and privacy requests
- Do not submit optional forms if you do not want us to receive their information.
- Unsubscribe using the link in any Buttondown email.
- Ask to access, correct, or delete identifiable information by emailing info@artifocial.com. We may need to verify the request and may retain information when law permits or requires it.
- Alarmly's in-app analytics control is described in its product-specific privacy policy.
Depending on your location and which law applies, you may have additional rights. We will not discriminate against you for making a valid privacy request.
6. Cookies, browser storage, and Do Not Track
artifocial.com sets no cookies. Vercel Web Analytics is cookieless — it identifies a visit by a hash Vercel derives from the incoming request, and that hash is discarded after 24 hours. The one alarm_created event the Alarmly Web app sends rides that same pipeline and that same short-lived hash, and creates no identifier of its own. We run no advertising pixels, no tag manager, and no third-party analytics script.
Two things are stored on your device, and neither is a cookie. First, when you arrive from a link we tagged with campaign parameters, the site saves that single arrival — the campaign parameters and the page you landed on — in your browser's session storage, so that a signup you complete a few clicks later is credited to the link you actually came from instead of being recorded as “direct”. It stays in that one browser tab and is erased when you close the tab. Second, if you create an alarm in the Alarmly Web app, one true/false flag is kept in your browser's local storage so that setting a second alarm is not counted as a second conversion. That flag records no alarm, no time and no date, and it stays until you clear your browser storage.
Neither value is handed to anyone else as stored, and neither is sent anywhere on its own. One value derived from the first does leave your device: when you create your first alarm, the campaign label from that arrival — matched against a fixed list we publish, with anything unrecognised recorded as other — travels with the alarm_created event described in section 2. Where there was no such arrival the label is direct; where your browser blocked the storage so we genuinely could not tell, it is unavailable rather than direct, because a measurement we failed to make is not the same as knowing you came on your own. Blocking site data in your browser settings prevents both, and nothing on the site breaks if you do.
Payment pages are the exception, and they are not ours. When Foundry checkout is accepting payment, it hands you to Stripe's own hosted pages, where Stripe sets the cookies it uses to detect fraud, under Stripe's cookie policy. Those cookies belong to Stripe's domain, not to artifocial.com.
Browser “Do Not Track” signals are not standardized, so the site does not change behavior in response to that signal; our practices remain the same: no cross-site advertising profile and no sale of personal information. You can use browser controls or content-blocking tools to limit requests to analytics services.
7. Security and international access
We use reasonable administrative and technical measures appropriate to the information we handle, but no internet transmission or storage system is guaranteed to be completely secure. Our current commercial launch scope is the United States. The website may be reachable elsewhere; that reachability is not a representation that we actively market or contract in every jurisdiction.
8. Children
The general website and Alarmly are intended for people age 13 or older. Foundry forms and commercial interactions are for adults age 18 or older. We do not knowingly collect personal information online from children under 13. If you believe a child under 13 sent us personal information, contact us so we can review and delete it as appropriate.
9. Changes and contact
We will update the date above when this notice changes. If a change materially affects how we use information already collected, we will provide additional notice or seek consent when applicable instead of silently applying a new use.
Questions or requests: info@artifocial.com with the subject “Privacy Request.”