Privacy Policy

Introduction

Enginr ("we," "our," or "us") is committed to protecting your privacy. This Privacy Policy explains how we collect, use, disclose, and safeguard your information when you use our website and mobile application (collectively, the "Service"). By using the Service, you agree to the collection and use of information in accordance with this policy. We do not sell your personal information or share it for purposes beyond what is disclosed here. If any terms are undefined in this Policy, they have the same meaning as in our Terms of Service.

Information We Collect

Information You Provide

When you create an account or otherwise provide information, we collect:

• Account Information: For account setup we require an email address, a display name, and a username. You may also choose to add a profile photo.
• Authentication Data: If you sign up with an email, you provide a password (which is stored in encrypted form). If you choose third-party login via Google or Apple, we receive authentication tokens instead of a password, as well as basic profile information from those providers (for example, your email address and name). We do not store any passwords ourselves; third-party identity providers like Firebase Authentication handle credential storage.
• Profile Information: You may add details to your profile such as a bio, links to external profiles (e.g. GitHub, LinkedIn), personal website URLs, or information about your projects and skills. Providing this information is optional but any information you do add will be part of your profile.
• User Content: All content you create on Enginr – including posts, code snippets, comments, likes, and other contributions – is collected and stored. This also includes any attachments or media that you upload. Note that User Content you post may be visible to others on the Service (see Publicly Visible Information below).
• Communications: If you send messages through the Service (for example, direct messages to other users) or contact us for support, we collect the contents of those communications. This includes any support requests or feedback you submit.
• Payment and Subscription Information: If you choose to subscribe to our "Pro" tier or make other purchases, we (or our payment partners) collect information about the transaction. For example, we will record that you purchased a subscription and its status (e.g. active, expiration date). Note: Payment processing is handled by third parties (such as Apple App Store, Google Play, or our payment processor). We do not collect or store your credit card number or other sensitive payment details on our own servers.

Information Collected Automatically

When you use our Service, certain data is collected automatically:

• Device and Technical Information: We receive data about the device and app you use to access the Service. This includes your device type (e.g. phone model or computer browser), operating system and version, unique device identifiers, browser type, and app version. We also record certain device settings (like language and region) and hardware stats (such as CPU and memory).
• Usage Data: We collect information about how you interact with our app and website. This includes the features or screens you use, the content you view or engage with, the links or buttons you click, and the time spent on different parts of the Service. For example, we may log that you viewed a particular user's post or visited a project link. This usage data helps us analyze engagement and improve the user experience.
• Log Data: Our servers automatically record logs of certain events whenever you use the Service. These logs may include your Internet Protocol (IP) address, the times and dates of access, pages viewed, and app actions (such as crashes or error reports). For instance, if the app crashes, we capture a crash report containing the state of the app at the time of the crash. Crash reports may include device state information, unique device identifiers, hardware and OS details, and the approximate location of your device at the time of the crash (e.g. to help identify regional issues). We also log events like authentication attempts or important account actions for security auditing.
• Cookies and Tracking Technologies: On our website, we use cookies and similar technologies to remember your preferences and track your use of the Service. For example, cookies may keep you logged in by storing your session token, or help us understand how users navigate pages. Third-party analytics and service providers (described below) may also set cookies or use tracking pixels to collect information on our behalf. You can control or delete cookies through your browser settings; however, note that some parts of the Service might not function properly if cookies are disabled.

How We Use Your Information

We use the collected information for the following purposes:

