privacy policy
the short version
- your original photos and videos never leave your phone. they stay in Apple Photos.
- memoe looks at your photos on your phone first and saves what it finds there.
- videos are read on your phone only. no video, and no frame of one, is ever sent anywhere, not even with cloud checks on.
- photos in iCloud shared albums you are in are read on your phone only, like videos. none is ever sent anywhere, not even with cloud checks on.
- memoe reads your photos with a model that is part of the app. on a phone where it runs, no previews of your photos are sent to anyone. in you, read photos with lets you choose cloud checks instead (see below).
- only if you say yes, and only when memoe isn’t reading your photos with that model (it can’t run on your phone, or you chose cloud checks in you), memoe can send small previews of some photos, through memoe’s server, to OpenAI so a model can describe them. memoe’s server doesn’t keep them.
- memoe finds faces and groups the ones that look alike on your phone. the faces and the names you give people stay there.
- what you type into the search bar is sent the same way, so it can be understood. no photos go with it. when memoe can’t reach its server, an iPhone with Apple Intelligence reads it on your phone instead, and nothing is sent.
- unless you turn it off, memoe’s server also keeps a short record of each search for six months at most: your sentence with the names of people taken out, what it was understood as, and a few counts. it isn’t linked to you, your account or your phone, and no photo, face, or name or place from your library is ever in it. the switch is help improve search in you.
- memoe’s server also keeps, for your account, whether you have memoe pro (which plan, its dates, and whether it is active, expired or refunded) and a count of the cloud checks you use each month, so it can apply your plan’s limit. neither holds a photo, a preview or a search. if you bought the founding edition and claim an offer for memoe pro, it keeps a record of that claim too.
- your earlier conversations with memoe are saved on your phone, and nowhere else.
- you sign in with Apple. the app doesn’t ask for your name or email.
- the website no longer offers a beta sign-up. if you signed up while it did, you gave your name and email to Tally, only so we could invite you to the beta and tell you about the launch.
- the website sells the founding edition, a preorder. if you buy it, you give your email, Stripe takes the payment and memoe keeps a record of your purchases. nothing about you is public unless you choose it.
- the website also auctions a few domain names. if you bid, you type your email and tick the box that says you have read the terms, then give a card, your name and your billing address on Stripe’s page (a phone number is optional), Stripe saves the card, and memoe keeps a record of the sale to answer any payment dispute. the public sees only a name you choose, or “bidder” and a number.
- the website counts visits with Vercel Web Analytics: no cookies, and nothing that says who you are. the app has no analytics tools; what memoe’s server keeps of how you use it is the search record above, which you can turn off, and the monthly count of cloud checks, which it needs to apply your plan’s limit.
- no ads, nothing follows you from one app or website to another, and nothing is sold.
who we are
memoe is an iPhone app made by CommuteGeek Corp. of Alberta, Canada (“we”, “us”). this page explains what the app, its server, the website’s beta sign-up and the founding edition do with your information. you can reach us at info@commutegeek.com.
what memoe does on your phone
memoe asks for full access to your Photos library, because it searches the whole library and creates albums. through Apple’s Photos framework it reads each photo’s date, location, favorite status and whether it is a screenshot or a selfie, and it looks at the photos themselves as small previews.
using Apple’s Vision technology on the phone, memoe works out what is in your photos (for example people, clothes and colors, objects, scenes and words in photos). it saves that on your phone so your searches run there, and it picks up where it left off if you quit.
describing photos in words. memoe has a small model inside the app (an open-source one, TinyCLIP, under the MIT licence) that turns a picture into a short list of numbers, and a sentence into a list of the same kind, so the two can be compared. for each photo it keeps one list in a file on your phone that is left out of backups and removed when you delete your account. when you describe something no label covers, such as “a child in a wizard costume”, the short description that memoe’s server makes from your sentence is turned into numbers on your phone and compared with the photos’ lists there. the lists are not the pictures, and they are never sent anywhere. the model makes them from the copy of the photo that is already on the phone, and memoe doesn’t download a photo from iCloud just for this.
inside videos. for a video whose file is already on your phone, memoe reads up to 32 frames across it (about one every two seconds), how fast it moves, how often it cuts and what it sounds like (using Apple’s sound classifier, on the phone), and keeps a small outline of scenes, labels and times in a file on your phone that is left out of backups and removed when you delete your account. it uses the outline to answer searches such as “a calm video of the sea”. no video, frame, sound or outline is ever sent anywhere, and a video is never downloaded from iCloud to be read.
making things. when you tap create to make a carousel, give photos a look, export, or save a frame, memoe does it all on your phone and saves the result as new copies in Apple Photos or in the place you choose; your originals are not changed. exports leave your location out unless you turn on include location. your own looks are saved on your phone, left out of backups and removed when you delete your account. memoe never posts anything for you.
places. the country and state of a photo come from boundaries bundled inside the app, with no network request. in clean up, the details of a card can show a city or neighborhood. for that, memoe asks Apple’s geocoder about the middle of a square of about 500 m, never the exact spot.
clean up. your swipes, the delete pile, levels, streaks and achievements are saved on your phone and never sent anywhere. memoe deletes a photo or a video only after you review the pile and confirm, and iOS asks you to confirm once more. deleted photos and videos stay in recently deleted for 30 days. the optional daily reminder is a notification made on your phone, and nothing about your photos is in it beyond counts.
trips and events. memoe notices a trip (days away from where you usually take photos) or an event (a lot of photos in a few hours) from each photo’s date and place, on your phone, and saves what it found in the phone’s storage. to name a trip or an event it asks Apple’s geocoder about the middle of a few squares of about 500 m, never the exact spot. if you allow it, a reminder to sort the photos is a notification made on your phone; it has a place name, dates and a count. while the app is closed, iOS may wake memoe now and then so it can look at the dates and places of your last few weeks of photos on the phone and find a trip that just ended. none of this is sent to memoe’s server.
find similar. when you ask for photos like one photo, memoe works on your phone: it describes that photo from what it already knows and compares it with the photos it has looked at, and the comparison is not stored. if memoe’s own model isn’t reading your photos (it can’t run on your phone, or you chose cloud checks in you), cloud checks are on and you have one left, it may send one small preview (up to 512 px) of that photo to be described, like any cloud check; on a phone where the model runs, nothing is sent. nothing else leaves your phone, and the description is not kept on our servers.
people from your contacts. if you choose, memoe reads the pictures of the contacts you pick, on your phone, to suggest who is who in your photos. contact pictures and names are never uploaded, and memoe keeps only a number for each face, not the picture. a name leaves your phone only inside a sentence you type. you can forget your contacts any time in you, and signing out or deleting your account removes them.
albums made for you. memoe makes albums of trips, events and things like plane photos or sunsets, and picks the best photos for each, all on your phone and without cloud checks. the list is kept in the phone’s storage, left out of backups and removed when you sign out or delete your account. an album is written into Apple Photos only when you tap save to photos. if you allow notifications, memoe tells you when an event or a trip has an album ready; that notification is made on your phone and has a title and a count. none of this is sent to memoe’s server.
videos. from Photos, memoe reads a video’s date, place, length and whether it is a favorite. using Apple’s Vision technology on the phone, it works out what is in the video’s poster (the small picture Photos keeps on the phone) and, when the video’s file is already on the phone, in a couple of frames from inside it. no words are read from a video, and a video is never brought down from iCloud just to be read. when you search for someone by name, memoe looks for faces in a few frames of each video the search is left with and compares them, on your phone, with the faces of the people it knows. for that it keeps one small number for each face, not the picture, in a file on your phone that is left out of backups. videos are never part of the groups of people. no video, and no frame or face from one, is ever sent to memoe’s server, to OpenAI or to anyone else: cloud checks and enhanced indexing never get a video. a video you tap plays on your phone.
shared albums. if you are in an iCloud shared album, for example one a friend made after a trip, memoe reads it on your phone like the rest of your library: each photo’s date, place and size, what is in it, and the faces in it, using the copy Photos keeps on your phone. none of that is sent to memoe’s server, to OpenAI or to anyone else: previews and enhanced indexing never get a photo from a shared album, even with cloud checks on, and its faces are matched on your phone only. memoe never writes to a shared album and never puts a friend’s photo in one of your albums. when you tap share with friends on a trip, memoe hands the photos you choose to the iOS share sheet and iOS and iCloud take it from there, under Apple’s policies. memoe asks which one is you? and keeps the answer on your phone, together with a list of which shared photos it has already seen (identifiers, not photos), in files that are left out of backups. if you allow notifications, memoe can tell you when friends add photos you are in; that notification is made on your phone.
earlier conversations. so that closing the app doesn’t lose them, memoe keeps your recent conversations on your phone: what you typed, what memoe answered, and which photos it showed (as the identifiers Photos gives them, not the photos). the file holds your most recent 20 conversations, is left out of backups and is never sent anywhere. you can delete one, or all of them, from the history list on home.
photos from iCloud. if you use iCloud Photos with Optimize iPhone Storage, some of your photos live only in iCloud. when memoe needs one, to read it, to show it or to let you swipe it, it asks Apple’s Photos framework to bring it down. that is a transfer between your phone and Apple, under Apple’s policies. memoe’s background work waits for Wi-Fi unless you turn on download photos over cellular in you, and never uses cellular data in Low Data Mode.
people. memoe finds the faces in your photos and groups the ones that look like the same person. it does this on your phone, using Apple’s Vision technology to find each face and a small face-matching model that is bundled inside the app to compare them. the faces, the groups and the names you give people are saved on your phone and are never uploaded. when memoe isn’t sure that two groups are the same person, it asks you. a name you save stays on this phone. a person has their own page, and a search for them also looks in your videos, as described under videos.
what leaves your phone
signing in. the app uses Sign in with Apple and asks for no name or email. the app sends Apple’s identity token to memoe’s server, which checks it with Apple and returns a session token that lasts 30 days. the phone keeps that token in the iOS Keychain. the session token contains an identifier Apple creates for you and this app, and when the token expires.
what you type. when you search, memoe sends your sentence to its server, along with a tiny summary of where you are in the app: the filters of your current search (for example, whether it asks for photos or videos), what you did last, how many photos are shown or selected, the date range of those photos, and the current time and time zone. the server passes this to OpenAI so a model can turn your sentence into a search. no photos are included. if your sentence has the name of someone you’ve named, that name goes with it as part of the sentence, but no face and no photo does. when memoe can’t reach its server and your iPhone has Apple Intelligence, your sentence is read on your phone instead, by the language model Apple builds into iOS, and nothing about it is sent; memoe says so in its answer. what memoe’s own server keeps of a search is described under what memoe’s server keeps.
small previews, only if you say yes, and only when memoe’s own model isn’t doing the reading. on a phone where the model inside the app is running, memoe sends no previews at all, whatever the setting below says. that is the default. in you, read photos with lets you choose cloud checks instead (searching by description is then off), and a phone where the model can’t run works that way too. in that case, after you sign in, memoe asks whether it may send small previews of photos. if you tap allow cloud checks, memoe can send a preview (a JPEG with a longest side of 512 pixels, about 50 KB) of some photos to its server, which passes it to OpenAI so a model can say what is in the photo. memoe chooses which photos, for example ones a search can’t settle on the phone. each preview travels with the identifier Photos gives that photo on your phone, so the answer can find its way back to the right photo. that identifier goes no further than memoe’s server. the description comes back to your phone and is saved there. if you tap not now, or turn off cloud checks later, no previews are sent.
what is never sent. your original photos and videos, any frame of a video, any photo from an iCloud shared album, your name or email (the app never asks for them), the locations in your photos, the numbers memoe makes from your photos and the outlines it makes of your videos, the faces memoe finds and the names you save (a name travels only when you type it into a search, as part of that sentence), what you make with create, and your clean up activity.
who handles it
- Apple provides Sign in with Apple, Photos and iCloud Photos, the geocoder, and the App Store, which also confirms your memoe pro subscription to memoe’s server. Apple handles that information under its own privacy policy.
- OpenAI receives the previews and sentences described above through memoe’s server, and processes them to send back a description or a search. for the founding edition, it also receives a smaller copy of the first-place picture, to check it before it is shown. memoe’s server doesn’t send OpenAI your Apple identifier or any photo identifier. OpenAI handles what it receives under its API terms and privacy policy, which say how long it may keep API data and why.
- Vercel hosts memoe’s server and this website, keeps the standard request logs described below, and counts visits to the website with its Web Analytics, as described under this website.
- Tally runs the sign-up form and stores what you enter there for us, as described under the beta sign-up.
- Stripe processes founding edition payments, refunds and disputes, and handles what you enter on its checkout page under its own privacy policy.
- Supabase hosts the database that keeps founding edition purchases and, in a part of its own, the search record described under what memoe’s server keeps.
- Twilio places a phone call to the owner of memoe when someone takes first place on the founding edition leaderboard, and sends the owner a text message for each purchase of a set size or more. For a call, memoe’s server tells Twilio the name that founder chose to be listed under (or “founder no. N”) and their total, which are what the leaderboard already shows. For a text, it tells Twilio the amount of the purchase, whether it was a preorder or a badge upgrade, the buyer’s listed name (only if they chose to be listed) or “founder no. N”, their total and the total of all purchases. Both go to the owner’s own phone number. no email address and nothing else about a purchaser is sent. Twilio tells memoe’s server whether a call was answered, so memoe can call again if it was not. Twilio handles that under its own privacy policy.
the app has no ads and no third-party SDKs, and no analytics tools of its own beyond the search record described under what memoe’s server keeps. we don’t sell your information and we don’t use it to track you across other apps or websites.
what memoe’s server keeps
for the app, memoe’s server doesn’t store photos, previews or descriptions. each request is handled in memory and forgotten, with three exceptions: the search record below, the plan and the count of cloud checks it keeps for your account (after the search record), and the claim records of founder offers for people who bought the founding edition. the founding edition on this website is kept too: its purchases are described under the founding edition.
the search record. unless you turn off help improve search in you, memoe’s server keeps one record for each search it reads for you. we use it to learn what people ask memoe for, to improve the product and to test search. a record holds:
- the sentence you typed, with the names of people memoe found in it replaced by a marker that only says a name was there, and anything that looks like an email address, a phone number, a web address, a long number or the number of a street address replaced as well;
- what the sentence was understood as: the places, dates, things and other filters memoe searched for, with names, album names and words printed in photos taken out;
- the model that read it, how long that took, the language of the sentence (as well as memoe can tell), the app’s build number and its platform (iOS);
- a random code the server makes for that one search, with no link to your account, your phone, your Apple identifier or any other search;
- afterwards, only counts: how many photos matched for sure and how many might match, how many were left unchecked, and whether you opened a result or changed the search.
no photo, preview, face, saved name, or place or date from your library is ever in a record. it holds no account, session, device or IP address, and no user agent. only the owner of memoe can read the records, and only to learn how search is used and to test it. they are not shared, sold or used for ads. records are deleted automatically 180 days after they were made.
some limits, said plainly. a name memoe doesn’t recognise as a name (a pet’s, say) and a place you type stay in the sentence, so don’t type anything into search that you wouldn’t want read. the switch controls only this record: a search is still sent to be understood, as described above. because a record isn’t linked to you, nobody can find yours afterwards to change or delete it; turning the switch off stops new records at once, and the ones already kept are deleted when they are 180 days old. a search that memoe already understood once on your phone can be answered from your phone’s memory, without asking the server again, and then leaves no record, so the records undercount repeated searches.
your plan and your cloud checks. to know whether you have memoe pro, memoe’s server checks your subscription with Apple: the app sends Apple’s signed record of the purchase, and the App Store tells the server when a subscription renews, is refunded or ends. for your account, which is the identifier Apple creates for you and this app and never your name or email, the server keeps which plan you have, its dates, whether it is active, expired or refunded, and the numbers Apple uses to name it. to apply your plan’s monthly limit it also keeps how many cloud checks, and how many enhanced indexing descriptions, your account has used in each calendar month (counted in UTC), with an identifier for each request so a retried request isn’t counted twice. no photo, preview, description or search sentence is in any of it. it is kept while your account exists and is deleted when you delete your account.
founder offer claims. if you bought the founding edition, memoe may send you a personal link to claim an offer for memoe pro. memoe’s server then keeps a claim record in the same database as the founding edition: the email you bought with, the steps you took (link opened, email confirmed, plan chosen, offer revealed) with their dates, the plan you chose, the App Store offer code issued to you (kept encrypted until you reveal it) and a log of each change. the link itself is kept only as a scrambled number that can’t be turned back into it. nothing from your photos is in it. it is kept while the offer can be claimed, and afterwards for as long as questions about a code or a charge, or tax and accounting law, require. to have it deleted, write to info@commutegeek.com from the email you bought with; we keep only what the law requires us to.
two kinds of logs exist besides. Vercel keeps standard request logs (such as the time, the address of the request and your IP address) under its own policies. memoe’s own logs have error messages when something breaks and running totals of how many photos were described and what that cost, with no photo content, photo identifiers or search text in them.
deleting your data
open you in memoe, choose delete account, and confirm with Apple one more time. memoe then asks Apple to revoke its Sign in with Apple access and wipes what it saved on the phone: the photo index, the numbers it made from your photos, what it read from your videos and shared albums, the faces and names, your own looks, the contacts it was given, your earlier conversations, the albums it made for you, your clean up progress, the trips it found and your settings. your photos and albums in Apple Photos aren’t touched. if Apple or the network can’t be reached, nothing is wiped, and you can try again.
the founding edition. to come off the leaderboard, change your display name or delete your founding edition details, write to info@commutegeek.com from the email you bought with. none of that changes what you bought. we delete your display name, your listing and any picture or video you sent, and keep the records of your purchases for as long as tax and accounting law requires.
delete account also deletes the plan record and the cloud-check counts memoe’s server keeps for your account. the other thing it keeps for the app is the search record, and because nothing in a record says whose it is, it can’t be picked out for one person; it deletes itself after 180 days. a founder offer claim is deleted when you write to us, as described under what memoe’s server keeps. if you signed up for the beta, see the beta sign-up to have that deleted too. deleting the app from your phone also removes the photo index, the faces and names, your earlier conversations, the trips, and the clean up progress it saved.
your choices
- turn photo previews on or off any time in you (turn off cloud checks or turn on cloud checks). turning it off stops sending at once. while memoe’s own model is reading your photos on your phone, no previews are sent whatever this says. choose how memoe reads your photos, with this phone or with cloud checks, in you (read photos with).
- turn help improve search on or off any time in you. turning it off stops new search records at once; the ones already kept are deleted when they are 180 days old.
- sign out from you as well.
- change or take back Photos access, or the reminder permission, in the iOS Settings app.
- turn the daily reminder on or off in clean up settings. there you can also turn off finding trips and events, or only the reminders about them.
- turn albums for you, or only the albums after events and trips, on or off in you.
- choose whether photos in iCloud may come down over cellular data (download photos over cellular in you, off until you turn it on).
- turn notices when friends add photos on or off in you (it shows when you are in a shared album). leaving a shared album in Apple Photos stops memoe reading it.
- delete earlier conversations one at a time, or all of them, from the history list on home.
- choose, or forget, the contacts memoe uses to suggest names in you. if you gave memoe full access to your contacts, you can take it back in the iOS Settings app.
- when you preorder, choose whether you are on the leaderboard and what display name it shows, or leave both off. you can ask us to change either later.
- keep a browser from being counted on memoe.co by turning on Do Not Track or Global Privacy Control in it (many browsers and blockers have a switch). there is nothing to sign out of or delete, because nothing is stored.
- ask us a question about your information at info@commutegeek.com. if your local law gives you rights over your information, such as access or deletion, tell us and we’ll help.
children
memoe is for people old enough to have their own Apple Account, and it isn’t directed at children under 13. we don’t knowingly collect personal information from them. photo libraries can show anyone, and previews of photos only leave the phone if the account holder says yes.
this website
memoe.co sets no cookies for visitors (the only cookies are the sign-in of memoe’s own moderation page, a short one that remembers for 30 minutes that you typed a top-three email if you use edit my spot on the founding edition page, and the two described under domain sales if you bid on one). it loads nothing from other websites, not even fonts (they are served from here), until you open the beta sign-up form, which comes from Tally (see below), or go to Stripe’s checkout page to pay. pages on other websites that it links to, such as our Instagram and LinkedIn pages, are theirs, with their own policies. Vercel hosts it and keeps standard request logs.
counting visits. memoe.co counts visits with Vercel Web Analytics, so we can see which pages are read. it uses no cookie and keeps nothing in your browser. for each page you open it counts the page address, the website that sent you (only when it was another website), your country, your browser and operating system, and whether you are on a phone, a tablet or a computer. Vercel tells one visit from another with an anonymous code that it makes from the visit and that changes every day, so a visit is not linked to the one the day before. memoe sees totals and breakdowns from it, never a record of one person. the counter is Vercel’s own script, served from memoe.co itself, so your browser asks no other website for it.
before anything is counted, the page cleans the address. memoe’s own moderation pages are never counted. the code in an invite or challenge link is hidden, so the page is counted but not whose link it was. everything after a question mark is dropped, except campaign tags such as utm_source, and so is everything after a #. a receipt page’s address carries a Stripe session number: it is never sent. a page that doesn’t exist is counted under the address that was asked for, cleaned the same way. nothing is counted if your browser sends Do Not Track or Global Privacy Control, and nothing is counted anywhere but memoe.co. only the website is counted: the app sends nothing to Web Analytics.
the founding edition page has a short video, served from here. it loads only when you scroll to it, and it plays without sound until you turn it on. memoe keeps nothing about whether you watched it: no note in your browser, no cookie, no count.
the founding edition
this website sells the memoe founding edition: a preorder, and badge upgrades for founders who have one. there are no accounts: a purchase is kept with the email you give with it, and purchases made with the same email add up. this is what is kept, and why.
your email. you give it with your purchase. Stripe sends your receipt to it. memoe uses it to keep your purchases together, to deliver what your preorder includes and tell you about it (such as when memoe launches), and to answer you if you write to us. it is never shown in public.
paying. you pay on Stripe’s checkout page. Stripe receives your payment details, your email and, where tax is calculated, your billing address, and memoe never sees your card. memoe keeps a record of each purchase: what it was, the price you chose, the tax, the total paid, Stripe’s fee, any refund or dispute and where it stands, Stripe’s reference numbers for them, and the version of the terms you accepted and when, and the country in your billing address, which Stripe reports with the payment (memoe keeps that country only, never the rest of the address) and which is used only for the country totals described below. memoe sends Stripe your email, for receipts, and an internal account number, and nothing else about you.
what is public, and only if you choose it. your display name and your total purchases appear on the leaderboard, and on the founding edition page if you are first, only if you choose to be listed when you preorder. the page you see after paying shows your purchase to whoever has its address, which only you are given.
a picture, if you are first. the founder in first place may send a picture for the top of the founding edition page. memoe saves it again without its metadata (such as where and with what it was taken) and keeps that copy in the same database. to check that it suits a public page, memoe’s server sends a smaller copy of it, and nothing else about you, to OpenAI, whose model looks at it twice and answers whether it is legal to show and free of anything sensitive: one that is, which is most pictures, is approved at once, one that clearly isn’t legal is declined and deleted, and when it isn’t sure, or the picture touches something sensitive, it stays private and a person at memoe looks at it instead. it is public only after it is approved, and only while you are first. you can remove it from the page you see after paying, and we delete it when you ask us to delete your founding edition details.
a video, if you are first. the founder in first place may also send one short video (an MP4 or MOV file of up to 60 seconds and 48 MB) for the top of the founding edition page. it travels to memoe’s server in pieces and is kept in the same database. memoe blanks the usual camera, date and location tags in the file but can’t promise it finds every one, so a video can still carry where it was filmed; turn location off when you film. a video is never sent to OpenAI or anyone else to be checked, and no computer approves it: it stays private until a person at memoe has watched it and approved it, or declines it and says why. it is public only after that, and only while you are first, played from the first-place card. you can remove it from the page you see after paying, and we delete it when you ask us to delete your founding edition details.
a link, if you add one. a founder in first, second or third place may add one link to be shown next to their name; a link added earlier stays, whatever place its owner is in now. memoe keeps the address you give it in the same database (without a tracking part such as what follows a question mark), shows it on the leaderboard and, for the top three, the founding edition page, and checks it only against its own list of well-known sites: it is not sent to anyone else to be checked. you can remove it from the page you see after paying, and we delete it when you ask us to delete your founding edition details.
edit my spot. if you didn’t add your link, picture or video after paying, edit my spot on the founding edition page lets you do it later. you type the email you paid with, and if it belongs to a founder in first, second or third place right now, you can add, change or remove your link, and (in first place) your picture and video. there is no code and memoe sends no email for this: the email you type is the only check, so anyone who knows the address of a founder in the top three could use it to edit that founder’s link, picture and video while they hold the place. a picture still goes through the check described above, a video still waits for a person, a link must be a well-known site, and you can remove or replace either from the page you see after paying. the page says whether an address is in the top three, which is the one thing it tells someone who types it. signing in sets one cookie, which memoe’s server alone can read, for 30 minutes: it holds an expiry and a signature and nothing else about you, and done (or 30 minutes) ends it. memoe keeps a short record that someone signed in to edit a spot, named by an internal number, not your email, and a scrambled value of the caller’s address, used only to limit how often it can be tried.
a referral link. every founder gets a link to share, made from a random code that isn’t derived from your email or your name. when someone opens it and makes their first purchase, memoe records on their order which founder’s link it came through, to count it. the count appears next to your name on the leaderboard if you chose to be listed, and on the page you see after paying. nobody is shown who bought through a link: not you, and not the public. the code is read from the address and sent with the purchase; it is not stored in the browser.
the other lists, and the country map. the founding edition page also shows today’s list (founders by what they paid since midnight in Mountain Time), the newest founders and, once someone has a referral, the referrals list, and a flag and a map of which country pays the most (“larpiest countries”). the lists show only what the total leaderboard shows (a listed founder’s display name, total, place, referral count and, on the newest list, how long ago they joined), nothing else, and nothing about a founder who chose not to be listed. the flag and the map are made from the country in the billing address of each paid purchase, as Stripe reports it with the payment: every paid purchase counts, listed or not, but the page receives only a total and a number of buyers for each country, never an order, a name or an email, and a country with fewer than three buyers is shown inside “other countries” so that no one buyer can be picked out. the country is not stored next to your name or shown anywhere with it. it is the country of the billing address you give at checkout, not necessarily where you live; memoe keeps only that country, never the address, and does not look at your device’s location for this. the map’s “per capita” view divides each country’s total by its population, using a fixed table of public population figures that ships with memoe; it uses nothing about you that the total view does not.
a picture of the leaderboard. anyone on the founding edition page can make a picture of the top three and the leaderboard, and share it or save it. the picture is drawn in that person’s own browser from what the page already shows: the names and totals of founders who chose to be listed, first place’s approved picture if there is one, and the day. memoe’s server isn’t asked to make it and isn’t told that it was made, and it holds no email, link or purchase detail. one thing is optional: a founder further down than the picture lists can type the email they paid with to have their own place highlighted. that email goes to memoe in one request, memoe looks it up among the founders who chose to be listed and answers with that founder’s place, listed name, total and founder number, and the picture marks them; the same answer lets that person make their own share card (next paragraph). the email is not drawn on the picture, not stored and not used for anything else (the only trace is a counter that limits how often one device may ask, kept under a scrambled form of its address), and an address that isn’t listed gets the same answer as one that never paid. the answer is only what a listed founder chose to have shown, but it can be further down than the page lists, so whoever knows a listed founder’s email can see that founder’s place and total this way, and make that founder’s card. once a picture is shared or saved, it is in the hands of whoever has it.
a share card. the page you see after paying, and the share dialog on the founding edition page for a founder who chose to be listed (after typing the email they paid with, as above), can make a picture of your badge for you to share or save: a title, your display name if you gave one, your founder number, your place if you are listed (otherwise it says the rank is private), your total and the day, with a few lines that say what the card does not give you. you can pick any title your total has earned; the picking and the drawing happen in your own browser, and memoe’s server isn’t asked to make the picture, isn’t told that it was made and isn’t told which title you chose. anyone whose payment goes through gets it, whatever they paid, with no time limit. once it is shared or saved, it is in the hands of whoever has it.
a challenge card and its page. a founder who is in the top three of the total leaderboard, or of today’s list, can make a challenge card in the same two places, instead of the share card: a picture drawn in their own browser, with the title they earned, their rank, what they paid and a link, memoe.co/c/ followed by their referral code (the code is random and isn’t derived from the email or the name). making it works as above: memoe’s server isn’t asked to draw it, and the lookup by email answers only what a listed founder chose to have shown. there is no time limit. anyone who opens the link gets a page that asks memoe’s server for the founder’s listed name, place, total and today’s place (the same plain answer for a code that is nobody’s, a founder who isn’t listed or one who is hidden), and compares the price the visitor types, in the visitor’s own browser, with the leaderboard; the price is not sent anywhere and nothing is stored in the browser. the page’s button goes to the founding edition page with the same code, so a first purchase made that way counts as that founder’s referral, as described under referral links. the page asks search engines not to list it.
sponsors. a company can pay to show its name and one link in the header of the founding edition page (the sponsor page). it gives a company name, a link, the days it books and its email; memoe keeps them with the payment, and nobody sees the email. the name and the link are shown to every visitor, marked “sponsored by”, only while a banner that a person at memoe approved is running; the link opens in a new tab and, once you follow it, that site’s own policy applies. a sponsor’s payment counts toward no total or list, and memoe doesn’t count how many visitors see a banner or follow its link. if a sponsor isn’t approved, the payment is refunded in full. a company can also offer its own price for a slot: the offer puts a hold on its card at Stripe (nothing is charged until a person at memoe says yes, and the hold is let go on a no or after six days); memoe keeps the offer and its answer with the booking, nobody else sees the amount, and an offer that isn’t accepted is kept as a record with no charge. the logo slot also takes a picture you upload: memoe checks it, shrinks it, saves it again as a new picture without anything the original carried (such as a location) and shows it to every visitor while the banner runs; it is deleted if the booking is refunded or taken down.
country takeovers. a buyer can pay for the “larpiest countries” banner to show a country they choose and a name they type for a few hours. the country and the name are shown to every visitor while the takeover runs, so type a name you are happy to show; the email you give with the payment is kept with the purchase as for every purchase here and is never shown. a takeover is a purchase of the founding edition, so it is counted in your total, in the leaderboard if you opted to be listed, and in the totals by billing country, which never name anyone. memoe keeps the country, the name, the hours and the time it ran with the payment.
where it is kept, and for how long. founding edition records are kept in a database hosted by Supabase and handled by memoe’s server on Vercel. records of purchases are kept for as long as tax and accounting law requires. the rest is kept until you ask us to delete it, as described under deleting your data. memoe also keeps an audit log of changes to purchases, entitlements and moderation decisions, which names a purchaser by an internal number, not their email.
domain sales
memoe.co/domains sells a few domain names in live auctions. looking at the page asks you for nothing, and the page keeps nothing in your browser until you start to bid. this is what is kept if you do, and why.
what you give before your first bid. your email, a tick in a box that says you have read and understood the domain terms of sale in full, and an optional phone number and an optional name to show. then Stripe’s own page, which shows your email, asks for your card, your full name as it is on the card and your billing address, and memoe never sees the card number. Stripe may ask your bank to confirm the card (3-D Secure). the details are asked for because they are how we know who bought a domain and how we answer a question about the payment.
what memoe keeps. your name and email, and your phone number if you gave one; the card’s brand, last four digits, country and fingerprint (a code Stripe makes for a card, so the same card is recognised); your billing address and its country; what your bank did about 3-D Secure; the time you ticked the box and the version of the terms; the network address and browser you used when you ticked it, and the network address of each bid; and every bid you place, with its amount and time. a sale also keeps the charge, any refund or dispute and where it stands, and the transfer of the domain. these are used to run the sale, to stop fraud and to answer a payment dispute: if you dispute a charge with your bank, memoe gives the bank this record. they are kept as long as a dispute or the law requires, and are deleted when you ask us to, except where a sale or a dispute needs them.
what is public. a bid shows a name you chose to show, or “bidder” and a number, and the country in your billing address. never your full name, email, phone number or card.
cookies. saving a card sets one cookie for up to two hours so the page can match you to the card when you come back from Stripe; once the card is saved, one more for 30 days holds a signature and a number that says which bidder you are on this browser. both are read only by memoe’s server, hold nothing else about you, and are removed by not you? forget this browser on the page. nothing else is kept in your browser.
who sees it. Stripe takes the card and the charge under its own privacy policy. memoe’s server texts the owner of memoe about a sale or a problem with one, using the domain, the price and a sale reference, never your name, email or phone number. the details are in the same database as the founding edition’s, hosted by Supabase and handled by memoe’s server on Vercel. a domain buyer also gets the same preorder benefits as the main site (the app at launch, the pro discount and a founder badge); they are claimed by email and use only what you write to us.
the beta sign-up
memoe is on the App Store now, and this website no longer offers a beta sign-up. memoe.co/waitlist still goes to the form that was used. it comes from Tally (tally.so), which acts for us, and Tally’s own privacy policy applies to what happens there. nothing is loaded from Tally unless you open that address.
if you signed up while the form was offered, you gave Tally your first name, last name and email, and it stores them for us. we use them only to email you about the beta, about memoe being live and about the launch. we never sell them, and we don’t share them for advertising. after you signed up, the window offered a card to share with friends; sharing went through your phone’s own share sheet, and we never saw who you sent it to. while the sign-up was offered, your browser could remember one random code so your invite link worked (in its local storage, not in a cookie, and nothing else was kept there): the link carried that code, a friend who opened it passed it on to the sign-up form, and Tally received the code with the sign-up, so we could count the sign-ups that came through each link. the website no longer makes that code; one made earlier stays in your browser until you clear its data, and is used for nothing.
we keep them until you ask us to delete them, or one year after launch, whichever comes first. to have them deleted, write to info@commutegeek.com. we delete them and ask Tally to delete them as well.
changes and contact
if memoe changes what it sends or saves, we’ll update this page and the date at the top before the change ships, and ask again in the app where it matters. paid features, such as memoe pro, are bought through the App Store, and Apple handles the payment. the founding edition is the exception: it is paid on this website, through Stripe.
questions? info@commutegeek.com.