Privacy Policy & Terms and Conditions - OpenThanks

Privacy Policy

Welcome to OpenThanks. OpenThanks is a service operated by OpenThanks Inc, a Delaware C corporation located at 95 Worth St., New York, NY 10013 ("we," "our," or "us"). OpenThanks is a platform for sending and receiving genuine appreciation on the web, through our iOS app, and through our Android app distributed on Google Play. We are committed to protecting your privacy and being transparent about the data we collect and how we use it. This Privacy Policy explains how we collect, use, share, and safeguard your information when you use any of these products, including Google user data accessed through Google Sign-In or the Google Calendar API. It is intended to meet Google Play's User Data and Data safety disclosure requirements, the Google API Services User Data Policy (including Limited Use requirements), and applicable privacy laws.

By using OpenThanks, you agree to the collection and use of information in accordance with this policy. If you do not agree with our policies and practices, please do not use our services. This policy is linked from our homepage, our Google OAuth consent screen, our Google Play store listing, and is accessible in-app (including via Settings → Privacy in iOS and the website loaded in the Android app).

In short: We collect what we need to run OpenThanks — your account, the appreciations you send and receive, and (if you opt in) a device token so we can notify you. Optional calendar suggestions (Apple Calendar and/or Google Calendar) and Apple Intelligence rewriting are processed on your device to suggest someone to thank — we do not upload your calendar events to OpenThanks servers, sell your data, or use Google user data or calendar contents for advertising. You can disconnect Google Calendar, revoke Apple Calendar access, or delete your account as described below.

Information We Collect

Account & Authentication Information

You can create an account using email, phone number, Google, or LinkedIn. Depending on how you sign in, we collect:

Email address: When you sign in with an email magic link or one-time code, Google, or LinkedIn.
Phone number: When you sign in with your phone number, we collect and store it to authenticate you and to match appreciations that were sent to that number. Your phone number is not publicly displayed on your profile.
Basic profile information: Your name, username, and profile picture (including photos you upload, or from Google or LinkedIn if used), and your LinkedIn profile URL where applicable.
Account identifier: A unique identifier used to link and secure your account.

When you use Google or LinkedIn to sign in, we request only the minimum permissions necessary (name, profile picture, and email). We do not access your Google contacts, Drive, Gmail, or post on your behalf as part of sign-in. Separately, if you choose to connect Google Calendar in the iOS app for evening thank-you suggestions, that uses a different OAuth consent with the readonly Calendar scope described in Google User Data & Calendar API.

Information You Provide

Appreciation messages: The appreciation messages you write for others, including whether you mark them public or private.
Media content: Photos you choose to attach to your appreciations or set as your profile picture.
Recipient contact details: The name, email address, phone number, or OpenThanks profile of a person you wish to thank, so we can notify them and help them claim the appreciation.
Profile details: Any optional bio, headline, or favorite nonprofit you add to your profile.
Reactions: Hearts you leave on appreciations.
Donation details: If you make a donation, payment is processed by our payment provider (Stripe). We receive confirmation details such as amount and status, but we never receive or store your full card number.

Automatically Collected Information

Usage data: Pages and screens visited, features used, and basic interaction patterns needed to keep the service reliable.
Device information: Browser or app type, operating system, device model where available, and (if you allow notifications) a device push token so we can deliver alerts you have opted into on iOS and/or Android.
App activity & diagnostics: On mobile apps, basic crash and performance signals needed to keep the app working (for example install/update state and error logs). We do not use this for advertising.
Log data: IP address, access times, and referring URLs on the website and when the Android app loads our web experience, used for security and troubleshooting.

We do not use third-party advertising trackers, and we do not sell or share your information for cross-app or cross-site advertising.

How We Use Your Information

We use the information we collect only to operate and improve OpenThanks, specifically to:

Create and manage your account and authenticate you when you sign in by email or phone.
Send a one-time login verification code (OTP) by text message when you choose to sign in with your phone number.
Enable you to send, receive, accept, decline, edit, and heart appreciation messages.
Notify you — by email, in-app notices, and (if enabled) push or local reminders — about appreciations and related activity.
Match appreciations sent to your email or phone so you can claim them.
Show public appreciations in the community feed and on profile pages; keep private appreciations visible only to the sender and recipient.
Process and confirm donations you choose to make.
Respond to your inquiries and provide customer support.
Monitor usage to maintain, secure, and improve the platform.
Detect, prevent, and address technical issues, fraud, and security threats.
Comply with our legal obligations.

