PhotoToCalendar

PhotoToCalendar

Terms of Use &
Privacy Policy

  • Last updated:
  • Android & iOS
  • English

The Terms of Use explain how you may use PhotoToCalendar. The Privacy Policy explains how your information is processed and the choices available to you.

Your privacy at a glance

  • You choose what to scan

    Selected content is sent to Google Cloud Vertex AI after the App asks for your permission to use AI processing.

  • You confirm calendar events

    The App lists available calendars and adds approved events. It does not scan your existing appointments.

  • History is stored on your device

    Saved scans are kept locally for up to 365 days, subject to cleanup and a 500-entry limit. You can delete them earlier.

  • You have deletion choices

    Delete your signed-in account in Profile & Settings, clear history separately, or contact us about your data.

This is a summary. The full policy below explains provider processing, retention and deletion.

Contact the developer

Part A

Terms of Use

1Acceptance and the service

PhotoToCalendar (the “App”) is provided by its developer (“we”, “us”, “our”), reachable using the contact details below. By downloading, installing or using the App, you agree to these Terms of Use. If you do not agree, please stop using the App.

The App uses Google Gemini through Google Cloud Vertex AI to extract proposed calendar events from photos, PDFs, Excel files and shared text. You can review and edit the results before confirming which events to save to a calendar on your device.

The Privacy Policy describes data processing. Agreeing to these terms does not replace any separate consent that may be required.

2Accounts

You may use the App as a guest. Guest use creates a Firebase user identifier even if you do not sign in with Google or Apple. Some features, including purchasing credits, require sign-in. Keep your account secure and use only accounts you are authorised to access.

Signed-in users can sign out or request deletion through Profile & Settings → Delete Account. Guest users can contact us about their data. Continued use after signing out or deleting an account creates a new guest session. Deletion does not refund purchases or remove saved calendar events.

3Credits, purchases and free use

  • Credits are consumable units used to save events. The App may offer a free first save, limited free use or a save supported by a rewarded advertisement, as shown in the App.
  • Watching a rewarded advertisement may allow a save without spending credits; it does not necessarily add credits to your balance.
  • Scan, document-trial and free-save limits apply. Available allowances and purchase prices are shown in the App or the relevant store.
  • Purchased credits are for use within the App, cannot be transferred and cannot be exchanged for cash, subject to your statutory rights.
  • Apple App Store or Google Play processes payments; RevenueCat manages purchase verification. We do not receive your payment-card number.
  • For a refund, use the relevant store's refund process. For missing credits or a purchase problem, contact us. Mandatory consumer rights still apply.

4Advertising

The App displays Google AdMob banner and rewarded advertisements. Availability and rewards depend on successful loading and completion of the relevant flow and are not guaranteed. The current App requests non-personalised ads. See Part B, section 5 for advertising data.

5Review AI results before saving

AI output can contain incorrect or incomplete titles, dates, times, locations or descriptions. Review every event and correct its details before saving. The App does not guarantee accurate scheduling, reminders or calendar synchronisation.

To the extent permitted by law, we are not responsible for losses caused by relying on unverified AI output. This does not exclude liability or rights that cannot lawfully be excluded.

6Acceptable use and your content

Use the App lawfully. Do not submit content you are not entitled to process, infringe another person's rights, bypass limits or security controls, automate bulk requests, or disrupt the service.

Your content remains yours. You authorise the limited processing needed to analyse selected content, return results and save approved events. The App's code, design and branding remain the property of their respective owners.

7Availability and liability

The App is provided “as is” and “as available”, subject to law. Features depend on services and conditions including connectivity, device permissions, your calendar provider and app stores. We do not guarantee uninterrupted or error-free operation.

To the maximum extent permitted by law, we exclude liability for indirect or consequential loss, lost profits or loss of data. Nothing in these terms excludes liability that cannot be excluded or reduces mandatory consumer protections.

8Stopping use and account deletion

You may stop using the App at any time. We may restrict access where necessary to address misuse or a breach of these terms. Account deletion and local-history deletion are separate actions; see Part B, section 9.

9Changes to these terms

We may update these terms or the available features and allowances. Updated terms appear on this page with a revised date. Where law requires notice or consent for a change, we will provide it.

10Governing law

