Privacy, in plain language.

1. 1

   You record your OJT work

   Profile details, logs, timer data, photos, notes, and saved reports are written to local app storage.

2. 2

   You choose what happens next

   You can keep working offline, export a file, make a backup, request an AI report, or watch a rewarded ad.

3. 3

   Only the selected feature receives data

   Exports go to the destination you choose. AI prompts go to the AI processing chain. Ad interactions go to Google Mobile Ads and the credit backend.

4. 4

   Results return to the device

   Generated text is shown in Interna and is saved locally only when you save it. Earned credits are verified against backend records.

AI is used only after you request a narrative report or a weekly learning-note suggestion. Interna builds a text prompt from relevant data for the selected report range. That prompt can include your name, course, school, company, supervisor, current and previous work-log text, dates, quantities, time ranges, and an optional weekly learning note.

Proof photos are not included in the current AI prompt. The prompt passes through Interna's Supabase Edge Function and is sent to Google Gemini first. If a retryable service error occurs, the same prompt may be retried through xAI Grok and then an NVIDIA-hosted model. The function records prompt length in its application log, not the prompt text, but platform invocation logs and each provider's own processing rules may apply.

AI output is returned to Interna and shown for review. It becomes a saved narrative only when you save it. AI text can be incorrect or incomplete; review it before submitting it to a school, coordinator, or supervisor.

On Android and iOS builds, you can choose to watch a rewarded ad to earn an additional AI-report credit. Interna requests non-personalized ads, but the Google Mobile Ads SDK can still automatically process an IP address, general location estimated from that address, app interactions such as ad views and taps, diagnostics, and device or account identifiers for advertising, analytics, and fraud prevention.

Interna creates a time-limited reward session before showing an ad. The backend stores the session status, install and device bucket, reward amount and type, ad-unit and transaction details when provided, timestamps, and verification results. This prevents a reward from being reused or claimed for a different installation.

The current app starts with a local free allowance and later provides a recurring weekly free allowance. Rewarded credits have a separate backend weekly limit. Exact credit limits may change without changing the categories of information described here. Watching an ad is optional; you can continue using offline reports and the rest of the app without watching one.

• Camera and photo library: requested only when you choose to take or attach a proof image. You can keep logs without photos.
• Notifications and alarms: used for optional shift and timer reminders. You can disable reminders in Interna or revoke notification access in device settings.
• Biometrics: used only for the optional app lock. You can turn the lock off in Interna.
• Files and sharing: used when you select a backup to restore or choose where to save or share a PDF, DOCX, CSV, photo report, or JSON backup.
• Internet: used for AI generation, rewarded ads, credit and trust checks, provider-policy links, and the privacy-policy page.

Interna's current feature flow does not use precise location or microphone recording. Device settings may show permissions contributed by underlying app modules; the app source does not contain a current location-tracking or audio-recording feature.

Backups include logs, proof photos, settings, saved narratives, and weekly learning notes. They do not include or restore AI credits, reward-credit records, backend trust decisions, or the secure installation identifier. Restoring a backup overwrites the matching local data currently in the app.

You can avoid sending an AI prompt by using the offline report option. You can avoid advertising-related processing by not starting a rewarded ad. You can revoke app permissions through your device settings.

Interna uses encrypted HTTPS connections for supported backend, AI, advertising, and policy requests. Native installations use secure device storage for the installation identifier where supported, and the optional biometric lock relies on the operating system. Ordinary local logs and photos rely on the device's app sandbox and operating-system protections; Interna does not separately end-to-end encrypt every local record or exported file.

Supabase, Google, xAI, and NVIDIA may process information in countries outside your own. Privacy and data-protection rules can differ between countries. No digital system is completely secure, so protect your device, screen lock, proof photos, exported reports, and backup files.

Interna is designed for OJT and internship record-keeping. It is not directed to young children. Students who are not legally able to consent on their own should use the app only with appropriate parent, guardian, school, or institutional guidance.

Before photographing a workplace, document, colleague, customer, patient, or screen, make sure you have permission and follow your employer's or school's rules. Do not place confidential workplace or third-party personal information in an AI prompt unless you are authorized to do so.

This policy may be updated when Interna's data handling, providers, permissions, or features change. The effective date at the top will be updated when a revised policy is published. Material changes should be reviewed before continuing to use the affected online feature.