Conjuguinho privacy policy

Updated 1 October 2026

Conjuguinho is developed by Daniel Braithwaite. Optional usage sharing is unavailable in this version, and no usage summaries are sent. A future service will need an updated policy and your explicit choice before it can collect and send optional summaries.

You can use Conjuguinho without an app account, advertising or a subscription. The optional sharing choice does not reduce free or purchased access.

Your learning on your iPhone

Your optional name, chosen tenses, saved verbs, answers, lesson drafts, practice history, scores and preferences are stored on your iPhone. They are not uploaded to the developer. The learning content is included in the app.

The optional streak widget reads a small local activity summary shared with the app. Daily reminders are local notifications scheduled with your permission; they do not use a developer push-notification service. Haptic preferences also remain local.

In Add a verb, the balls respond when you tilt or gently shake your iPhone. The app uses current device-motion samples only while the ball field is active. It stops reading motion while you search, view verb details, leave the app or use Reduce Motion. The samples are not saved or uploaded, and the app does not read fitness or activity history. You can also use search and touch controls without moving your phone.

The app may keep local recovery copies when migrating, recovering or resetting progress. Reset progress replaces the active learning record; it is not a promise to erase every recovery copy. Removing the app and managing its storage are controlled by iOS. Your device or iCloud backup settings may include app data. Conjuguinho does not provide its own cloud synchronization, and the developer has no copy of your learning history to restore.

Optional usage summaries

Sharing is off by default. The app does not record summary counters before you opt in. This build has no configured destination and cannot send summaries. Learning and purchases work without this optional feature.

The proposed future feature would use coarse feature and technical-failure counts to improve the app. It would exclude names, answers, accuracy, lesson or verb identities, learning history, purchase records and persistent user/device identifiers. That proposal is not an active service, and this policy does not turn on consent. The recipient, exact fields, retention and withdrawal controls must be explained before sharing becomes available.

Feedback and privacy requests

Settings → Feedback & privacy → Send feedback opens the Conjuguinho Google Form. You can use the same form to ask Daniel Braithwaite about privacy or request access, correction or deletion of a feedback response: Conjuguinho feedback form

Only the message is required. A feedback category, manually entered app/iOS versions and an email for a reply are optional. The form is configured not to collect email automatically or require Google sign-in. It has no file-upload question, public response summary or saved response draft. Responses are reviewed in the developer's private Google Forms dashboard.

Nothing from the app is attached or prefilled automatically. The app and iOS versions are displayed in About this version for you to include manually if useful. Review what you write and leave out passwords, payment details and other sensitive information.

Submitting the form sends the fields you enter to Google and makes them available to the developer. Google also processes information about browser requests under its own privacy policy. The form is not a promise of anonymity: a reply email, message content or information processed by Google may identify you. Google's policy is available at Google privacy policy.

The developer uses responses to handle support, Portuguese corrections, suggestions and privacy requests. An optional reply address is used for that conversation, not marketing. Feedback is not published for other app users to read or combined with learning history.

Responses are kept only as long as needed to handle the report, follow up and maintain necessary support records. They are reviewed and deleted regularly. Google's service retention and backups are separate.

For an access, correction or deletion request, describe the report and approximate submission date in the form. Include a reply address only if you want a response. We may be unable to reply or identify a report without enough information. Your rights may also depend on where you live.

Apple purchases and diagnostics

Apple processes the one-time Full version purchase, restoration and refunds. Conjuguinho reads Apple's verified entitlement to unlock content. The developer does not receive your payment-card details, and the app does not send learning data, receipts or purchase history to a developer server. Restoring a purchase restores access, not local learning history. Apple's services operate under its privacy policy at Apple privacy policy.

Apple may make individual crash and hang reports available to the developer to diagnose failures and improve app performance. Reports can include app and iOS versions, device model, technical stacks, event times and device-level diagnostic identifiers that link reports from the same device. The developer uses these reports for troubleshooting, not advertising or tracking, and keeps downloaded reports privately only as long as needed to investigate and follow up on the issue.

App Store diagnostic reporting depends on Apple's settings and your sharing choices. Review Settings → Privacy & Security → Analytics & Improvements. TestFlight beta crash reporting follows Apple's separate automatic reporting rules. These Apple-managed reports are separate from the unavailable custom usage-summary service.

Conjuguinho writes fixed technical failure codes to the device's Apple system log, for example when saving progress fails. These entries contain no names, answers, learning history, arbitrary error descriptions or account identifiers. The app does not read back or upload these logs, use a third-party crash-reporting SDK, or attach logs to feedback. Apple controls system-log and Apple-report retention.

Privacy and support website

The public privacy and support pages are hosted on GitHub Pages. Our page code has no analytics scripts, advertising, embedded forms, third-party fonts or cookies. Reading the policy inside the app uses bundled text and does not contact GitHub.

When you visit the website, GitHub receives the web request. GitHub states that it logs and stores visitors' IP addresses for security, including when visitors are not signed into GitHub. GitHub controls that hosting data and its retention under its privacy statement; we do not promise zero IP retention or storage only in your country. GitHub describes Pages data collection at GitHub Pages data collection and its privacy practices, retention and privacy contact options at GitHub privacy statement.

Following an external link, such as Send feedback, opens the destination service, whose privacy practices apply. The website does not attach your local learning data to those requests.

Your choices

You can use the app without submitting feedback, edit local preferences, disable daily reminders, and manage Apple analytics and backup settings. There is no Conjuguinho account to delete. To contact the developer, use the feedback form above; no email address is required unless you want a reply.

This policy will be updated when the app's data practices change. A material expansion of optional collection requires a new choice before that collection begins.