Frequently Asked Questions

Redactli uses AES-SIV-512 deterministic encryption to transform sensitive values in your CSV files. When you select columns to anonymize (like names, emails, or account numbers), Redactli encrypts each value into a human-readable token. For example: 'John Smith' becomes 'Name_a3b7c9d2'. The same input always produces the same encrypted output, which preserves data relationships for AI analysis while protecting identities.

No. Redactli processes your CSV entirely in your browser using JavaScript. Only the selected column values you choose to encrypt are sent to our API—never the full file. Your raw data, file structure, headers, and unselected columns never touch our servers. This is a core privacy principle of Redactli.

Redactli uses AES-SIV-512 (AES Synthetic IV mode with 512-bit keys), a deterministic authenticated encryption algorithm. This ensures the same plaintext always encrypts to the same ciphertext, which is essential for preserving data relationships in AI analysis. AES-SIV is a NIST-approved encryption standard used in high-security applications.

Yes! Redactli includes smart PII detection that scans your CSV column headers and suggests which columns likely contain personally identifiable information (PII). It detects common patterns like names, email addresses, phone numbers, addresses, ID numbers (ABN, ACN, SSN, passport), and financial data (account numbers, credit cards). You can accept the suggestions or manually select which columns to encrypt. The final decision is always yours.

Deterministic encryption means the same input always produces the same output. This is different from randomized encryption where the same input produces different outputs each time. For example: 'john@example.com' → 'Email_k9m2p4x7' (always the same). Why it matters for AI: If the same customer appears 10 times in your data, AI will see the same encrypted token 10 times and recognize it's the same entity—without knowing the actual identity. This preserves patterns, relationships, and analytical value.

Your encryption keys are stored in Supabase Vault, an encrypted key management system. Keys are encrypted at rest using AES-256 and are only accessible to your account. Redactli employees cannot access your encryption keys or decrypt your data. You have full control over key rotation and management through your dashboard.

No. Redactli is designed with privacy-first principles: (1) Client-side processing: Your raw CSV never leaves your browser. (2) No data storage: We don't store uploaded files, processed data, or results. (3) Encrypted keys: Encryption keys are encrypted at rest and only you can access them. (4) In-memory only: API requests are processed in real-time and discarded immediately. When your session ends, all data is purged from memory. We cannot and do not retain your data.

Yes. Redactli implements pseudonymization as defined by GDPR Article 4(5). The encrypted data cannot be attributed to individuals without the encryption key. Key compliance features: (1) Data minimization: Only selected column values are processed. (2) No data retention: We don't store your raw or anonymized data. (3) Client-side processing: Sensitive data stays in your browser. (4) Encryption key control: You control and can delete your keys anytime. This makes Redactli compliant with GDPR (EU), Australian Privacy Act, CCPA (California), and similar data protection regulations.

Nothing is stored. Redactli processes everything in real-time: (1) Your browser uploads only selected column values to our API. (2) Our API encrypts/decrypts the values in memory. (3) Encrypted values are returned to your browser immediately. (4) Your browser reconstructs the CSV with encrypted values. (5) All data is purged from server memory. We don't have backups, logs, or archives of your data. Once the API response is sent, the data is gone forever.

If you lose your encryption key, data encrypted with that key remains permanently encrypted. This is a security feature—not even Redactli employees can recover lost keys. Best practices: (1) Download and securely store your key when it's first generated. (2) Use a password manager (1Password, LastPass, Bitwarden) to store keys. (3) Never share your encryption key via email or messaging. You can rotate to a new key anytime, but data encrypted with the old key will remain encrypted forever unless you have that key saved.

Yes, paid plan users (Starter, Pro, or Lifetime) can rotate encryption keys. This generates a new key and marks the old one as inactive. When to rotate keys: (1) Compliance requirements (e.g., annual key rotation). (2) Security incident or suspected key compromise. (3) Team member departure who had key access. (4) Regular security hygiene. Important: Data encrypted with the old key cannot be used with the new key. Save your old key if you need to work with historical anonymized data.

The Free plan includes: (1) 10 files per month (resets monthly). (2) 200 rows per file maximum. (3) Encryption only (no decryption). (4) CSV input/output only. (5) PII detection and smart suggestions. (6) AES-SIV-512 encryption. Free tier is perfect for testing Redactli or occasional use. For regular use, check out our paid plans.

Free plan: You're hard-limited to 10 files and 200 rows per file per month. When you hit the limit, you'll see an upgrade prompt and cannot process more files until next month or upgrade. Paid plans: Starter (100 files/5,000 rows) and Pro (500 files/50,000 rows) have soft limits. If you consistently exceed them, we'll contact you about upgrading to the next tier. We don't automatically cut you off or charge overage fees.