• Provide and Improve the Service: We use your information to operate Enginr's core features. For example, we use account and authentication data to create and secure your account, and profile information to populate your profile. User Content and communications are used to display the content you create and facilitate interaction with other users. We also analyze usage and crash data to understand usage trends and improve the Service's functionality and stability.
• Enable Social Features: The information you provide (like your display name, profile, and posts) allows you to engage with the build-in-public community. We use it to enable features such as following other users, commenting on posts, and sharing project updates.
• Communication: We may use your contact information to send you service-related announcements and account notifications. For example, we might send email or in-app notifications for important updates, such as changes to policies or alerts about account activity. We will also respond to you regarding any support inquiries you send us. (We will not send you marketing emails unrelated to the Service without your consent.)
• Subscriptions and Transactions: For users who purchase a Pro subscription, we use your information to manage your subscription benefits and status. For instance, we maintain records of your subscription tier and verify your eligibility for Pro features. Transaction logs are used for accounting and to resolve any billing issues.
• Monitoring and Safety: We continuously monitor activities on the Service to detect and prevent fraudulent, abusive, or illegal behavior. Information (including user posts and messages) may be reviewed by our team or automated systems to enforce our Terms of Service and Community Guidelines. This is to ensure the security of user accounts and the integrity of the platform. If we identify content or behavior violating our rules or the law, we may use relevant data to address the issue (e.g. by issuing warnings, removing content, or suspending accounts).
• Debugging and Technical Maintenance: Automatically collected log and crash data are used to troubleshoot errors, investigate crashes, and fix technical problems. This helps us keep the Service reliable and secure. For example, crash reports (via Firebase Crashlytics) are analyzed to determine what caused an app failure so we can patch it.
• Analytics: We may aggregate usage data to generate insights into how our users as a whole use the Service. This helps us understand which features are popular or where users encounter difficulty, guiding future development. For this purpose we might use analytics tools (like Firebase Analytics) to track metrics such as daily active users, retention, or feature usage frequency.

We will use your personal information only for the purposes above or for compatible purposes that we will explain to you at the time, and we will ask for your consent if we ever need to use it for any other purpose.

Analytics & Telemetry

To improve our Service and ensure it operates reliably, we use the following analytics and monitoring tools. This section provides transparency about what data these tools collect and how you can control them:

Firebase Analytics

We use Firebase Analytics (operated by Google) to understand how users interact with our Service. This includes tracking which features are used, how often the app is opened, screen views, and general engagement metrics. Firebase Analytics collects:

• Device information (type, operating system, app version)
• Usage events (screens visited, buttons clicked, features used)
• Session information (how long you use the app)
• Approximate location (country/region level, derived from IP address)

This data is used in aggregate form to identify popular features, detect usability issues, and guide product improvements. Firebase Analytics does not collect the content of your posts, messages, or personal details like your email address.

Opt-out: You can disable analytics collection in Settings > Privacy & Safety by toggling off "Allow analytics collection." When disabled, no usage events will be sent to Firebase Analytics.

Learn more: Firebase Privacy Policy

Firebase Crashlytics

We use Firebase Crashlytics (operated by Google) to detect, track, and fix app crashes and stability issues. When the app encounters an error or crashes, Crashlytics automatically captures:

• Device and app state at the time of the crash (memory usage, battery, screen orientation)
• Technical details about the error (stack traces, error messages)
• Device information (model, OS version, app version)
• A unique installation identifier (not linked to your account)

Crashlytics data is used solely for debugging and improving app stability. It does not include the content of your posts, messages, or passwords. Crash reporting cannot be disabled as it is essential for maintaining app stability and security for all users.

Learn more: Firebase Privacy Policy

Sentry Error Monitoring

We use Sentry (Sentry.io) as an additional error monitoring service for both our mobile app and website. When errors occur that don't cause a full crash, Sentry captures:

• Error details (error type, message, stack trace)
• Browser/app context (version, operating system)
• Network information (IP address, which is anonymized after processing)
• Breadcrumbs (recent user actions leading to the error)

We have configured Sentry to scrub sensitive data before transmission, including email addresses, passwords, and authentication tokens. This means your personal information is not sent to Sentry. Error monitoring cannot be disabled as it is critical for identifying and fixing bugs that affect all users.

Learn more: Sentry Privacy Policy

Your Telemetry Choices

We respect your privacy preferences and provide the following controls:

• Analytics Opt-Out: You can disable Firebase Analytics collection in your Privacy & Safety settings. This stops usage tracking while keeping essential error monitoring active.
• Global Privacy Control (GPC): On web browsers, we honor the GPC signal. If your browser sends a GPC signal, we automatically apply "Do Not Sell or Share" preferences to your account.
• Essential Monitoring: Crash reporting (Crashlytics) and error monitoring (Sentry) remain active for all users to ensure app stability and security. These services do not collect personal content or account information.

How We Share Your Information

We do not sell your personal information to third parties. We only share or disclose your information in the following circumstances:

Publicly Visible Information

Certain profile and activity information is public by default on Enginr, meaning it can be seen by other users of the Service (and potentially by anyone on the internet if our content is publicly accessible):

