Alan Christopher Thomas alanchrt

This policy is not ready to publish as written. The main problem is not missing boilerplate; it is that several categorical promises do not match Duramata’s apparent data flows. That creates FTC exposure, Google OAuth verification risk, and material diligence problems in an acquisition.

This is a legal-risk review, not legal advice. Privacy counsel should validate the final policy against production configurations, vendor contracts, and actual retention behavior.

Highest-priority findings

Priority	Issue	Why it matters / recommended change
Critical	Google data in a sale	Google’s Limited Use rules permit transferring Google user data during a merger or acquisition only with explicit prior user consent. The general corporate-transaction clause is therefore insufficient for Gmail/Calendar data. Plan for affirmative consent, reauthorization, or excluding/deleting that data before transfer. [Google API Services User Data Policy](https://developers.google.com/terms/api-services-user

Data Platform Setup

Architecture

Lifecycle analytics use Cloudflare Pipelines writing raw NDJSON events into R2. Workers emit semantic events such as sprite_created; RARRA metrics are SQL queries over those events, not categories computed at write time. If the activation definition changes, update the SQL and re-query historical data.

The API worker is the producer:

Google Play closed testing — manual setup steps

This change adds a Google Play closed testing (alpha track) build to the production CI lane. Each app.* release now runs two Android builds in parallel:

android-build → the existing internal build (production profile), unchanged, still installable by Expo/EAS testers via a direct link.
android-build-play → a new Play Store build (production-play profile) that auto-submits to the closed testing (alpha) track.

Loops Contact Segmentation for a Waitlist Flow

TL;DR

Don't use lists for lifecycle state. Use a custom contact property (subscriptionStatus) and the sendEvent endpoint.

Why Not Mailing Lists?

Keybase proof

I hereby claim:

I am alanchrt on github.
I am alanchrt (https://keybase.io/alanchrt) on keybase.
I have a public key whose fingerprint is 0817 268C 001E DA3F C325 DF8A CDF1 536E CA70 A16C

To claim this, I am signing this object:

	var distancePoints = function(p1, p2) {
	// Find the distance between two points
	return Math.sqrt(Math.pow(p2[0] - p1[0], 2) + Math.pow(p2[1] - p1[1], 2));
	};

	var intersectCircles = function (c1, r1, c2, r2) {
	// Find the points of intersection for two circles
	// Based on: http://stackoverflow.com/a/3349134
	var d = distancePoints(c1, c2);
	if (d > r1 + r2) // Circles do not overlap

	import json, serial, threading, time
	import mindwave

	headsets = [
	{
	'name': 'red',
	'headset': mindwave.Headset('/dev/tty.MindWaveMobile-DevA', open_serial=False),
	},
	{
	'name': 'green',

	headsets = [
	{
	'name': 'red',
	'headset': mindwave.Headset('/dev/tty.MindWaveMobile-DevA', open_serial=False),
	},
	{
	'name': 'green',
	'headset': mindwave.Headset('/dev/tty.MindWaveMobile-DevA-1', open_serial=False),
	},
	]

	<!doctype html>
	<html>
	<head>
	<title>Reinventing Retail</title>
	<style>
	body {
	font-family: Helvetica, Arial, sans-serif;
	background: #000;
	margin: 0;
	overflow: hidden;

	/*****************************************************************************\
	* Batch Spreadsheet Geocoding Script *
	* Author: Alan Christopher Thomas *
	* http://alanchristopherthomas.com/ *
	\*****************************************************************************/

	function onOpen() {
	// Add the Geocode menu
	SpreadsheetApp.getActiveSpreadsheet().addMenu("Geocoder", [{
	name: "Geocode addresses",