Yes! You can upgrade or downgrade your plan anytime. Upgrades: Take effect immediately, you're charged the prorated difference. Downgrades: Take effect at the end of your current billing period. Cancellations: You keep access until the end of your paid period. No contracts or commitments—cancel anytime. Your encryption keys remain accessible as long as you have an account.

Yes! We offer a 14-day money-back guarantee on all paid plans (Starter and Pro monthly/yearly). If you're not satisfied within 14 days of purchase, email us at support@redactli.com for a full refund—no questions asked. Note: The Lifetime Deal is final sale (non-refundable) due to limited quantity and one-time pricing.

Starter ($9/month): 100 files/month, 5,000 rows per file, 1 user only (no teams), CSV input/output, Email support. Pro ($29/month): 500 files/month, 50,000 rows per file, 3 users included ($9 per extra seat), Everything in Starter plus team collaboration features, encryption key rotation, usage analytics dashboard, and priority email support.

Yes! Pay $49 once and get Starter-tier features (100 files/month, 5,000 rows per file) forever. Important limitations: (1) 1 user only — Cannot add team members (unlike Pro). (2) Limited quantity: Capped at 200 units total. (3) Launch only: Available for 2-4 weeks, then removed. (4) No refunds: Final sale due to lifetime pricing. Perfect for solo entrepreneurs, consultants, or small business owners who want permanent access without monthly fees.

Redactli works with any AI tool that accepts CSV file uploads, including: ChatGPT (OpenAI), Claude (Anthropic), Gemini (Google), Perplexity AI, Microsoft Copilot, and custom AI applications and APIs. The anonymized CSV is a standard file format that works universally. You can also use it with data analysis tools like Excel, Tableau, Power BI, or Python/R scripts.

Redactli accepts CSV files, which Excel can export. To use Redactli with Excel data: (1) Open your Excel file (.xlsx). (2) Go to File → Save As. (3) Select 'CSV (Comma delimited)' format. (4) Upload the CSV to Redactli. After anonymization, you can download the result as a CSV file. Redactli preserves all your data—only the selected columns are encrypted. You can then open the CSV in Excel if needed.

Yes! Two ways: (1) Export/Import Method: Download your Google Sheet as CSV, upload to Redactli web app, download encrypted CSV, import back to Google Sheets™. (2) Google Sheets™ Add-on (Recommended): Install the Redactli add-on, generate an API key in your Redactli account, enter API key in add-on settings, encrypt/decrypt directly within Google Sheets™! The add-on is faster and more convenient.

Redactli accepts and exports CSV (Comma-Separated Values) files only. CSV is a universal format that works with Excel, Google Sheets™, and all AI tools. To use Redactli with your data: Excel: Export as CSV (File → Save As → CSV). Google Sheets™: Use File → Download → Comma-separated values (.csv). After encryption: Download CSV and open in Excel or any tool.

File size limits depend on your plan's row limit: Free: 200 rows per file (typically ~50KB). Starter: 5,000 rows per file (typically ~1-2MB). Pro: 50,000 rows per file (typically ~10-20MB). There's no hard limit on file size in MB—just the row count. If you have a massive file with millions of rows, split it into chunks that fit your plan's row limit. Tip: Most CSV files are small. A 5,000-row customer list is typically only 1-2MB.

Yes, with important caveats: (1) Encrypted files are safe to share — They contain no sensitive data, only encrypted tokens. (2) Encryption keys should NOT be shared casually — Anyone with the key can decrypt. (3) Pro plan supports teams — Add team members to your account ($9/seat), they get shared keys. Free/Starter plans: You're the only user. If you share your key, that person could decrypt your data, but they'd need their own Redactli account to use the decrypt feature. Pro plan: Team members share the same encryption keys and can collaborate on encrypted datasets.

Encrypt any columns containing personally identifiable information (PII) or sensitive data. Always encrypt: Names (first, last, full name), email addresses, phone numbers, physical addresses, ID numbers (ABN, ACN, SSN, passport, driver's license), account numbers, credit cards. Consider encrypting: Company names (if sensitive client list), IP addresses, medical record numbers, employee IDs. Don't encrypt: Transaction amounts, dates, timestamps, product names, categories, non-sensitive metrics (click counts, etc.), generic demographic data (age ranges, regions). Redactli's PII detection will suggest columns to encrypt based on header names. You always have final control.

Absolutely! In fact, this is the recommended approach. When you upload a CSV, Redactli shows you checkboxes for each column. Select only the columns containing sensitive data (names, emails, IDs). Leave data columns unchecked (amounts, dates, categories). Example: Customer purchase data - Encrypt: Customer Name, Email, Phone. Leave plain: Purchase Date, Product Name, Amount, Category. This gives AI the data it needs to analyze (what was bought, when, how much) while protecting customer identities.