Privacy policy
Reppin privacy policy
Reppin is in private, invitation-only development. This policy describes what Reppin does with information today: this website, Reppin's closed application service, and the internal research tooling that uses Google Drive. It will be revised before Reppin opens to the public.
1. Where Reppin stands today
Reppin is a concert-tracking identity platform for live-music fans, being built in Oklahoma City. It is not open to the public: there is no public sign-up and no app to download. Three things exist today, and this policy covers each in turn:
- This website (section 2) — static informational pages.
- Reppin's application service (section 3) — running, but closed. Only people Reppin has individually invited can create an account, and Reppin processes their information to operate those accounts.
- Internal research tooling (sections 4–10) — run by Reppin's founder on the founder's own equipment; it reconstructs live-music history from public web archives and keeps backup copies of that research in the founder's own Google Drive. This is the only activity that involves Google user data, and it involves one Google account: the founder's.
2. This website
This site is static pages. It sets no cookies, runs no scripts, loads nothing from third parties and uses no analytics. The host that serves it keeps ordinary web-server access logs (requested address, time, IP address, browser identification) for its own operation, as hosts do; Reppin does not combine those logs with any other information or use them to identify visitors.
3. Reppin's closed application service
Reppin operates an application service (at api.reppin.live) that is in a closed proving state. It is not open to the public: creating an account requires an invitation that Reppin issues individually, and so far those accounts belong to Reppin's own founder and testers. For an invited person, the service processes what is needed to create and operate an account — an e-mail address and its verification, sign-in credentials or a link to a sign-in provider the person chooses (such as Google or Discord), a session cookie, and the service's operational logs. That information is used to run the account and for nothing else; it is not sold or used for advertising.
Before Reppin opens accounts to the public, this policy will be replaced by one that describes the application's data practices in full, including what the product itself stores about shows and attendance. Until then, nothing described in this section applies to anyone Reppin has not invited.
4. Internal research tooling and Google Drive
Reppin operates an internal application registered with Google under the name "Reppin Seeder". It is a research and evidence-preservation tool, not a product: it has no public interface, no user accounts and no sign-up, and it is used by one operator — Reppin's founder. Google requires applications that use Google APIs to say what they do with Google user data; this section and the following six exist for that reason.
The tool does two distinct things, and only the second involves Google:
- Public-web research. It requests archived copies of public web pages (venue calendars and similar) from the Internet Archive and stores what it receives on the operator's computer, where the operator reviews it. No Google service or Google account is used for this (see section 11).
- Backup to Google Drive. After a research run, it copies the files it produced into the operator's own Google Drive and reads them back to verify the copy. This is the only use of Google user data.
5. Google Drive access granted
The application holds Google's per-file Drive permission, https://www.googleapis.com/auth/drive.file. Google's account permissions page shows the existing "Reppin Seeder" authorization as having access only to the specific Google Drive files used with the app. The application has no permission to see or change the rest of the Drive, and no access to Gmail, Contacts, Calendar, Photos or profile information beyond what Google provides to complete sign-in.
What that permission does and does not mean: Google limits the application to the files it created (or that the account owner explicitly opens with it), but within those files Google's permission allows an application to see, edit, create and delete them. Google does not restrict which of those operations the application performs. The narrower behaviour described in section 7 — write once, never overwrite or delete — is Reppin's own restriction, built into the tool, not a limit Google enforces.
If the application's permission ever changes, this policy will be updated before the change is used. If Google's consent screen ever asks for anything broader than per-file Drive access, the tool's configuration has drifted from this policy and the operator should decline and correct it before continuing.
6. Information the tooling processes
The tool writes the following kinds of files to Drive. All are produced by the tool itself; none is read from Drive or from any other Google service.
- Copies of archived public web pages obtained from the Internet Archive.
- Databases derived from those pages: lists of advertised events, performer names as printed, dates, and the tool's own review notes.
- Run logs and integrity manifests (file names, sizes and checksums) that let a backup be verified later.
Through Google sign-in, the tool's authorization is tied to the operator's Google account identity. The tool stores the resulting access credential locally (section 9) and does not record the Google account's e-mail address, name or other account details obtained from Google in its files or reports.
7. How Google Drive is used
The tool performs these operations, and is built to perform no others:
- List the files in the folder it created, reading their names, sizes and the checksums Google reports.
- Upload new files into that folder. It is built to write each file once and to refuse rather than replace a file that already exists.
- Read back the files it uploaded, to confirm byte-for-byte that the backup matches the original.
It is built not to delete, move, rename, share or change the permissions of any Drive file. Those restrictions are enforced in the tool's own code and tested; they go further than Google's permission requires (section 5), which would allow the application to edit or delete its own files. They are properties of this software as written, not guarantees about Google's platform or about any other software that may hold access to the same account. Reading only its own files is, by contrast, enforced by Google's per-file permission.
Google user data is used only to provide this backup function. It is not used for advertising, is not sold, is not shared with third parties, is not used to train machine-learning or artificial-intelligence models, and is not used to make decisions about any person.
8. Storage, sharing, retention
Backup files live in the operator's own Google Drive, under Google's terms and security. The originals, and a second local copy, live on the operator's computer. Apart from Google Drive (for the backup) and the Internet Archive (for the research in section 4), the tool's only other destination is the operator's own private source-control repository, where it keeps its mission records — including the names and checksums of the backups it has made. Beyond those checksums, no information obtained from Google leaves the operator's computer or the operator's Drive, and no third party receives Drive file content from the tool.
The tool never deletes anything from Drive. Backup files remain until the account owner deletes them in Google Drive; deleting the folder the tool created removes every file it placed there. The tool keeps no copy of Google user data anywhere other than the operator's own computer, the operator's own Drive, and the backup checksums in its mission records.
9. Security and its limits
The access credential Google issues is stored in the configuration of the transfer program the tool uses on the operator's computer. The tool's own code is written never to print, log or transmit that credential, and its reports pass through a filter intended to remove credential-shaped text before anything is written. Google's per-file permission (section 5) limits that credential to the files the tool created. It does not make those files safe from a misused credential: anyone able to use it could read, change or delete them, because Google's permission allows that and the tool's own write-once restrictions bind only the tool's code.
These are reasonable measures for a single-operator tool, not a guarantee. The security of the backups also depends on the security of the operator's computer and Google account, which are outside this software's control. No method of storage or transmission is completely secure.
10. Revoking Google access
The account owner can withdraw the application's access at any time from Google's account permissions page, myaccount.google.com/permissions, by removing "Reppin Seeder". After revocation the tool can no longer list, write or read the backup files; the files themselves stay in Drive until the account owner deletes them.
11. Public-web research and other people's information
The research files described above are derived from publicly archived web pages and can contain names of performers, venues and promoters as those pages printed them, together with dates of advertised events. That material is public information about public events. It is not Google user data, is not obtained from Google, and is handled as research evidence under the operator's review: an advertised listing is treated as a claim to be checked, never as an established fact about any person. Nothing from it is published on this site. Anyone with a question about such a mention may use the contact in section 14.
12. Opening to the public
When Reppin opens accounts or any feature to the public, this policy will be replaced first by one that describes exactly what the product collects, why, and how it is kept. Nothing in sections 4–10 describes a consumer feature.
13. Changes to this policy
If the tooling's use of Google user data changes, or the application service's practices change, this page will be updated before the change takes effect and the effective date above will move. Reppin's use of Google user data is limited to what this published policy describes.
14. Contact
Questions about this policy, about Reppin's handling of information, or about a mention in Reppin's research material: reppin.live@gmail.com.