SuruLab
WorkAboutNotesContact日本語
SURULAB · PRIVACY

SipWrite Privacy Policy

Effective date: October 29, 2026

SuruLab (“we,” “us,” or “our”) provides SipWrite, an English grammar and usage checking app. This policy describes the information processed when you use SipWrite. Contact us at surulab.inc@gmail.com with privacy questions or requests.

Information stored on your device

Your diary entries, typed text, editable Apple Pencil handwriting, handwriting recognition results, and saved feedback are stored locally on your device. SipWrite does not upload your diary history or handwriting files as part of ordinary local saving. Deleting the app or using the in-app controls removes local content, subject to the device’s backup and operating-system behavior.

Information processed for an English check

When you request an English check, SipWrite sends the text you submit, together with the instructions needed to check it, to SipWrite’s backend. Handwriting is recognized on your device; SipWrite sends the resulting text for checking, not the Pencil drawing. The backend sends the submitted text to Groq to generate grammar and usage suggestions. Groq processes the text as our service provider. We do not send your local diary history or handwriting drawing to Groq.

The check is intended to correct meaningful grammar and usage issues while preserving the writer’s meaning and voice. It is not intended to provide medical, legal, financial, or other professional advice. Avoid submitting sensitive personal information that is not needed for an English check.

We have enabled Groq’s Zero Data Retention (ZDR) control for inference APIs. Groq states that this prevents retention of inference inputs and outputs for system reliability and abuse monitoring. Groq still retains usage metadata that does not include submitted text or generated responses. SipWrite uses inference APIs and does not use Groq batch processing, fine-tuning, or LoRA features. These controls and practices are governed by Groq’s current terms and data settings and may change. See Groq’s data handling documentation.

Anonymous account and service records

SipWrite creates a pseudonymous Supabase Auth account so the backend can authenticate requests and apply usage limits. You do not provide an email address or password to create this account. The account has an internal user identifier and an authentication session stored securely on your device.

To operate the checking service, we process limited operational records: a pseudonymous user identifier, request identifier, keyed digest of the submitted request, processing status, token counts, model and prompt version, error category, and timestamps. These records do not contain the submitted writing or generated feedback. We do not intentionally include writing, handwriting, authentication tokens, or provider keys in application logs. Google Cloud and Supabase may process connection, authentication, and infrastructure information, such as IP address, to deliver and protect their services.

The backend schedules deletion of request records older than 24 hours. Cleanup runs hourly, so deletion may occur later than the 24-hour threshold if a scheduled run is delayed or fails. Per-user usage counters are removed when the associated anonymous account is deleted. Time-bucketed usage counters are retained until they pass a database cleanup cutoff of two UTC calendar days; because cleanup is hourly and the cutoff is based on a date boundary, this is not an exact 48-hour expiry. Project-wide daily usage counters are not associated with a particular account and are not removed when an individual account is deleted.

The app's own request records are separate from provider-managed infrastructure logs. Terraform does not configure a custom Cloud Logging retention period. If the Google Cloud project retains its default log-bucket settings, application and service logs in the `_Default` bucket are retained for 30 days; entries in Google's `_Required` audit log bucket are retained for 400 days. Our Supabase project is on the Free plan, whose API and database logs are retained for 1 day under Supabase's current plan terms. Provider-managed retention settings and plan terms may change. See Google Cloud Logging retention and Supabase log retention.

We do not use submitted writing for advertising or sell personal information.

Account and data deletion

You can request deletion of the anonymous SipWrite account from the app’s Settings. The server queues the request, blocks further checks, waits for any in-progress check to finish, and then deletes the Supabase Auth account, that account's request records, per-user usage counters, and temporary activity/deletion records. If deletion is temporarily unsuccessful, the hourly cleanup job retries it. Project-wide usage counters are retained and are not attributable to the deleted account. The app's diary entries, editable handwriting, recognized text, and saved feedback are stored locally and are not deleted by this server-side account deletion; remove them separately using the app’s local data controls or delete the app. Deleting the app alone may not delete the server-side anonymous account. Provider-managed infrastructure and security logs may persist until their applicable retention period expires.

You can also contact surulab.inc@gmail.com for help with a privacy request. We may ask for information reasonably needed to identify the relevant request or account. We may retain information when required by law or temporarily needed to address security, fraud, or service-integrity issues.

Children

SipWrite is not directed to children under 13, and we do not knowingly collect personal information from children under 13.

Changes to this policy

We may update this policy when the app or its data practices change. We will post the current version here and update the effective date.

Contact

For privacy questions or requests, email surulab.inc@gmail.com.

For app support, visit SipWrite Support.


Need help with the app? Visit SipWrite Support.