These terms are governed by Greek law, subject to mandatory protections in your country of residence. Jurisdiction is determined by applicable law; these terms do not remove any right to bring a consumer claim before a competent court in your country.

Part B

Privacy Policy

1Who is responsible

The developer of PhotoToCalendar is responsible for personal information processed to operate the App. This policy covers the Android and iOS App, identified as com.mathcoder.phototocalendar. Contact dimitristsoukalos@gmail.com about privacy, deletion or data requests.

Providers may also process information for their own purposes, including sign-in, payments and advertising. Their notices are linked in section 7.

2Information the App processes

Accounts and purchases

Firebase Authentication creates a user identifier for guest use. This is pseudonymous; guest use does not mean that no personal information is processed. Google or Apple sign-in involves authentication tokens and basic profile details made available by the provider, such as an email address and display name. Apple may provide a private relay email.

Cloud Firestore stores credit balances and update timestamps linked to your identifier. RevenueCat receives this identifier, including during guest use, to associate purchase records with the App user. Verification records can include a transaction identifier, product, credit amount, event type and processing timestamp.

Content you select

The App processes selected photos, camera images, PDFs, spreadsheet content, shared text and optional instructions. These may contain event details, names or other personal information in the source. Choose content you are entitled to share, including information about other people.

Technical and local information

Providers process technical information such as IP addresses, device or app information, authentication and integrity tokens, and operational logs. Firebase App Check uses Google Play Integrity on Android and Apple App Attest or DeviceCheck on iOS to check the App or device.

Settings, AI-processing permission, terms status, scan timestamps and identifiers, trial and free-use flags, ad-reward timing and rating-prompt counters are kept locally. Advertising data is explained in section 5.

3AI processing

Before the first analysis, the App asks permission to send selected content to Google Cloud Vertex AI, using Google Gemini. The choice is remembered on the device for later scans. You can decline and avoid AI analysis. Selecting a file does not give access to every file in your library.

  • Images may be resized locally. The selected image or PDF is included in the analysis request.
  • For Excel, the first worksheet is converted locally to text, which is sent for analysis.
  • Shared text, optional instructions and date context are included where relevant.
  • Results return to your device for review and editing.

We do not store submitted scan files or extracted event content in our Firestore account database. A local copy may be saved in history after you save events.

Google handles AI requests under its Cloud terms and data-processing arrangements. Its documentation describes possible retention for abuse monitoring and temporary caching; we do not promise zero retention by Google. See Google's AI data-retention documentation.

The App requests the EU location for Vertex AI analysis. Other services may process information elsewhere; see section 12.

4Camera, files and calendar permissions

Camera and photo or file access let you capture or select content. Shared content is received when you choose to share it with the App.

Calendar access lets the App list available calendars and their details, remember your chosen calendar and create approved events, including titles, dates, times, locations, notes and reminders. The operating system may grant broader access than the App uses.

The App does not read the contents of existing appointments or upload your existing calendar. New events may sync through your selected calendar account, such as iCloud or Google, under that provider's settings and policies.

Revoke permissions in device settings. The associated feature may then be unavailable.

5Advertising and tracking choices

The App uses Google AdMob for banner and rewarded advertisements. The current App requests non-personalised advertisements. These ads can still involve personal information and device storage.

Google's Mobile Ads SDK may process IP addresses, approximate location inferred from an IP address, advertising and other device identifiers, ad views and interactions, and diagnostic or performance information for ad delivery, measurement and fraud prevention. We do not provide selected scan files or extracted events to AdMob as part of this integration.

On iOS, the App requests App Tracking Transparency permission, which you can change in iOS settings. Android provides advertising-identifier controls. These choices do not stop all processing, such as network connections or security checks.

See Google's Android disclosure, iOS disclosure and Privacy Policy.

6Local history and settings

After a successful calendar save, the App creates a history entry on your device. It may contain a copy of the source file, its name and type, a short shared-text preview, a timestamp and saved event details.

The history archive is not synchronised to our servers. Content selected for analysis is nevertheless sent to Google Cloud as described in section 3. You can delete individual entries or clear all history in the App.

Device backups may include local app data. Deleting a history entry does not delete the original file in your library, a saved calendar event or a separate backup.

