Legal
Privacy Policy
Effective April 4, 2026 · Last updated September 30, 2026
1. Who we are
DigiBioFi ("we", "our", or "us") operates the professional profile platform at digibiofi.com. Your privacy matters to us. This policy explains what personal data we collect, why we collect it, how we protect it, and the rights available to you.
2. Data we collect
Account data: When you register, we store your email address, username, and hashed password. We never store plain-text passwords.
Profile data: Any content you choose to add to your public profile — full name, headline, bio, location, work experience, education, skills, projects, links, and profile image — is stored to render your profile page.
Uploaded files: Profile images, project thumbnails, and certificates you publish are served with the public profile. An uploaded resume PDF is stored privately and can be downloaded through the access-checked resume route when its profile is public. Resume PDFs, DOCX files, and text files submitted for AI analysis are scanned first. Non-PDF analysis sources are kept outside public file routes and removed after the background job finishes; an uploaded PDF may remain attached to your account until you replace or delete it.
Resume analysis: Resume analysis uses DigiBioFi's privately hosted model. Resume content is not sent to Gemini or another cloud language model. The extracted result and job status are stored with your account so you can leave and return to review the suggestions; the profile-prefill cache expires after 30 minutes. Completed job results have no separate automatic expiry and follow the account retention and deletion process described below.
Analytics and network security: For abuse prevention, rate limits, and trusted network rules, we process the request IP in memory. Security session and audit records retain only a coarse network prefix (IPv4 /24 or IPv6 /64), together with limited device/browser metadata. For public-profile analytics, we store a pseudonymous visitor hash rather than the raw IP. When approximate geolocation is enabled, we send only the coarse network address to IPWho for a lookup; country, region, city, and approximate coordinates follow the analytics retention schedule below. Elite geographic reports show only completed-day groups of at least five distinct pseudonymous visitor tokens, with counts rounded down to multiples of five; smaller groups have no location or count displayed. The keyed geolocation cache expires within 24 hours.
Contact messages: Messages submitted through the contact form are stored in our database and reviewed by our team.
Billing data: If you subscribe to a paid plan, payment processing is handled entirely by Stripe. DigiBioFi stores only Stripe customer and subscription identifiers — never raw card numbers or full payment details.
Session data: We use secure HTTP-only session cookies for authentication and flash messages. These are not used for advertising tracking.
Contact invitations: If you choose to invite people to DigiBioFi, we process only the contacts you explicitly provide or select — by uploading a CSV/vCard file, entering a contact manually, or (Android app only) picking contacts from your device's contact list. On Android 17 and newer, this uses the system's privacy-preserving Contact Picker, which never gives DigiBioFi broad access to your address book — only the contact(s) you select are shared with the app. On older Android versions, DigiBioFi may request permission to read contacts specifically when you tap "Import from Device," because that Android version's picker cannot otherwise hand over the selected contact's email and phone number together; DigiBioFi still only processes the one contact you select through that screen, never scans or syncs your address book in the background, and you can decline the permission and add contacts manually instead. Either way, we read only name, email address(es), and phone number(s) — never photos, postal addresses, notes, or other contact fields. Selecting or importing contacts never sends an invitation by itself; you review and confirm before we create anything, and separately choose whether each invitation is for email, text message, or both. We create a secure one-time invitation link but do not send it ourselves — you share it yourself through your own email app or text messaging app, and we have no way to know whether you actually send it or whether the recipient receives it. We store the destination(s) you invite, the invitation token, and whether you opened an email/text composer or copied the link for that invitation.
3. How we use your data
- To create and display your public professional profile
- To send email verification and password reset messages through our configured SMTP provider
- To display profile view and engagement analytics in your dashboard
- To process subscription payments and manage billing state via Stripe webhooks
- To prevent abuse, enforce rate limits, and protect platform security
- To respond to contact form messages
- To create secure invitation links for people you explicitly select, which you then share yourself by email or text message — we do not send these on your behalf
We do not sell your personal data. We do not use your data to build advertising profiles.
Newsletter
If you enter your email in the newsletter form we send one confirmation email. You are subscribed only after you click the confirmation link (valid 48 hours). We record the confirmation time and the wording version you agreed to. Unconfirmed requests are deleted after 7 days. Every email will include an unsubscribe link; on that page you may also ask us to delete your address entirely. Deleting your account removes your newsletter record. We do not sell or share the list.
4. Advertising
Where enabled, advertisements appear only on eligible public profile pages for signed-out visitors, under the heading "Advertisements". If advertising is provided by Adsterra, nothing is requested from the ad network until you choose "Show advertisements"; you can withdraw at any time with "Hide advertisements". Browsers sending a Global Privacy Control signal are not shown ads automatically.
DigiBioFi may display advertisements served by Google AdSense and other third-party vendors on public content and profile pages. Third-party vendors, including Google, use cookies and web beacons to serve ads based on a user's prior visits to this website or other websites on the internet.
Google's use of advertising cookies enables it and its partners to serve ads to users based on their visit to DigiBioFi and/or other sites on the Internet. For complete information on how Google manages and uses information collected across partner sites, please visit How Google uses information from sites or apps that use our services.
Users may opt out of personalized advertising by visiting Google Ads Settings. Alternatively, you can opt out of third-party vendor use of cookies for personalized advertising by visiting aboutads.info choices.
Ad placement and data: Ad code is rendered only in configured public-page placements, including eligible public profiles; it is not rendered in authenticated dashboards, administration, or billing. Google receives the page request and public-page context needed to serve and measure ads under Google's policies. Content you choose to publish on a public profile is visible to visitors and may be available to the ad script while it renders. DigiBioFi does not send private account documents, contact lists, or credentials as ad-targeting fields. Uploaded resume files are delivered only through the access-checked resume route when the profile is public.
5. Data sharing
We share data only with the following third-party services required to operate the platform:
- Stripe — payment processing
- Configured SMTP provider — transactional email delivery (account emails such as verification and password reset; contact-invite emails are sent from your own email app, not by us)
- Google AdSense or Adsterra — advertising display (eligible public pages only, with your consent)
- Hostinger — hosts the support mailbox; messages you send to the support address are stored there and, when synchronization is enabled, copied into our admin support inbox as untrusted text (attachments are not stored)
- IPWho — approximate geolocation from a coarse network address for analytics and account-security review, when configured
- Mapbox — map imagery for the Admin and Elite Geography views. Your browser loads map tiles from Mapbox, so Mapbox receives that browser's IP address and requested map area; we send Mapbox no visitor data, only the aggregated, approximate locations drawn locally in the page
We do not share your data with data brokers, list vendors, or unaffiliated third parties for marketing purposes.
6. Data retention
Profile, resume, completed AI results, career goals and coaching history are retained while your account exists, with no separate automatic expiry. Successful account deletion removes your local account records, owned uploads, generated exports and cached resume proposals. If file cleanup or subscription cancellation fails, deletion pauses and the account remains available for retry. Organization ownership must first pass to an eligible active member. Messages and attachments shared with recipients, support records and organization-owned recruiting history may remain for those recipients or the organization.
Contact messages older than 365 days and analytics events, geolocation rows and profile-view records older than 730 days are eligible for automatic deletion. A scheduled background process removes bounded batches; processing delays or a stopped worker can extend those periods. Security and audit records, bug reports and invitation opt-out suppression have no automatic age expiry in the current application. Provider records and backup copies follow separate retention processes; local account deletion does not establish erasure from Stripe, identity/email providers, logs or backups. Stripe may retain financial records under its own obligations.
7. Security
We use industry-standard measures to protect your data: HTTPS enforced in production, bcrypt password hashing, CSRF protection on all forms, HTTP security headers (HSTS, CSP, X-Frame-Options), and rate limiting. We conduct security reviews before deploying changes.
8. Your rights
You have the right to access, correct, export, or delete your personal data. To exercise these rights, contact us at privacy@digibiofi.com. We will respond within 30 days.
You can update profile visibility (public / private) and edit or delete profile content at any time through your dashboard.
9. Cookies and Tracking Technologies
We use cookies and similar technologies for the following purposes:
- Strictly Necessary Cookies: Secure HTTP-only session cookies to authenticate users and prevent session hijacking, and CSRF token cookies to prevent cross-site request forgery attacks.
- Preference Cookies: Local storage settings to remember your visual theme preference (dark/light mode).
- Advertising Cookies & Web Beacons: On public-facing pages where advertisements are rendered, Google and its certified ad tech partners set cookies and web beacons to serve, measure, and personalize advertisements according to Google's policies.
We do not use tracking pixels, keystroke monitors, or fingerprinting scripts for internal behavioral tracking.
10. Changes to this policy
We may update this policy to reflect changes in our practices or applicable law. When we make material changes, we will update the effective date at the top of this page. Continued use of DigiBioFi after changes constitutes acceptance of the updated policy.