We never use your information for advertising or marketing by third parties, and we do not sell your data.

iOS App, Calendar & On-Device Features

Our iOS app uses the same OpenThanks account and servers as the website for your profile, appreciations, hearts, and in-app notifications. Some iOS features process information on your device so we can help you thank people without sending sensitive context to our servers.

Calendar suggestions stay on your device. You may optionally connect Apple Calendar (on-device EventKit) and/or Google Calendar (Google Calendar API, readonly). OpenThanks reads today's meetings and attendees only to suggest one person you might want to thank. We do not upload your calendar events, meeting notes, or full event history to OpenThanks servers. You can turn the evening nudge off anytime in Settings, disconnect Google Calendar in Settings, or revoke Apple Calendar access in iOS Settings.

What the iOS app may access (with your permission)

Notifications: So we can show alerts you choose — for example a Friday morning gratitude reminder, or a weekday evening thank-you nudge. Some reminders are scheduled locally on your phone; others use a push token stored with your account so we can deliver remote alerts.
Apple Calendar: Optional. Used only for the evening thank-you nudge. We look at today's event titles, times, and attendees (names and emails when available). We skip obvious holiday and birthday calendars and do not read meeting notes or attachments. Processing stays on your iPhone.
Google Calendar: Optional and separate from Google Sign-In. If you connect Google Calendar, the app requests readonly access via Google's OAuth and Calendar API as described in Google User Data & Calendar API.
Photos: Only when you choose a photo for an appreciation or your profile.
Siri & App Shortcuts: Optional phrases like thanking someone or opening compose. Spoken drafts and reminder names stay on device until you choose to send an appreciation.

Evening thank-you nudge (Calendar)

When enabled, on weekdays OpenThanks may schedule a local notification around 8:00 PM suggesting one person from that day's meetings from whichever calendar sources you connected (Apple and/or Google). Selection happens on your device using simple rules (for example preferring smaller or one-on-one meetings and skipping people you recently thanked). If Apple Intelligence is available on your device, it may help choose among candidates or warm up a short draft — still on device. If nothing relevant is found, or it is a weekend, we send no nudge.

When you tap the nudge, the app can open compose with a suggested name and optional draft. If an attendee email matches an OpenThanks member, we may look up that public profile so you can thank them as a linked member — that lookup uses only the email address, not your full calendar.

On-device AI (Apple Intelligence)

Where available, the app can rewrite an appreciation to sound warmer using Apple's on-device models. That text is processed on your device and is not sent to OpenThanks for AI rewriting. If on-device AI is unavailable, optional features simply fall back to your own wording or a simple template.

What we store on our servers vs. on your device

On OpenThanks servers: Your account and profile, appreciations you send or receive, hearts, in-app notification records, media you upload, and (if notifications are allowed) your device push token. We do not store Apple or Google calendar event contents on our servers.
On your device only: Calendar contents used for suggestions (fetched from Apple EventKit and/or Google Calendar API); Google Calendar OAuth access and refresh tokens in the iOS Keychain; local reminder schedules; Apple Intelligence rewrites; temporary share drafts and widget summaries kept in an App Group container on your iPhone; appearance and reminder preference toggles.

Share Extension, widgets & App Group

If you share a contact, photo, text, or calendar invite into OpenThanks, the Share Extension may prepare a draft on your device and hand it to the main app through Apple's App Group storage. Widget summaries (such as how many appreciations you've sent this month) are also stored only on device. Drafts are not uploaded until you choose to send an appreciation.

Your controls in the iOS app

Turn Friday Gratitude Reminder on or off in Settings.
Turn Evening thank-you nudge on or off in Settings (requires at least one connected calendar source when on).
Connect or disconnect Google Calendar, and allow Apple Calendar, in Settings.
Change or revoke Notifications, Apple Calendar, Photos, and Siri access in iOS Settings → OpenThanks.
Edit or delete pending appreciations you authored; accept or decline ones sent to you; choose public or private when composing.
Log out to clear the locally cached profile and widget snapshot on that device. Disconnecting Google Calendar (or uninstalling the app) removes the on-device Google tokens used for Calendar.