• Profile Data: Your display name, username, profile photo, bio, and any links or external profiles you list on your profile are visible to others.
• User Content: Content you post (such as your posts, code snippets, comments, or project updates) is visible to others on the platform. This includes the text of posts and comments, as well as any likes or similar interactions associated with your user account.
• Social Graph: Information about who you follow and who follows you (your follower and following lists) is visible to other users. Likewise, if the Service displays counts of likes or comments on your content, those interactions are attributable to your public profile.
• Community Interactions: If you participate in any public discussions, Q&A, or other interactive features, your contributions will be public along with your username.

Please be mindful that any information you make public on Enginr (or that is posted publicly by others about you) can be viewed and used by others. Do not include information in your profile or content that you wish to remain private.

Service Providers

We share certain information with third-party service providers and partners who assist us in operating and providing the Service. Each of these providers is contractually obligated to protect your data and use it only for the services they are providing. The categories of service providers we use include:

• Hosting and Infrastructure: We use Google Firebase (a service by Google) for our backend infrastructure. This includes Firebase Authentication (for user login and identity management), Firestore/Database and Cloud Storage (for data storage, such as user profiles, posts, and media), and Firebase Cloud Functions (for server-side logic). As a result, your personal data (account info, profile, content, etc.) is stored on Google's servers as part of Firebase. Google may process this data on our behalf in accordance with Google's privacy and security terms.
• Analytics: We use Firebase Analytics (Google) to collect anonymized statistical data about how users use our app, and Crashlytics (part of Firebase) for crash reporting. These tools automatically gather device identifiers, app usage events, and crash logs in order to help us understand performance issues and usage patterns. For example, Crashlytics will log information about your device and app state at the time of a crash (such as OS version, device model, and a stack trace of the error) and send it to our Firebase console for review. This information is used strictly for debugging and improving stability.
• Error Monitoring: In addition to Crashlytics, we use Sentry (Sentry.io) as an error and exception monitoring service. When errors occur in the app or website, Sentry captures debugging information (like the error message, the code location, and device context) to help us diagnose issues. This may include technical identifiers like your IP address or device ID, but it does not include your account passwords or the content of your communications. Sentry is obligated to keep any data it processes on our behalf confidential and secure.
• Payments and Subscriptions: For managing our in-app subscriptions (Pro accounts), we use a service called RevenueCat. RevenueCat helps coordinate subscription status across App Store and Google Play. When you subscribe or unsubscribe, RevenueCat receives identifiers related to your purchase (like an anonymous user ID and receipt data) to inform us of your subscription state. RevenueCat does not receive your full payment details; those are handled by Apple or Google during the transaction. We share only the information necessary for subscription management, and RevenueCat is similarly bound to protect it.
• Other Vendors: We may use additional third-party tools or services to improve the Service – for example, Firebase Cloud Messaging to send push notifications, or Firebase Remote Config to test feature variations. These services may incidentally process some user data (like device tokens for notifications or non-personal configuration parameters). We ensure that all such vendors access only the data needed and are covered by appropriate data protection agreements.