7Who receives information

  • Google Firebase and Google Cloud: authentication, credit records, purchase webhooks, security and AI analysis. Read Firebase's privacy information and the Google Cloud Privacy Notice.
  • Google AdMob: advertising and measurement, as described in section 5.
  • RevenueCat: user identifiers and purchase records to verify purchases and manage credits. Read its Privacy Policy.
  • Google and Apple: sign-in, distribution, payments and device integrity checks. Read the Google Privacy Policy and Apple Privacy Policy.
  • Your calendar provider: saved events may sync according to that account's settings.

We do not sell your scan content or account information. Advertising-related disclosures still apply. Information may also be disclosed where required by law or necessary to address fraud, protect rights or respond to a lawful request.

8Retention

  • Accounts and credits: kept while the account is used, unless deletion is requested. A guest account may remain after uninstalling; uninstalling does not request server-side deletion.
  • History: entries older than 365 days are removed when cleanup runs, including at startup. The maximum is 500 entries, so older entries may be removed earlier. Expired files may remain until the next cleanup.
  • Temporary files and settings: processing or picker copies may remain in app storage or cache until removed by the App or operating system. Settings and usage flags remain until cleared or local app data is removed, subject to backup and restore.
  • Purchase verification and fraud prevention: separate verification records, records of any promotional credits, and relevant logs may remain after account deletion. Verification records have no automatic expiry in the current service. Contact us to request review and deletion of remaining personal information, subject to applicable retention requirements.
  • Providers: Google, RevenueCat and Apple apply their own retention rules for security, payments, backups and legal obligations. AI-request retention is described in section 3.

9Deleting your account and other data

Signed-in users can open Profile & Settings → Delete Account. The App requests deletion of the Firebase authentication account and Firestore user record. You may need to sign in again to complete deletion.

This does not clear local history or settings, remove calendar events or library source files, remove separate verification records, or automatically erase a RevenueCat customer record. Delete saved scans in History and calendar events in your calendar app.

For guest accounts, remaining information or a failed deletion, email dimitristsoukalos@gmail.com. Include the App name and enough information to identify the account or purchase. Do not send passwords or full card details.

Requests may require verification. Information may be retained where law requires or permits it, including for a payment dispute. Continued use after deletion starts a new guest session.

10Purposes and legal bases

Where the GDPR applies, processing necessary to provide the requested service, manage accounts and credits, verify purchases and answer service-related requests is based on performance of a contract.

We rely on legitimate interests for proportionate security, fraud prevention and disputes, and on legal obligations for required records or disclosures. Optional processing that requires consent, including advertising-related storage or tracking, must rely on consent. Device permissions and acceptance of these terms do not replace separate consent required by law.

Declining AI processing prevents analysis. Revoking a permission affects the associated feature.

11Your rights

Depending on applicable law, you may request access, correction, deletion, restriction or portability, and object to processing. Where processing relies on consent, you may withdraw it without affecting earlier lawful processing. Contact us using the details below.

We respond to GDPR requests within one month, subject to permitted extensions and identity checks. You may complain to your local supervisory authority or the Hellenic Data Protection Authority. The AI proposes events for your review; it does not make decisions with legal or similarly significant effects about you.

12International processing and security

The EU location requested for Vertex AI does not mean all account, advertising, purchase or operational data remains in the European Economic Area. Providers may process data in the United States or other countries.

Transfers subject to GDPR require appropriate safeguards, such as an applicable adequacy decision or contractual protections. Contact us for information about the safeguards relevant to your data, and consult the provider notices in section 7.

The App uses encrypted service connections, authentication, Firestore access rules and app-integrity checks. No system guarantees absolute security. Local files depend on your device's security and backup settings.

13Children

The App is not directed at children under 13. Higher requirements for independent consent apply where local law provides them. We do not knowingly seek information from children who cannot lawfully use the service. Contact us if you believe a child's information should be removed.

14This page and policy updates

This page itself uses no analytics, advertising scripts, cookies or browser storage. Its JavaScript supports printing and navigation only. The server delivering the page may process ordinary request information, such as an IP address, under its hosting arrangements.

We may update this policy as the App or services change. The current version appears here with its last-updated date. We will provide additional notice or request consent where required.

Contact

For support, privacy questions or a data request, contact the developer of PhotoToCalendar.

Email: dimitristsoukalos@gmail.com
App: PhotoToCalendar
App identifier: com.mathcoder.phototocalendar

You can also request account deletion by email if you no longer have access to the App.