Google User Data & Calendar API

This section describes how OpenThanks accesses, uses, stores, and shares Google user data. It applies when you use Google Sign-In and when you optionally connect Google Calendar in the OpenThanks iOS app. Our use of Google user data complies with the Google API Services User Data Policy, including the Limited Use requirements.

Google Sign-In (identity only)

If you choose Sign in with Google, we receive basic account profile information needed to create or sign in to your OpenThanks account — typically your name, email address, and profile picture. We do not receive your Google password. Sign-in does not grant OpenThanks access to your Google Calendar, Gmail, Drive, or contacts.

Google Calendar (optional evening thank-you nudge)

Separately from sign-in, the iOS app may ask you to connect Google Calendar so we can suggest one person to thank from today's meetings. That connection uses Google OAuth with the narrow scope:

https://www.googleapis.com/auth/calendar.readonly — view events on your Google calendars (we request readonly access only).

What Google user data we access: For the local calendar day, event identifiers, titles/summaries, start and end times (or all-day dates), cancellation status, recurrence indicators when present, and attendee display names and email addresses (including which attendee is you). In the current product we read your primary Google Calendar. We do not request write access, and we do not read meeting notes/descriptions for ranking, attachments, or other Google products.

How we use that data: Solely to power the optional weekday evening thank-you nudge and related on-device ranking/drafting described in iOS App, Calendar & On-Device Features — so OpenThanks can suggest one person from your day to appreciate. We do not use Google Calendar data to serve ads, personalize ads, sell data, train generalized AI/ML models, or build credit or employment profiles.

How we store that data: Calendar event contents retrieved for suggestions are processed on your device to choose a candidate and schedule a local notification. We do not upload or store your Google Calendar events on OpenThanks servers or databases. OAuth access and refresh tokens needed to call the Calendar API are stored only in the iOS Keychain on your device. Tokens are not sent to OpenThanks backends.

How we share that data: We do not sell Google user data. We do not share Google Calendar event contents with third parties for advertising or unrelated analytics. Limited service providers that host OpenThanks (for example our database provider) do not receive your Google Calendar events through this feature. If you later choose to send an appreciation to someone suggested from a meeting, only the appreciation content and recipient details you confirm are stored as part of the normal OpenThanks service — not your full calendar.

Retention and deletion: Google Calendar OAuth tokens remain on your device until you disconnect Google Calendar in OpenThanks Settings (which revokes the token with Google when possible and deletes it from the Keychain), revoke OpenThanks access in your Google Account permissions, or delete/uninstall the app. Because calendar events are not stored on our servers, disconnecting or revoking access stops further Calendar API access; there is no server-side calendar archive to delete. OpenThanks account deletion is separate and is described in Account & Data Deletion.

Limited Use:OpenThanks's use of information received from Google APIs will adhere to the Google API Services User Data Policy, including the Limited Use requirements. We use Google Calendar data only to provide or improve user-facing features that are prominent in the requesting app (the evening thank-you suggestion), and we do not transfer Google user data to others unless necessary to provide those features (with your direction), for security/legal compliance, or as part of a merger/acquisition with notice — and never for serving advertisements.

Protecting Google user data

Calendar API calls use HTTPS / TLS.
OAuth tokens are stored in the iOS Keychain with device-local accessibility controls.
We request only the readonly Calendar scope needed for the nudge feature.
You can review and revoke OpenThanks access at any time in your Google Account → Security → Third-party access / connections.

Android App & Google Play

Our Android app is distributed on Google Play (package name com.openthanks.myapp). It is a Trusted Web Activity (TWA): it opens the same OpenThanks website you use in a browser, inside a full-screen Chrome-based container, so you can sign in and use OpenThanks with the same account, servers, and privacy practices described in this policy.

Same product, same policy. Data you create in the Android app (account, appreciations, hearts, profile, donations) is stored and processed the same way as on the website and iOS app. This Privacy Policy applies to the Android app, and the information we disclose here is intended to be consistent with the Data safety section on our Google Play listing.

Data the Android app accesses, collects, uses, and shares

Consistent with Google Play's User Data policy, here is what the Android app handles:

