Privacy policy

Who we are

Ramble is operated by the team behind the Ramble product. If you have questions about this policy or your data, contact us using the support details in the App Store listing or sign in on the web and use Settings.

What Ramble does

You record voice Rambles on your iPhone. Audio is transcribed and lightly tidied (punctuation, removing ums and false starts) so each Ramble is easier to read. Your words stay yours; we do not rewrite or polish for meaning. Tidied Rambles sync to your account so you can read them in the app and on the web, organise them into albums, and mark favourites.

We do not see your Rambles

We do not read, listen to, or review your Rambles as part of running the Service. Your Rambles are processed automatically for transcription and tidying, and stored so you can access them. We only access Ramble content when you ask for support, when we need to fix a technical problem you report, to keep the Service secure, or when the law requires it.

Information we collect

Account information

• Email address — used to create and sign in to your account.
• Password — stored only as a secure hash; we never store your plain-text password.
• Account settings — such as your recording minute allowance and usage totals associated with your account.

Your content

• Rambles — transcripts, tidied text, any text you edit, album names, favourites, timestamps, and recording duration.
• Albums — names you choose and which Rambles belong in each album.

We store this content in our PostgreSQL database on EU servers, linked to your account, so it syncs between the app and the web.

Audio

Audio files are stored on your phone. They remain on your device in the app’s local storage. We do not store your audio files on Ramble’s servers. To transcribe a Ramble, the app sends audio to our transcription provider (see below) for processing. Temporary copies may exist on that provider’s systems for the time needed to return a transcript.

Waitlist

If you submit your email on our marketing site to join the waitlist, we use that address only to contact you about Ramble (for example launch news). You can ask us to remove it at any time.

Usage and diagnostics

• Usage logs — when transcription or tidying runs, we may log operation type, success or failure, audio duration or text length, token counts, latency, app version, and related metadata. This supports billing against your minute allowance, reliability, and abuse prevention.
• Error logs — if something fails on the web or in the app, we may log error messages, paths, HTTP status, user agent, app version, and optional account linkage to fix problems.
• Web sessions — when you use the website, we use session cookies and similar technologies so you can stay signed in and protect forms (CSRF).
• API access — the app uses an API token tied to your account to sync Rambles securely over HTTPS.

How we use information

We use your information to:

• Provide transcription, tidying, sync, search, and account features;
• Enforce fair use and minute allowances;
• Keep the Service secure and fix bugs;
• Respond to support requests and legal obligations;
• Send waitlist or product messages you have asked for.

We do not use your Rambles to train Ramble’s own machine-learning models.

Third-party processors

We rely on trusted providers to run Ramble. They process data only to perform services for us, under their terms and our instructions:

• AssemblyAI — speech-to-text. Audio you choose to transcribe is uploaded to AssemblyAI for transcription. We follow AssemblyAI’s terms and data policies for API use.
• OpenAI — text tidying. We send transcript text to OpenAI’s API so fillers can be removed and punctuation added, without changing your meaning. We follow OpenAI’s terms and data policies for API use.
• Stripe — payment processing when you pay on the web. Stripe handles payment details; we receive billing status and limited customer information needed to manage your subscription or purchase.
• Hosting — the web app and PostgreSQL database are hosted on cloud infrastructure (including Railway) on EU servers.
• Google Fonts — the website loads the Inter typeface from Google; your browser may request fonts from Google’s servers (see Google’s privacy policy).
• Apple — if you download the app from the App Store, Apple processes purchase and device information under Apple’s policies.

On-device transcription (for example when cloud keys are not configured in development builds) may use Apple’s on-device speech frameworks; that processing stays on your device.

Encryption and security

Data in transit between your devices, our servers, and third-party APIs is protected using TLS (HTTPS). Passwords are hashed. We apply reasonable administrative and technical measures to protect account and Ramble data; no online service can guarantee absolute security.

AI and training

Your voice and your Rambles are yours. Nothing you send through Ramble is used to train our models. Transcription and tidying use AssemblyAI and OpenAI as processors only; we use their APIs in line with their policies, which are designed for business API use rather than training on your content. We do not use your Rambles to build or improve Ramble’s own models.

Retention and deletion

• You can delete individual Rambles and albums in the app or on the web.
• You can delete your account from the app, which removes your account and associated Rambles from our systems subject to brief backup retention.
• We may retain minimal logs for security, billing disputes, or legal compliance for a limited period.

Your rights

Depending on where you live (including the UK and EEA), you may have rights to access, correct, delete, restrict, or export personal data, and to object to certain processing. To exercise these rights, contact us as above.

International transfers

Some providers may process data outside the EU. Where that happens, we rely on appropriate safeguards (such as standard contractual clauses) offered by our processors. Your Ramble text stored in our database is hosted in the EU as described above.

Changes

We may update this policy from time to time. We will post the new version on this page and update the “Last updated” date. Continued use of the Service after changes means you accept the updated policy.