Privacy Policy
Last updated:
Who we are
SmartSoft provides personal software development mentoring with Hasan Yıldız. This policy describes the Android app and its backend. Hasan Yıldız is the contact responsible for handling questions about your data; the contact link is below.
Data we use and why
Google sign-in provides your Google account identifier and email address so we can create and verify your student account. We assign an internal account identifier and use session credentials to keep you signed in. We do not receive or store your Google password.
We store your onboarding answers, mentoring goals, experience, topics, learning preferences, teaching language, preferred days and times, timezone and app language to personalize mentoring and show suitable booking times.
Booking records include the lesson time and duration, attendance email, reservation status, reminders and Google Meet link. Purchase records include account and store transaction identifiers, product, purchase time and lesson entitlements. They support fulfillment, booking and prevention of duplicate credits. Google Play handles payment details; our backend does not receive card numbers.
Google Calendar and Meet
We use the mentor’s Google Calendar to check availability and create confirmed lesson invitations and Google Meet meetings. Your email and lesson details are shared with Google and the mentor for these invitations. Student sign-in does not grant access to your personal Google Calendar.
You join through Google Meet. Meeting audio, video, shared screens and chat are handled by Google Meet under its own policies. Our app backend does not store meeting recordings or conversation content.
Notifications and analytics
With Android notification permission, Firebase Cloud Messaging uses a push token and installation identifier to deliver lesson reminders approximately 30 minutes before a lesson. You can turn a lesson’s reminder off from My lessons or disable the app’s notifications in Android settings. Disabling reminders prevents delivery; account deletion removes the server’s device registration.
Firebase Analytics measures onboarding, screen visits, paywall views and checkout steps. It receives an internal account identifier, app-instance identifier, events and technical app/device information. RevenueCat receives the account and app-instance identifiers and verified purchase information to process entitlements and, when its integration is enabled, forward purchase events to Analytics. We do not add names, email addresses, onboarding answers or meeting links to custom analytics events. The app does not display ads; advertising-ID collection and ad-personalization signals are disabled.
Sharing and security
Data is shared only as needed with the mentor, our hosting infrastructure and the providers described here: Google Sign-In, Calendar, Meet and Play; Firebase; RevenueCat; and WhatsApp when you choose to contact support. These providers may process data in other countries according to their policies. We do not sell your personal data.
Production connections use HTTPS. Credentials are kept in protected server storage or encrypted Android storage; server session records use token hashes. Access controls restrict student records to their account. The public privacy and terms pages do not set cookies or embed analytics, forms, scripts or third-party assets. Opening a provider or WhatsApp link subjects that visit to the provider’s practices.
Retention and account deletion
Your profile, preferences and account data remain while your account is active. You can request deletion in Settings → Delete account and confirm it. Signing out does not delete your account. Pending booking work or lessons that have not ended must finish before in-app deletion can complete; contact Hasan Yıldız below if you need assistance or cannot access the app.
Successful deletion removes your Google account identifier and email, onboarding answers, server push registration, session and refresh credentials, and stored booking attendance email. Pseudonymous purchase, lesson and append-only credit records remain to preserve transaction ownership, prevent fraud and duplicate credits, and resolve service disputes; they no longer contain your Google sign-in identity or attendance email. These retained records have no automatic deletion deadline. A hash-only acknowledgement, containing no account identifier, is valid for up to 24 hours solely to retry a lost deletion response.
Deleting the app account does not delete your Google account, erase the independent records of Google Play, Google Calendar/Meet, RevenueCat, Analytics or WhatsApp, or automatically refund a payment. Requests concerning retained records, provider-held data, access or correction can be made through the contact below. We assess those requests and coordinate with the relevant provider; provider retention and available privacy controls follow their own policies.
You can also request account and personal-data deletion without the app through the Delete account page linked below. Its form stores your Google sign-in email until the request is resolved, then removes the request record. Hasan Yıldız verifies ownership by contacting that email before deletion; submitting a request alone cannot delete an account. Pending bookings and future lessons must be resolved first.
Changes and your choices
You can update app language and lesson-time preferences, control notifications and request access, correction or deletion through our contact. Privacy rights that apply to you are not limited by this policy. Material changes are reflected in the updated date and communicated where required; new data uses requiring permission will not be authorized merely by this page.
Contact and privacy requests
Hasan Yıldız · WhatsApp @mentorsoftware