Privacy notice
Version: 18 November 2026
Who is responsible?
Daniel Schreiber, Dietrich-Bonhoeffer-Str. 29, 63075 Offenbach am Main, Germany, operates AutoShare Photos and is responsible for the processing described here. For privacy questions or requests, email daniel@autosharephotos.com.
Visiting the website
We use Cloudflare to deliver the public website and route connections to our operator-run application server. This involves technical request data, including IP addresses, browser information, requested addresses and connection times. These data are used to deliver the service, maintain availability and prevent abuse. Cloudflare can process traffic passing through its network.
Our signup and login abuse controls use hashed email or IP-based keys, counters and expiry times. Hashing these values does not make them anonymous. Expired rate-limit records are removed when subsequent requests trigger cleanup.
The legal basis is our legitimate interest in delivering and protecting the service (Article 6(1)(f) GDPR).
Joining the waitlist
We store your email address, the page language you used, signup and confirmation times, confirmation-link hashes and expiry times, and records of email delivery and manual invitations. We use these to confirm your request, manage future access and document eligibility for the advertised early-bird offer.
We send a confirmation link, valid for 24 hours. After you explicitly confirm, we send a welcome email with a blind copy (BCC) to the operator so that we can manage invitations. Verification emails and login codes are not copied to the operator. We send only waitlist and access-related messages, not a newsletter.
Invitations are selected and sent manually. Joining the waitlist does not create an account or grant access. There is no promised invitation date or queue position.
We process the waitlist and send these messages on the basis of your consent (Article 6(1)(a) GDPR). Reply to an email or write to the address above to withdraw consent or request deletion. Withdrawal does not affect processing that was lawful before withdrawal.
Our manual retention guidance is to review unconfirmed entries after seven days, confirmed entries without an invitation after 12 months, and ordinary waitlist records 30 days after a successful invitation. These are review points, not automatic deletion deadlines. We retain records only while needed for these purposes.
During routine cleanup, we preserve your email and first confirmation date, linked to your app account where available, to carry early-bird eligibility through the invitation process. This evidence is kept while needed to establish or administer that entitlement, based on our legitimate interest in honoring and documenting the offer (Article 6(1)(f) GDPR). An explicit request to delete your waitlist data also removes this evidence; we will explain that the proof of eligibility is being removed. Deleting waitlist data does not itself close an existing app account.
Invited accounts and Google Photos
Signing in to AutoShare Photos and connecting Google Photos are separate actions. App sign-in uses an emailed code. We store your verified email, account identity, invitation eligibility, login/session records and limited device/browser metadata needed for authentication. Codes are stored as hashes, work once and expire after five minutes. A necessary, secure session cookie keeps you signed in for up to seven days, renewed during continued use. Logout revokes the current app session. Expiry of a code or session does not imply immediate deletion of every related database record.
To connect Google Photos, you sign in to Google in an isolated browser running on our server, controlled through the app. Google receives your Google sign-in details. Our application does not ask you to submit a Google password to an AutoShare Photos form. The hosted browser profile retains Google login cookies, local storage and browser data so that sharing can continue unattended. That profile grants access to the connected Google session; it is not merely a list of the photos you selected. The operator administers the server and can access stored profiles and application data for operation and support.
We read album and face-group catalogs from your connected Google account, including names, identifiers, search selectors and shared-album access information. We store your chosen people, target album, sync start date and enable/pause setting, as well as synchronization schedules, results, errors and album membership history. Photo identifiers and capture dates help us select eligible photos and avoid adding the same photo again. History is retained across album changes so that previously shared photos stay remembered.
The original library and destination album remain in Google Photos. Our service does not build a separate photo library or run its own face-recognition model; it uses Google's existing face groups. For the people picker, we store small representative face photos for your account, including groups you have not selected. Only your account can view them in the app. The hosted browser also processes photo content and may cache images and other page data. Group names and photo metadata can relate to family members and other people who have no account here. Choose albums, people and sharing permissions with their privacy in mind.
Photos added to the target album become visible according to that album's Google sharing settings. Pausing automation or logging out does not retract photos already shared. Logging out of the app also does not disconnect the hosted Google session or stop enabled sharing. Pause sharing in the app to stop future scheduled additions; contact us to close your account and remove the stored Google profile.
We use account data to provide the service you request (Article 6(1)(b) GDPR), and necessary operational/security records to run, troubleshoot and protect it (Article 6(1)(f) GDPR). We retain account settings, profiles and history while needed to operate your account, including when sharing is paused. Closure and deletion are handled manually. We also consider necessary support, recovery and legal-obligation periods; there is no automatic account-deletion schedule.
Email and support
Resend delivers confirmation emails, login codes, invitations and operational alerts. It receives recipient addresses, message content and delivery metadata. Operational alerts go to the affected account owner with the operator copied (CC); welcome emails use the operator BCC described above.
Replies to our public address are forwarded through Cloudflare Email Routing to the operator's mailbox. Email delivery also involves the sender's and recipient's mail providers. If you contact us, we process your address, message and any attachments to respond and handle your request. Please do not email Google passwords or login codes.
The legal basis follows the purpose of the message: consent for waitlist messages, providing the requested account service or responding to pre-contractual requests (Article 6(1)(b) GDPR), and our legitimate interest in handling other enquiries and operational problems (Article 6(1)(f) GDPR).
Public-site measurement
We use Plausible Cloud, provided by Plausible Insights OÜ in Estonia, to understand
public-page use and count successful waitlist confirmations. We measure public
pageviews, time spent on the page, scroll depth and clicks on external web
links. We record a Waitlist Confirmed event after the API confirms success.
The private account and remote-browser pages are excluded.
We omit referrers and remove query strings and fragments from page URLs and external link destinations. For external links we record only the destination's origin and path. We do not supply email addresses, confirmation tokens, account IDs or other user-identifying custom properties. Requests still carry the IP address and browser User-Agent necessary for internet communication.
According to Plausible's data policy, it uses these transiently to derive approximate location and browser/device information and a daily, website-specific visitor identifier. It does not store raw IP addresses or raw User-Agent strings. It stores event/session records for statistics, rotates and deletes its identifier salt every 24 hours, and does not track visitors across days, devices or websites. Plausible uses no analytics cookies or persistent browser identifiers and processes visitor data in the EU.
Our legal basis is our legitimate interest in understanding aggregate demand and improving the public website with limited, privacy-conscious measurement (Article 6(1)(f) GDPR). The statistics are not used for individual advertising or access decisions; invitations remain manual.
Providers and international processing
The principal services involved are:
- Cloudflare, Inc. (USA): website delivery, network protection, API/remote-browser traffic routing and incoming email forwarding.
- Resend / Plus Five Five, Inc. (USA): transactional email and delivery records.
- Plausible Insights OÜ (Estonia): the public-site measurement described above.
- Google: your existing Google account and Google Photos service, which processes data under its own privacy terms.
Cloudflare, Resend, Google and email providers may process data outside the EEA, including in the USA. An EU email-sending region does not mean that all email data stays in the EU. Cloudflare describes reliance on the EU–US Data Privacy Framework and standard contractual clauses; Resend's data-processing terms include standard contractual clauses and describe its Data Privacy Framework participation. Google's transfer information explains its applicable safeguards. You can consult the linked terms or contact us for information about safeguards.
Provider details: Cloudflare privacy, Resend privacy and data-processing terms, Plausible data policy, Google privacy and international transfers.
Retention and your rights
We use the retention criteria explained above. Support correspondence and operational records are kept as needed to resolve requests, protect the service and meet applicable legal obligations. Backups and email-provider records can outlast the active database record; deletion requests are handled across the relevant operator-held records and providers, and deleted data must not be reintroduced through a backup restore.
Subject to the applicable conditions, you can request access, correction, deletion, restriction and data portability. You may object to processing based on legitimate interests for reasons relating to your situation, and withdraw consent at any time. Contact daniel@autosharephotos.com. These rights also apply to people depicted in photos or named in face groups; you do not need an AutoShare Photos account to contact us.
You may complain to a data-protection supervisory authority, including the Hessian Commissioner for Data Protection and Freedom of Information.
Providing an email is voluntary, but we cannot manage your waitlist request or app login without it. Connecting Google Photos is needed only to use the sharing service. We do not use your data for automated decisions producing legal or similarly significant effects.