RememberKit Back to RememberKit

Your data

Privacy policy

Last updated October 19, 2026

RememberKit helps you create and share travel journals. This policy explains how we handle information when you use RememberKit, including journals hosted on RememberKit subdomains and custom domains.

Information we use

We use your account identifier, verified email address, and available display name and profile picture to sign you in, identify your contributions, and manage access to blogs. Our shared login service uses Auth0.

We store the content and settings you provide, such as posts, photos, captions, travel routes and locations, comments, invitations, email subscriptions, and connected import sources. We use this information to provide the journal features you choose.

If you contact support, we store your message and account details to respond. For paid plans, Stripe handles payment collection; RememberKit stores customer identifiers, subscription status, and plan information rather than full payment-card details.

Google Photos

Connecting Google Photos is optional. Google asks you to approve access to selected photos and your account identity. RememberKit receives your Google account identifier and verified email address so that the correct account appears in your integrations list and photo-import buttons. We do not receive your Google password.

You choose the items to share in Google's photo picker. RememberKit can retrieve the items shared through those selections; it cannot browse your entire Google Photos library. We download selected photos and their associated file information into the post editor. Videos are skipped.

Imported photos enter the normal draft queue. They may be saved in your browser for draft recovery, and are uploaded to RememberKit when you save the post. Saving a draft does not publish it. When you publish a post, its photos are shared according to that blog's access settings.

We store encrypted Google access and refresh tokens with the blog's integration to keep the connection available for future imports. Tokens are used on the server and are not included in editor drafts or public posts.

We use Google data for account identification and the photo-import features described here. We do not sell Google user data, use it for advertising, or use it to train AI models. We follow the Google API Services User Data Policy, including its Limited Use requirements.

To disconnect, remove the Google Photos integration in Admin → Import → Integrations. This removes the account details and saved tokens from that blog's live integration settings. You can also revoke RememberKit's access through your Google Account connections. Disconnecting does not remove photos already copied into drafts or posts; delete those copies separately if you no longer want them.

Who can see your information

Public blogs make published posts, photos, routes, and public author information available to visitors and search engines. Private blogs limit their journal content to authorized members. Blog owners control access and can manage content. Choose what you upload and publish with those settings in mind.

We use service providers to operate RememberKit, including Cloudflare for hosting, databases, storage, and delivery; Auth0 for login; and Stripe for paid subscriptions. Google processes authorization and photo selection when you connect Google Photos. Blog owners may configure other integrations or email providers for their blogs.

We may access or disclose information when needed to provide support you request, investigate security or abuse, or comply with legal obligations. Access to Google data is subject to Google's Limited Use requirements.

Storage, deletion, and your choices

You can edit or delete journal content through the blog's admin tools and remove optional integrations. Removing a post or photo from RememberKit does not delete the original from Google Photos or another source. Removing an integration does not delete content already imported from it.

We retain account information and journal content to operate your account and blogs until you remove them, subject to backup retention and any records needed for billing, security, or legal obligations. Historical backups can retain older copies after live data changes.

The account dashboard provides account deletion, and a blog's plan page provides blog deletion. Blog deletion removes its content, settings, and backups. Account deletion also retires historical backups containing that account's information 30 days after live data is removed. Deleting your RememberKit account does not delete the shared BoatKit login or your Google account.

Contact us at ddr@boatkit.io to ask about your information, request correction or deletion, or get help exercising privacy rights. We may need to verify your identity before acting.

Cookies and browser storage

RememberKit uses cookies for sign-in and browser storage for preferences and recovering drafts, including pending photos. Clearing RememberKit's data in your browser removes local copies; it does not delete posts or photos already saved on the server. External login, payment, and photo-picker services handle their own cookies and data.

Contact and updates

For privacy questions about RememberKit, email ddr@boatkit.io. For questions about a particular journal's content or access, you can also contact its owner.

We will update this page when our practices change and revise the date above. Changes to how we access Google data will be reflected here and in the relevant connection notice.