Account & personal info: Name, email, phone (if used for sign-in), username, profile photo, and other profile fields you provide — to create and manage your account and show your profile.
User-generated content: Appreciation messages, attached photos or media you choose to upload, hearts, and related in-app activity — to provide the core OpenThanks service.
Contacts you enter: Email, phone, or username of someone you thank — only when you type or select that information yourself so we can notify or match the recipient. The Android app does not request broad access to your device address book.
Photos / media: Only when you choose to attach a photo or set a profile picture (via the system picker).
App activity: Screens and features you use within OpenThanks, for operating and improving the service.
Device or other IDs: If you allow notifications, a push token or equivalent device identifier used solely to deliver alerts you opted into. We may also process standard technical identifiers needed for security, fraud prevention, and app integrity.
Financial info: If you donate, payment card details are handled by Stripe; we receive confirmation such as amount and status, not your full card number.

Permissions (with your consent)

Internet / network: Required to load OpenThanks and sync your account.
Notifications (POST_NOTIFICATIONS): Optional. Requested only so we can show alerts you choose (for example appreciation activity or reminders). You can deny or revoke this in Android system settings.

We do not request location, microphone, SMS, call log, or full contacts permissions for the Android app. Camera or photo access, when used, is only through the system picker when you choose media.

How data is shared (Android / Google)

In addition to the service providers listed elsewhere in this policy:

Google Play & Google services: When you install or update the app from Google Play, Google processes install, update, and store-related data under Google's terms. The TWA uses Chrome / Android Browser Helper components provided by Google to display our website securely.
Google Sign-In (optional): If you sign in with Google, Google provides us with basic profile information (such as name, email, and profile picture) subject to your Google account settings and Google's privacy policy. We do not receive your Google password.
Our backend providers (including Supabase, email, SMS, and Stripe): receive only what is needed to operate OpenThanks, as described under Information Sharing below.

We do not sell personal information, and we do not share user data with third parties for their advertising or marketing. Data shared with service providers is for app functionality, security, analytics needed to run the service, or legal compliance — not for selling ads.

Security practices (Google Play Data safety)

Data is encrypted in transit using HTTPS / TLS.
Account authentication uses industry-standard providers and one-time codes where applicable.
You can request deletion of your account and associated personal data (see Account & Data Deletion).
We do not use collected data for independent third-party advertising.

Your controls on Android

Revoke notification permission in Android Settings → Apps → OpenThanks.
Clear app storage or uninstall the app to remove locally cached website data on that device.
Manage or delete your OpenThanks account on the web (or while signed in through the app) as described below.

Information Sharing and Disclosure

We do not sell, rent, or trade your personal information. We do not share your information with third parties for their marketing purposes — ever.

What is public on OpenThanks

The following is visible to others on the platform:

Your name, username, and profile picture.
Appreciation messages you send — only after the recipient accepts them, and only if marked public (private appreciations stay between you and the recipient).
Appreciation messages you receive and accept (subject to the same visibility rules).
Your optional profile bio, headline, and favorite nonprofit.
Heart counts and, where shown, who hearted an appreciation.

Your email address and phone number are never displayed publicly.

Limited service providers

We share the minimum data necessary with trusted service providers strictly so they can perform services for us. They are contractually bound to protect your data and may not use it for their own purposes. These include:

Hosting & database (including Supabase): to run the platform and store your account, appreciations, and media securely.
Email delivery: to send appreciation notifications and reminders.
SMS delivery (Twilio): to send one-time login verification codes (OTP) to your phone number.
Payment processing (Stripe): to process donations you choose to make.
Apple: when you use iOS features such as push delivery, Siri, App Groups, or on-device Apple Intelligence — subject to Apple's terms and your device settings. We do not receive your Apple Calendar contents on OpenThanks servers.
Google: when you install the Android app from Google Play, use Google Sign-In, use the Chrome-based Trusted Web Activity container that displays OpenThanks, or (in the iOS app) optionally connect Google Calendar via Google's OAuth and Calendar API — subject to Google's terms and your Google account / device settings. Google Calendar event contents are processed on device as described in Google User Data & Calendar API and are not stored on OpenThanks servers.

We may also disclose information if required by law, to protect our rights or users' safety, or in connection with a merger or acquisition (in which case this policy continues to apply).