Each of these providers only receives the information required for their function. They are not permitted to use your information for any unrelated purposes, and must adhere to confidentiality and security obligations. For more details on the privacy practices of these third-party services, you may refer to their privacy policies (e.g., Google/Firebase's Privacy Policy, Sentry's Privacy Policy, RevenueCat's Privacy Policy, etc.).

Legal Compliance and Protection

We may disclose your information if we determine in good faith that such action is necessary to comply with applicable laws, regulations, legal processes, or governmental requests. This includes:

• Responding to subpoenas, court orders, or similar legal process.
• Disclosing information to law enforcement or regulatory authorities if required by law, or when we believe disclosure is necessary to protect our rights, investigate fraud, or ensure the safety of our users or the public. For example, if we in good faith detect content that implicates harm to someone, we might preserve and share relevant data with authorities.
• Enforcing our Terms of Service and other agreements, or investigating potential violations thereof. If you engage in actions that violate our policies or are unlawful, we may use and share data necessary to investigate and address the issue.

In any such case, we will only share the information that is reasonably necessary and will attempt to notify you of the demand when allowed (for instance, unless we are legally prohibited from doing so). Protecting the privacy and safety of our users is important to us, but there may be circumstances where we are legally obligated to disclose information. We will always strive to balance legal requirements with the security and privacy of our community.

Business Transfers

If Enginr is involved in a merger, acquisition, bankruptcy, asset sale, or other transaction whereby control of the service is transferred, your information may be among the assets transferred to the buyer or acquiring party. This would be done to ensure continuity of the Service. The new owner would be required to honor the commitments we have made in this Privacy Policy (unless you're notified of changes and consent to them). Similarly, if we ever engage in corporate restructuring or reorganization, user information could be shared among our affiliated entities under the same commitments of confidentiality. We will notify you (for example, via email or a notice on our Service) of any such change in ownership or control of your personal information, as well as any choices you may have regarding your data as a result.

Links to Other Sites

The Service may contain links to third-party websites or services – for example, a link to a project's GitHub repository, a YouTube video, or articles on external sites that users share. Please be aware that if you follow a link to an external site, this Privacy Policy no longer applies. Those third-party sites are governed by their own privacy policies and terms. We do not control and are not responsible for the content, security, or privacy practices of any external websites. We encourage you to review the privacy policy of any site you visit via links on our Service. Enginr disclaims any liability for the privacy practices of such third parties.

Your Rights and Choices

You have certain rights and choices regarding your personal information. We provide the following options to all users:

• Access and Update: You can access and update your account profile information at any time by logging into Enginr and visiting your account settings. Here, you can edit details like your display name, bio, profile photo, and linked accounts. Please keep your information up to date.
• Delete Your Account: You have the right to delete your Enginr account if you no longer wish to use the Service. You can initiate deletion through the Privacy & Safety section of your account settings. Once you confirm, we will deactivate and begin the process of deleting your personal data (as described in Data Retention below). Account deletion is permanent and cannot be undone.
• Data Export: You can request and download a copy of your personal data directly from your account settings. Navigate to Settings > Account > Data & Privacy and select "Export Your Data." Your export will be generated as a JSON file and made available for download within minutes. Download links expire after 72 hours, and exports are limited to once every 24 hours to prevent abuse.
• Communication Preferences: You can control certain communications from us. For example, you can opt in or out of non-essential email notifications or newsletters via your notification settings in the app. (Note: we will still send emails for important account or transaction notices, such as password resets or billing issues, as these are not promotional.)

In addition to the above, users in certain regions (such as the European Union or California) may have additional rights under applicable law. These can include the right to correct inaccurate data, object to or restrict our processing of your data, or not be subject to automated decision-making. We will honor any such rights as required by law. For example, California residents have the right to know what categories of personal information we collect and how we use and share it, to request that we delete their personal information, and to not be discriminated against for exercising privacy rights. Enginr does not sell personal data, as noted above, so the "Do Not Sell" right is not applicable. If you are a California resident and send us a verifiable request regarding your data or rights under the CCPA/CPRA, we will respond as required.

To exercise any of your rights or choices, you can use the self-service tools provided in the app (where available), submit a formal request through our Privacy Request Form, or contact us at support@enginr.dev for assistance. We will need to verify your identity (for example, by confirming control of your account email address) before fulfilling certain requests, especially for data access or deletion, to protect your security. We will respond to requests within the time frame required by law.

Data Security

We implement appropriate technical and organizational measures to protect your personal information. This includes using encryption for data in transit (HTTPS/TLS encryption for all data exchanges with our Service) and encryption at rest for stored data. We restrict access to personal data to authorized personnel with a legitimate need to know. Our databases and servers are protected by firewalls and industry-standard security practices. We also monitor for possible vulnerabilities and attacks.

However, please note that no method of transmission over the internet or method of electronic storage is 100% secure. While we strive to use commercially acceptable means to protect your information, we cannot guarantee absolute security. You should also take care with how you handle and disclose your own personal information and credentials – for example, by choosing a strong password and keeping it confidential. If you have reason to believe that your interaction with us is no longer secure (for instance, if you suspect your account has been compromised), please contact us immediately so we can assist.

Data Retention

We retain your personal information only for as long as necessary to fulfill the purposes outlined in this Privacy Policy, or as required by law. In general, this means:

• For as long as you have an active account on Enginr, we will keep the information you have provided and content you have created.
• If you choose to delete your account, we will initiate deletion of your personal data. Most of your personal data (profile information, posts, etc.) will be removed from our live systems within approximately 30 days of your deletion request. This delay allows us to confirm your intent and handle any ongoing matters (like resolving support issues or processing final subscription billing). During this period your account will be deactivated and not accessible to other users.
• After 30 days, residual copies of your data may remain in our backups or archives for up to an additional period (no longer than 90 days in backup systems, except as noted below). We maintain backups to ensure resilience of the Service, but we will securely erase or overwrite personal data from backups in the normal course of backup rotation.
• Certain types of data may be retained longer if necessary for legal compliance or legitimate business purposes. For example, we may keep logs of security events and communications to comply with law, prevent fraud, resolve disputes, or enforce our agreements. If we are required by law to retain certain data (such as transaction records for tax/accounting, or information related to an investigation), we will retain that specific data as needed. We may also retain anonymous or aggregated information (which no longer identifies any individual) indefinitely for analysis and improvement of our Service.

In summary, once your account is deleted or otherwise becomes inactive, we remove or anonymize personal data according to the timeframes above and our internal data retention policies. If for some reason deletion is not possible (for instance, if your data was stored in an offline backup archive that is impractical to access), we will secure and isolate that data from further use until deletion is feasible.

International Data Transfers

Enginr is based in the United States, and the infrastructure we use (such as Firebase by Google) is also primarily located in the U.S. This means that if you are accessing the Service from outside the United States, your personal information will be transferred to and processed in the United States (and potentially other countries where our service providers have facilities). The data protection and privacy laws of these countries may be different from those in your home country.

For Canadian users: Please see our Canada Privacy Addendum for information specific to your rights under PIPEDA and how we handle cross-border data transfers from Canada.

We are committed to protecting your privacy and will take appropriate safeguards if we transfer your information across international borders. In particular, for users in regions like the European Economic Area (EEA) or United Kingdom, we rely on legal mechanisms such as Standard Contractual Clauses (SCCs) or your consent to legitimize data transfers from your country to the U.S. These mechanisms are intended to ensure that an equivalent level of data protection travels with your data.

By using Enginr, or by providing us with your information, you acknowledge that your information will be transferred to the United States and other jurisdictions as needed for the purposes described in this Privacy Policy. We will handle that information as described here regardless of the laws in the receiving country. If you have questions about international data transfer or require more information about the safeguards in place, please contact us.

Children's Privacy

Enginr is not intended for children under 13 years of age, and we do not knowingly collect personal information from anyone under 13. If you are under 13, you are not permitted to use the Service or provide any personal data (such as name, address, or email). In the event we learn that we have inadvertently collected personal information from a child under 13, we will take prompt steps to delete such information from our records.

If you are a parent or guardian and you believe that your child (under 13) has created an account or otherwise provided personal information to us, please contact us immediately (see Contact Us below). We will work with you to remove the child's information and terminate the account, in compliance with the Children's Online Privacy Protection Act (COPPA) and other applicable laws.

For minors aged 13 to 18, we recommend parental guidance in using the Service. If you are under the age of majority in your jurisdiction (for example, under 18 in most U.S. states), you should use Enginr only with the involvement and consent of a parent or legal guardian. Some regions may impose higher age requirements for full privacy rights (for instance, under 16 in certain jurisdictions). We will comply with applicable laws regarding minors in those regions as well.

Changes to This Privacy Policy

We may update or revise this Privacy Policy from time to time to reflect changes in our practices or for other operational, legal, or regulatory reasons. If we make material changes to how we handle your personal information, we will provide you with clear notice. This may include, for example, posting a prominent notice on our website or in the app, or contacting you via the email address associated with your account. We will also update the "Last Updated" date at the top of this Privacy Policy.

It's important that you review any updated Privacy Policy. By continuing to use the Service after any revisions become effective, you will be deemed to have accepted the updated terms (to the extent permitted by applicable law). If you do not agree to any changes, you should stop using the Service and, if applicable, delete your account. We encourage you to periodically review this Privacy Policy to stay informed about how we are protecting your information.

Contact Us

If you have any questions, concerns, or comments about this Privacy Policy or our privacy practices, please contact us. We are here to help and will respond to your inquiry as soon as reasonably possible. You can reach us at:

• Email: support@enginr.dev
• Website: https://enginr.dev (you may also use any contact forms or support chat provided on our site)

For privacy-specific inquiries or requests (such as data access or deletion requests), please include in your message that your inquiry is about "Privacy" so we can route it to the correct team. If you prefer to contact us by mail, please send correspondence to our business address listed on our website.

Your trust is important to us. We value your feedback and are committed to resolving any concerns you have about your privacy. Thank you for using Enginr and for reviewing our Privacy Policy.