Privacy and Data Security on Givee

Your privacy and data security are a top priority on Givee. 🛡️ Let’s break down how Givee handles your data and what you can do to keep your account secure:

Data Collection & Usage:

• Personal Information: When you sign up, Givee collects things like your email and maybe name. This is used for your account and communication (password resets, important updates, etc.). They don’t sell this info; it’s just to service your account.
  
  

• Content Data: Everything you put on your Givee page (links, text, images) is stored so it can be displayed to your visitors. This content is under your control – you can add, edit, delete as you wish.
  
  

• Analytics Data: Givee tracks page visits and related metrics (like we discussed in Analytics). This is to provide you with insights and to improve the service. These analytics might use cookies or local storage for counting unique visitors, but it’s aggregated – Givee cares about totals and patterns, not personally identifying your visitors.
  
  

• Third-Party Services: Givee integrates with others (Stripe for payments, Tinybird/Posthog for analytics, etc.). These services may handle data under their own policies. For example, Stripe handles payment info securely (Givee never sees your full card number).
  
  

• Cookie Policy: Expect that Givee uses cookies or similar to keep you logged in and maybe for analytics. They likely have a cookie notice if required by law in certain regions.
  
  

Data Security Measures:

• Encryption: Givee uses HTTPS across the board (your pages and the dashboard). This means data transmitted (like login credentials, page content updates) is encrypted in transit. Always check for the padlock in the address bar.
  
  

• Passwords: If Givee uses passwords (or just social logins?), those are stored hashed, not plain text. Make a strong password regardless.
  
  

• Integrations OAuth: When you connect integrations (Instagram, etc.), Givee doesn’t get your actual password for those – it gets a token. These tokens are stored securely and can only be used to fetch what you authorized.
  
  

• Infrastructure: Hosted likely on reputable platforms (maybe Vercel/AWS). They maintain security patches and monitoring. Your data is in databases with restricted access. DynamoDB (for reactions) and PostgreSQL for main data are enterprise-grade – only Givee’s application can query them with proper keys.
  
  

• Access Control: Within your account, you can invite team members; only they can change your content. Random people cannot modify your page. Always only invite people you trust, and give them appropriate roles.
  
  

• Backups: Givee likely keeps backups of data to prevent loss. So if something catastrophic happens, they can restore. Backups are stored securely too.
  
  

Your Role in Security:

• Secure Password & 2FA: Use a strong, unique password for Givee if not using social login. As of now, Givee hasn’t mentioned two-factor authentication. If they introduce it, enable it. For now, strong password + don’t reuse it is key.
  
  

• Phishing Awareness: Givee will never ask for your password via email or DMs. If you get any suspicious communication, double-check. Only log in at the official Givee site (check the URL).
  
  

• Device Safety: Log out of Givee on shared devices. Keep your browser and OS updated to avoid vulnerabilities that could compromise saved logins.
  
  

• Integration Tokens: If you suspect any integration token is misused or you want to revoke, you can disconnect the integration via Givee or via the third-party (like in Instagram settings). Then reconnect fresh if needed.
  
  

Privacy Controls:

• Public vs Private: Givee pages are public by nature (anyone with your URL can see it). There isn’t a “private page” mode since the purpose is sharing. So avoid putting private info on a public Givee.
  
  

• Data Removal: If you delete something (block or whole page), it’s removed from public view immediately. Givee might keep a backup for a period, but eventually it’s purged. If you need all your data removed (GDPR right to erasure), you can delete your account or contact support.
  
  

• Third-party content: If you embed e.g., a YouTube video or tweet, note those external sites have their own tracking (YouTube might set cookies for a viewer, etc.). That’s part of using those services; just something to be aware of if you care about your visitor’s privacy too. Givee can't control third-party embeds’ trackers.
  
  

Transparency:

• Givee likely has a Privacy Policy document. It would detail everything like what they collect, how they use it, under what basis (e.g., legitimate interest to provide service), and how you can inquire about your data. It’s worth reading that (usually found in the site footer or docs).
  
  

• If Givee undergoes changes (like being acquired or changing policies), they usually email users about Privacy Policy updates. Keep an eye on those and review changes.
  
  

Payment Info:

• When you enter credit card info for billing, it’s processed by Stripe. Givee doesn’t store your full card details, just a token or last 4 digits via Stripe. Stripe is PCI DSS compliant. So your financial data is handled with industry best practice.
  
  

GDPR/CCPA Compliance:

• If you’re in EU or certain jurisdictions, you have rights to access your data, correct it, delete it, etc. Givee should facilitate those. For example, deleting account covers deletion, you can edit your info in profile covers correction, etc. They likely have a contact email for privacy requests if needed.
  
  

• Cookie consent: If Givee has EU users, they may show a cookie banner. If not, they might be relying on the fact the cookies are necessary for service or anonymized analytics.
  
  

In summary, Givee puts strong efforts to protect your data – but security is a shared responsibility. They secure the platform, you secure your account usage. Feel confident using Givee, knowing your personal data isn’t being misused and that your page’s content is safe (and backed up). And of course, if you ever have concerns, reach out to their support for clarity – a good platform will happily address security questions from users. 🔒