No mobile information will be shared with third parties or affiliates for marketing or promotional purposes. Information sharing with subcontractors in support services, such as our SMS provider, is permitted solely so they can deliver the messages you have consented to receive. All other use-case categories exclude text messaging originator opt-in data and consent; this information will not be shared with any third parties.

SMS Messaging Program

Program name: OpenThanks Login Verification

Program description: OpenThanks sends only one-time login verification codes (OTP) by text message when you choose to sign in with your phone number. This is the sole purpose of our SMS program. We do not send appreciation notifications, reminders, marketing, or promotional text messages.

Message frequency: You receive a text message only when you request a login verification code. Message frequency depends on how often you sign in with your phone number. You will not receive recurring or marketing texts.

Message and data rates:Message and data rates may apply. Your mobile carrier's standard messaging and data charges will apply to any messages you send or receive.

Support / HELP: For help, reply HELP to any message, or contact us at founders@openthanks.com.

Opt-out / STOP: You can cancel at any time by replying STOP to any message. After you send STOP, we will send a single confirmation message and then stop sending texts to that number. To resume, reply START.

How you opt in (consent)

Consent to receive SMS is obtained directly on the public OpenThanks sign-in page (https://openthanks.com/auth/login), which is openly accessible without any account or prior login. To opt in, you choose "Continue with Phone," enter your phone number, and tap "Send code" to request a one-time login verification code. A notice that you will receive a one-time verification code (OTP) at the number you provide, the disclosure that message and data rates may apply, and a link to this policy are all shown on that page at the exact point you request the code.

Providing your phone number and requesting a code is your affirmative opt-in for the sole purpose of login verification. We only send the one-time verification code described above. We never add you to any marketing or promotional texting list, and your consent to receive messages is never shared with third parties or affiliates for marketing or promotional purposes.

Sample message

"Your OpenThanks verification code is 123456. It expires in 10 minutes. Reply STOP to opt out, HELP for help."

How you opt out

You may opt out of text messages at any time by replying STOP to any message from us. You can also email founders@openthanks.com to have your number removed from SMS notifications. Opting out of SMS will not delete your account, but you may no longer be able to sign in using a one-time code sent by text.

Donations & Campaigns

OpenThanks lets you make optional donations to nonprofits in honor of someone you appreciate. Participation is entirely voluntary.

All donations and any fundraising or money-related campaign are optional, and any campaign may be paused or ended at any time, for any reason, at our discretion or the organizer's.
Payments are processed securely by Stripe. We do not receive or store your full payment card details.
We use your donation information only to process the donation, send you a receipt, and comply with legal and accounting requirements.
Donation amounts and the nonprofit honored may be displayed in connection with the appreciation, but your payment details remain private.

Data Security

We implement appropriate technical and organizational measures to protect your information, including:

Encryption of data in transit using SSL/TLS (including Google API requests).
Secure authentication through trusted providers and one-time codes.
Access controls limiting who can access personal data.
Secure data storage with industry-standard providers.
On-device storage of Google Calendar OAuth tokens in the iOS Keychain; calendar event contents for suggestions are not uploaded to OpenThanks servers.

No method of transmission or storage is 100% secure, and we cannot guarantee absolute security.

Data Retention

We retain your information for as long as your account is active or as needed to provide our services. You may request deletion of your account at any time. After account deletion:

Your profile information, including your email and phone number, will be permanently deleted.
Appreciation messages you sent will remain visible but attributed to "Deleted User."
Appreciation messages you received will be deleted.
Google Calendar OAuth tokens and on-device calendar caches are removed when you disconnect Google Calendar or delete/uninstall the iOS app; they are not retained on OpenThanks servers.
We may retain limited information where required by law or for legitimate business purposes (for example fraud prevention or accounting records for donations).

Account & Data Deletion

If you create an OpenThanks account, you can delete it and request deletion of associated personal data. This meets Google Play's requirement that apps offering account creation also offer account deletion.

In the product: Sign in on the website or in the Android / iOS app, open Edit Profile (https://openthanks.com/profile/edit), and use the account deletion option.
By email: Send a deletion request from the email associated with your account to founders@openthanks.com. We will verify ownership and process the request.

Deleting the Android or iOS app from your device does notby itself delete your OpenThanks account on our servers. Use one of the methods above to delete your account and personal data. After deletion, residual content handling follows the Data Retention section (for example public messages you authored may remain attributed to "Deleted User").

Your Rights and Choices

You have the following rights regarding your personal information:

Access: Request a copy of the information we hold about you.
Correction: Request correction of inaccurate or incomplete information, including through Edit Profile in the app or on the web.
Deletion: Delete your account and personal data as described in Account & Data Deletion.
Portability: Request a machine-readable copy of your data.
Opt out of SMS: Reply STOP to any text, or email founders@openthanks.com.
App reminder & calendar controls: Disable Friday reminders or the evening thank-you nudge in OpenThanks Settings; connect or disconnect Google Calendar there; revoke Apple Calendar, Notifications, Photos, or Siri access in iOS system Settings; and revoke Google access in your Google Account third-party connections.
Android notification controls: Deny or revoke notification permission in Android system Settings.
Withdrawal of consent: Withdraw consent where processing is based on consent.

To exercise these rights, contact us at founders@openthanks.com.

Cookies and Tracking Technologies

On the website, we use cookies and similar technologies to maintain your session and authentication state, remember preferences, and help keep the service secure. The iOS app stores preference toggles and a short-lived local profile cache on your device (and widget/share drafts in an App Group) — not for advertising. You can control website cookies through your browser settings, though disabling them may affect functionality. We do not use third-party advertising cookies or sell tracking data.

Children's Privacy

OpenThanks is not directed to children, and is not intended for children under 16. We do not knowingly collect personal information from children under 16. The Android app on Google Play is not designed for children and is not part of Google Play's Designed for Families program. If you believe a child has provided us with personal information, contact us at founders@openthanks.com and we will take steps to delete it.

Child Safety Standards (CSAE)

These are OpenThanks's published standards against child sexual abuse and exploitation (CSAE). They apply to the OpenThanks service operated by OpenThanks Inc — including our website (openthanks.com), our iOS app, and our Android app on Google Play named OpenThanks. OpenThanks has a zero-tolerance policy for CSAE.

Prohibited: Any content, conduct, or activity that involves or promotes child sexual abuse and exploitation (CSAE), including child sexual abuse material (CSAM), is strictly forbidden on OpenThanks.

What we prohibit

Creating, uploading, sharing, soliciting, linking to, or otherwise distributing CSAM or any content that sexually exploits or endangers minors.
Grooming, sexualizing, or otherwise exploiting minors, or attempting to contact minors for sexual purposes.
Using OpenThanks to facilitate, advertise, or normalize CSAE in any form.

How we address CSAM

When OpenThanks obtains actual knowledge of CSAM or other CSAE on our platform, we take appropriate action in accordance with these standards and applicable law. That may include removing the content, suspending or terminating accounts, preserving records as required, and reporting confirmed CSAM to the National Center for Missing & Exploited Children (NCMEC) or the relevant authority in the applicable jurisdiction.

Reporting & user feedback

If you encounter content or behavior on OpenThanks that may involve CSAE or CSAM, report it immediately:

Email: founders@openthanks.com (child safety / CSAE reports)
In product: Use available feedback or support options in the OpenThanks app or website, or contact us at the email above.

If you believe a child is in immediate danger, contact local law enforcement first.

Compliance with child safety laws

OpenThanks complies with applicable child safety laws and regulations, including processes to report confirmed CSAM to NCMEC or the relevant regional authority where required.

Child safety point of contact

For notifications from Google Play or others regarding CSAE content on OpenThanks, our designated child safety point of contact is:

OpenThanks Inc — Child Safety Contact

95 Worth St., New York, NY 10013

Email: founders@openthanks.com

This contact is authorized to discuss enforcement and review procedures and to take action when required.

International Data Transfers

Your information may be processed in countries other than your own, which may have different data protection laws. We take appropriate safeguards to ensure your information remains protected in accordance with this policy.

Changes to This Policy

We may update this Privacy Policy and Terms and Conditions from time to time. We will post the updated version on this page and revise the "Last updated" date. Changes are effective when posted.

Terms and Conditions

These Terms and Conditions ("Terms") govern your use of OpenThanks — including the website, iOS app, and Android app on Google Play — a service operated by OpenThanks Inc, a Delaware C corporation located at 95 Worth St., New York, NY 10013. By accessing or using the platform, you agree to be bound by these Terms and by the Privacy Policy above.

1. Acceptance of Terms

By accessing and using OpenThanks, you accept and agree to be bound by these Terms. If you do not agree, please do not use the platform.

2. Eligibility & Accounts

You must be at least 16 years old to use OpenThanks. You are responsible for maintaining the security of your account and for all activity that occurs under it. You agree to provide accurate information, including a valid email address or phone number used for sign-in and notifications.

3. Acceptable Use

OpenThanks exists to spread genuine, positive appreciation. You agree not to:

Post content that is harassing, hateful, defamatory, deceptive, or unlawful.
Create, upload, share, solicit, or distribute child sexual abuse material (CSAM), or engage in any child sexual abuse and exploitation (CSAE). See our Child Safety Standards (CSAE).
Send unsolicited promotional or spam messages to others.
Impersonate any person or misrepresent your affiliation.
Attempt to reverse engineer, disrupt, or gain unauthorized access to the platform.
Use the platform for any commercial purpose not expressly permitted by us.

4. User Content

You retain ownership of the appreciation messages and media you create. By posting content, you grant OpenThanks a non-exclusive license to host and display that content on the platform as needed to provide the service (for example, showing an accepted public appreciation). Private appreciations are shown only to the sender and recipient. You are responsible for the content you submit and confirm you have the rights to share it.

5. SMS & Login Verification

If you choose to sign in with your phone number, you consent to receive a one-time login verification code (OTP) by text message, as described in the SMS Messaging Program section. This is the only type of text message we send. Message and data rates may apply. Reply HELP for help or STOP to cancel at any time.

6. iOS Permissions & On-Device Features

Optional iOS permissions (Notifications, Apple Calendar, Photos, Siri) and optional Google Calendar connection are used only for the features described in iOS App, Calendar & On-Device Features and Google User Data & Calendar API. Calendar access is optional; declining Apple Calendar or Google Calendar does not prevent you from using the rest of OpenThanks. You may change these permissions at any time in OpenThanks Settings, iOS Settings, or your Google Account.

7. Android App & Google Play

The Android app distributes OpenThanks via Google Play and displays our web service in a Trusted Web Activity. Optional notification permission is used only as described in Android App & Google Play. Uninstalling the app does not delete your account; use Account & Data Deletionto remove your account and personal data. Google Play's terms also apply to installation and billing related to the store itself.

8. Donations & Campaigns

Donations are voluntary and processed by Stripe. Any fundraising or money-related campaign may be modified, paused, or ended at any time. Unless required by law, donations are generally non-refundable; for donation questions, contact founders@openthanks.com.

9. Disclaimer

The platform is provided on an "as is" and "as available" basis. OpenThanks makes no warranties, expressed or implied, and disclaims all implied warranties including merchantability, fitness for a particular purpose, and non-infringement.

10. Limitation of Liability

In no event shall OpenThanks or its suppliers be liable for any damages (including, without limitation, loss of data or profit, or business interruption) arising out of the use or inability to use the platform.

11. Termination

You may stop using OpenThanks and delete your account at any time as described in Account & Data Deletion. We may suspend or terminate access if you violate these Terms or to protect the platform and its users.

12. Modifications

We may revise these Terms at any time by posting an updated version on this page. By continuing to use the platform, you agree to be bound by the then-current Terms.

13. Governing Law

OpenThanks is operated by OpenThanks Inc, a Delaware C corporation with its principal address at 95 Worth St., New York, NY 10013. These Terms are governed by and construed in accordance with the laws of the State of Delaware and the United States, without regard to conflict-of-law principles, and you irrevocably submit to the exclusive jurisdiction of the courts located there.

Contact Us

If you have any questions about this Privacy Policy or our Terms and Conditions, please contact us:

OpenThanks (operated by OpenThanks Inc)

OpenThanks Inc, a Delaware C corporation

95 Worth St., New York, NY 10013

Privacy: founders@openthanks.com

Support & SMS help: founders@openthanks.com

Child safety / CSAE: founders@openthanks.com

Published CSAE standards: https://openthanks.com/privacy#child-safety-csae